LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Pasi Kärkkäinen" <email@example.com>
Cc: Daniel Kiper <firstname.lastname@example.org>,
Konrad Rzeszutek Wilk <email@example.com>,
Dan Magenheimer <firstname.lastname@example.org>,
Vasiliy G Tolstov <email@example.com>,
Subject: Re: [Xen-devel] Re: [PATCH 2/3] drivers/xen/balloon.c: Various balloon features and fixes
Date: Tue, 4 Jan 2011 11:43:14 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Fri, 2010-12-31 at 11:20 +0000, Pasi Kärkkäinen wrote:
> On Wed, Dec 29, 2010 at 05:49:10PM +0100, Daniel Kiper wrote:
> > Hi,
> > On Tue, Dec 28, 2010 at 12:52:03AM +0300, Vasiliy G Tolstov wrote:
> > > On Mon, 27 Dec 2010 11:39:18 -0500, Konrad Rzeszutek Wilk
> > > <email@example.com> wrote:
> > > > On Mon, Dec 27, 2010 at 07:27:56PM +0300, Vasiliy G Tolstov wrote:
> > > >> On Mon, 27 Dec 2010 10:08:47 -0500, Konrad Rzeszutek Wilk
> > > >> <firstname.lastname@example.org> wrote:
> > > >> > On Mon, Dec 20, 2010 at 02:47:24PM +0100, Daniel Kiper wrote:
> > > >> >> Features and fixes:
> > > >> >> - HVM mode is supported now,
> > > >> >> - migration from mod_timer() to schedule_delayed_work(),
> > > >> >> - removal of driver_pages (I do not have seen any
> > > >> >> references to it),
> > > >> >> - protect before CPU exhaust by event/x process during
> > > >> >> errors by adding some delays in scheduling next event,
> > > >> >> - some other minor fixes.
> > > >>
> > > >> I have apply this patch to bare 126.96.36.199 kernel from kernel.org. If
> > > >> memory=maxmemory pv guest run's on migrating fine.
> > > >> If on already running domU i have xm mem-max xxx 1024 (before that it
> > > >> has 768) and do xm mem-set 1024 guest now have 1024 memory, but after
> > > >> that it can't migrate to another host.
> > Do you still need memory hotplug patch for jeremy stable-2.6.32.x ???
> I think it would be good to have it for xen/stable-2.6.32.x aswell!
In general we are hoping to move development of new features to more
recent upstream versions and become increasingly conservative with what
gets taken into the 2.6.32.x branch.
If we think a particular feature is worth having for 2.6.32.x then I
think it would be worth getting them upstream and stabilised before
considering it for backport to 2.6.32.x.
> (that's the tree that's used the most atm).
But what is the demand for this particular functionality among the users
of that tree who cannot or will not switch to a more recent upstream?
Bearing in mind that this is primarily a domU feature and that domU
support is well established upstream.
next prev parent reply other threads:[~2011-01-04 11:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 13:47 Daniel Kiper
2010-12-20 14:51 ` [Xen-devel] " Ian Campbell
2010-12-29 15:01 ` Daniel Kiper
2010-12-27 15:08 ` Konrad Rzeszutek Wilk
2010-12-27 16:27 ` Vasiliy G Tolstov
2010-12-27 16:39 ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-12-27 21:52 ` Vasiliy G Tolstov
2010-12-29 16:49 ` Daniel Kiper
2010-12-31 11:20 ` Pasi Kärkkäinen
2011-01-04 11:43 ` Ian Campbell [this message]
2011-02-03 15:14 ` Daniel Kiper
2010-12-29 15:19 ` Daniel Kiper
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 2/3] drivers/xen/balloon.c: Various balloon features and fixes' \
* 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).