Messages in this thread | | | Date | Wed, 30 Sep 2009 17:56:02 +0200 | From | Avi Kivity <> | Subject | Re: [PATCH v4: kvm 1/4] Code motion. Separate timer intialization into an indepedent function. |
| |
On 09/30/2009 05:51 PM, Zachary Amsden wrote: >> Is anything preventing us from unifying the constant_tsc and !same >> paths? We could just do a quick check in the notifier, see the tsc >> frequency hasn't changed, and return. > > > Actually, yes. On constant_tsc processors, the processor frequency > may still change, however the TSC frequency does not change with it. > > I actually have both of these kinds of processors (freq changes with > constant TSC and freq changes with variable TSC) so I was able to test > both of these cases.
If the API allows us to query the tsc frequency, it would simply return the same values in all cases, which we'd ignore.
-- error compiling committee.c: too many arguments to function
| |