LKML Archive on
help / color / mirror / Atom feed
From: Dan Hecht <>
To: Zachary Amsden <>
Cc: Keir Fraser <>,
	Chris Wright <>,,,
	Christian Limpach <>,
	Andi Kleen <>, Andrew Morton <>,
	Steven Hand <>,, Ian Pratt <>
Subject: Re: [Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config	options and disableunsupported config options.
Date: Fri, 16 Feb 2007 14:38:13 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 02/16/2007 01:51 PM, Zachary Amsden wrote:
> Keir Fraser wrote:
>> On 16/2/07 17:46, "Jeremy Fitzhardinge" <> wrote:
>>> Keir Fraser wrote:
>>>> This initial patchset does not include save/restore support anyway, so in
>>>> fact it would be consistent to have CONFIG_PREEMPT configurable. I'm sure
>>>> that we are going to have some nasty bugs to fix up as a result, but we
>>>> can't fix them until we find them! Then we can convert our save/restore code
>>>> to use the freezer before submitting it for inclusion.
>>> OK.  So that makes the only config restriction the 100Hz ticks.
>> We can extend the Xen timer interface quite easily and get rid of this one
>> too. In fact it doesn't *much* matter if the CONFIG_HZ differs from the Xen
>> ticker rate -- we modified the Linux timer ISR to handle timer interrupts at
>> arbitrary times already. The only drawback is that jiffies updates in burts
>> if CONFIG_HZ is higher than the actual tick rate, and this can affect some
>> calibration constants and cause Linux to print out some weird values at
>> start-of-day.
> That's why we'd very much like to get a get_cpu_speed paravirt-op 
> implemented.  I think this would be useful to work around these problems 
> for Xen as well.

Yes, and regardless of whether you run your periodic timer slower than 
HZ, calibrating time in a VM is always difficult due to the fact the 
kernel is time sharing the physical cpu.  Why not just ask the 
underlying hypervisor?

Really, Time is one of those areas where paravirtualization makes a lot 
of sense, no matter how much virtualization hardware you have crammed 
into your cpu....

  reply	other threads:[~2007-02-16 22:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 10:00 Christian Limpach
2007-02-16 10:09 ` Andrew Morton
2007-02-16 10:47   ` Keir Fraser
2007-02-16 10:54     ` Andrew Morton
2007-02-16 11:03       ` Keir Fraser
2007-02-16 17:46         ` [Xen-devel] " Jeremy Fitzhardinge
2007-02-16 19:00           ` Keir Fraser
2007-02-16 19:24             ` Jeremy Fitzhardinge
2007-02-16 21:51             ` Zachary Amsden
2007-02-16 22:38               ` Dan Hecht [this message]
2007-02-17 15:06                 ` Rik van Riel

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config	options and disableunsupported config options.' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).