LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Keir Fraser <keir@xensource.com>
Cc: Chris Wright <chrisw@sous-sol.org>, Andi Kleen <ak@muc.de>,
<xen-devel@lists.xensource.com>,
Ian Pratt <Ian.Pratt@xensource.com>,
<virtualization@lists.osdl.org>,
Steven Hand <steven.hand@cl.cam.ac.uk>,
Christian Limpach <Christian.Limpach@xensource.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options.
Date: Fri, 16 Feb 2007 11:03:06 +0000 [thread overview]
Message-ID: <C1FB3FEA.98F7%keir@xensource.com> (raw)
In-Reply-To: <20070216025452.d25e3545.akpm@linux-foundation.org>
On 16/2/07 10:54, "Andrew Morton" <akpm@linux-foundation.org> wrote:
> OK, you're screwed. I agree that the process freezer is the way out of that
> one.
>
> Ingo said that he's clocked the freezer at a few milliseconds. But if it's
> any higher than that it'll need to get sped up once we convert cpu hotplug
> to use it.
A few milliseconds is acceptable. Presumably that is under some stress
workload? What we'd really like is to be able to gang-hotplug CPUs to
amortise the freezer overhead.
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.
-- Keir
next prev parent reply other threads:[~2007-02-16 11:03 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 [this message]
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
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=C1FB3FEA.98F7%keir@xensource.com \
--to=keir@xensource.com \
--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=linux-kernel@vger.kernel.org \
--cc=steven.hand@cl.cam.ac.uk \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--subject='Re: [patch 14/21] Xen-paravirt: Add XEN config options and disableunsupported config options.' \
/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
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).