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: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options.
Date: Fri, 16 Feb 2007 09:46:03 -0800 [thread overview]
Message-ID: <45D5EDDB.7050404@goop.org> (raw)
In-Reply-To: <C1FB3FEA.98F7%keir@xensource.com>
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.
J
next parent reply other threads:[~2007-02-16 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C1FB3FEA.98F7%keir@xensource.com>
2007-02-16 17:46 ` Jeremy Fitzhardinge [this message]
2007-02-16 19:00 ` [Xen-devel] Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options Keir Fraser
2007-02-16 19:00 ` Keir Fraser
[not found] <C1FBAFD7.99AB%keir@xensource.com>
2007-02-16 19:24 ` Jeremy Fitzhardinge
2007-02-16 21:51 ` Zachary Amsden
2007-02-16 22:38 ` [Xen-devel] " Dan Hecht
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:
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=45D5EDDB.7050404@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 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).