lkml.org 
[lkml]   [2009]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [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



\
 
 \ /
  Last update: 2009-09-30 17:59    [W:0.061 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site