All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org, Ian Pratt <Ian.Pratt@xensource.com>,
	Chris Wright <chrisw@sous-sol.org>,
	virtualization@lists.osdl.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Hand <steven.hand@cl.cam.ac.uk>,
	Christian Limpach <Christian.Limpach@xensource.com>
Subject: Re: [Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options.
Date: Fri, 16 Feb 2007 11:24:56 -0800	[thread overview]
Message-ID: <45D60508.10000@goop.org> (raw)
In-Reply-To: <C1FBAFD7.99AB%keir@xensource.com>

Keir Fraser wrote:
> 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.
>   

I was wondering what would happen if we tried that.  I guess its
equivalent to having stolen time between each Xen tick.

    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com, virtualization@lists.osdl.org,
	Steven Hand <steven.hand@cl.cam.ac.uk>,
	linux-kernel@vger.kernel.org, Chris Wright <chrisw@sous-sol.org>,
	Andi Kleen <ak@muc.de>, Andrew Morton <akpm@linux-foundation.org>,
	Ian Pratt <Ian.Pratt@xensource.com>,
	Christian Limpach <Christian.Limpach@xensource.com>
Subject: Re: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options.
Date: Fri, 16 Feb 2007 11:24:56 -0800	[thread overview]
Message-ID: <45D60508.10000@goop.org> (raw)
In-Reply-To: <C1FBAFD7.99AB%keir@xensource.com>

Keir Fraser wrote:
> 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.
>   

I was wondering what would happen if we tried that.  I guess its
equivalent to having stolen time between each Xen tick.

    J

  reply	other threads:[~2007-02-16 19:24 UTC|newest]

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

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=45D60508.10000@goop.org \
    --to=jeremy@goop.org \
    --cc=Christian.Limpach@xensource.com \
    --cc=Ian.Pratt@xensource.com \
    --cc=ak@muc.de \
    --cc=akpm@linux-foundation.org \
    --cc=chrisw@sous-sol.org \
    --cc=keir@xensource.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steven.hand@cl.cam.ac.uk \
    --cc=virtualization@lists.osdl.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.