[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] use INT64_MAX as max expiration
On Wed, 14 Mar 2012, Ian Jackson wrote: > Zhang, Yang Z writes ("[PATCH] use INT64_MAX as max expiration"): > > 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. > > This is a power performance improvement, yes ? Should we be accepting > these into qemu-xen-unstable at this point ? Although TBH it's quite > a small change so it might be worth making an exception. I am in favor of making an exception for this one _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |