From: Zachary Amsden <zach@vmware.com>
To: Andi Kleen <ak@muc.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 8/11] Add a CPU KHZ calibration function to paravirt-ops
Date: Tue, 06 Feb 2007 13:54:52 -0800 [thread overview]
Message-ID: <45C8F92C.9050605@vmware.com> (raw)
In-Reply-To: <20070206122628.GB47229@muc.de>
Andi Kleen wrote:
> On Mon, Feb 05, 2007 at 07:53:23PM -0800, Zachary Amsden wrote:
>
>> Provide a paravirtualized way to get the CPU clock frequency; this allows much
>> of the code in tsc.c to be shared between all paravirt implementations.
>>
>
> Is this really needed?
>
Honestly, no. But it is better and more accurate to do it.
> What worries me somewhat of your patches is that you seem
> to be quick at adding new hooks. But I would like to keep
> paravirtops as minimal as possible with new hooks only
> added when there is a very good justification.
>
> I don't see it here.
>
We can calibrate CPU frequency pretty accurately, despite being in a VM
where time does not operate in the normal way. Many other hypervisors
won't be able to do such a good job, or might not implement the required
hardware.
Adding this hook allows everyone to just re-use all the frequency
scaling / recalibration code in tsc.c.
The primary justification is allowing code re-use, which is why I
allowed myself to add a hook. I also want paravirt-ops to be as minimal
as possible.
Zach
prev parent reply other threads:[~2007-02-06 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 3:53 [PATCH 8/11] Add a CPU KHZ calibration function to paravirt-ops Zachary Amsden
2007-02-06 12:26 ` Andi Kleen
2007-02-06 21:54 ` Zachary Amsden [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45C8F92C.9050605@vmware.com \
--to=zach@vmware.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox