[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-changelog] [xen master] hvm/hpet: Correctly limit period to a maximum.
commit 825e70b1ec9df2a2d9f949232c4a368a0ea77416 Author: Don Slutz <dslutz@xxxxxxxxxxx> AuthorDate: Fri May 2 16:18:02 2014 -0400 Commit: Tim Deegan <tim@xxxxxxx> CommitDate: Thu May 8 12:03:53 2014 +0100 hvm/hpet: Correctly limit period to a maximum. In the code section after the comment: /* * Clamp period to reasonable min/max values: * - minimum is 100us, same as timers controlled by vpt.c * - maximum is to prevent overflow in time_after() calculations */ The current maximum limit actually allows "bad" values like 0 and 1. This is because it uses a mask not a maximum. Signed-off-by: Don Slutz <dslutz@xxxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> --- xen/arch/x86/hvm/hpet.c | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/xen/arch/x86/hvm/hpet.c b/xen/arch/x86/hvm/hpet.c index 910d87d..c64c547 100644 --- a/xen/arch/x86/hvm/hpet.c +++ b/xen/arch/x86/hvm/hpet.c @@ -404,6 +404,8 @@ static int hpet_write( if ( timer_is_periodic(h, tn) && !(h->hpet.timers[tn].config & HPET_TN_SETVAL) ) { + uint64_t max_period = (timer_is_32bit(h, tn) ? ~0u : ~0ull) >> 1; + /* * Clamp period to reasonable min/max values: * - minimum is 100us, same as timers controlled by vpt.c @@ -411,7 +413,8 @@ static int hpet_write( */ if ( hpet_tick_to_ns(h, new_val) < MICROSECS(100) ) new_val = (MICROSECS(100) << 10) / h->hpet_to_ns_scale; - new_val &= (timer_is_32bit(h, tn) ? ~0u : ~0ull) >> 1; + if ( new_val > max_period ) + new_val = max_period; h->hpet.period[tn] = new_val; } else -- generated by git-patchbot for /home/xen/git/xen.git#master _______________________________________________ Xen-changelog mailing list Xen-changelog@xxxxxxxxxxxxx http://lists.xensource.com/xen-changelog
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |