[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v3] use INT64_MAX as max expiration



On Fri, 16 Mar 2012, Zhang, Yang Z wrote:
> Change from v2:
> Correct the logic when calculating icount.
> 
> Change from v1:
> According to Jan and Stefano's comments, drop the previous logic which 
> setting the value in an arbitrary way and use Stefano's suggestion instead.
> 
> Currently, the max expiration time is 2147483647ns(INT32_MAX ns). This is 
> enough when guest is busy, but when guest is idle, the next timer will be 
> later than INT32_MAX ns. And those meaningless alarm will harm the pkg 
> C-state.
> 
> PS: Since the overflow will not happen with the expression((delta / 1000) + 
> (delta % 1000 > 0 ? 1 : 0)), so i also removed the comments" To avoid 
> problems with overflow limit this to 2^32."
> 
> Signed-off-by: Yang Zhang <yang.z.zhang@xxxxxxxxx>


Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.