linux-kernel - Re: [Xen-devel] Re: [PATCH 2/3] drivers/xen/balloon.c: Various balloon features and fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110203151450.GA1364@router-fw-old.local.net-space.pl>
Date:	Thu, 3 Feb 2011 16:14:50 +0100
From:	Daniel Kiper <dkiper@...-space.pl>
To:	Ian Campbell <Ian.Campbell@...rix.com>
Cc:	Pasi K?rkk?inen <pasik@....fi>, Daniel Kiper <dkiper@...-space.pl>,
	"jeremy@...p.org" <jeremy@...p.org>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	"haicheng.li@...ux.intel.com" <haicheng.li@...ux.intel.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	Dan Magenheimer <dan.magenheimer@...cle.com>,
	Vasiliy G Tolstov <v.tolstov@...fip.ru>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"andi.kleen@...el.com" <andi.kleen@...el.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"fengguang.wu@...el.com" <fengguang.wu@...el.com>
Subject: Re: [Xen-devel] Re: [PATCH 2/3] drivers/xen/balloon.c: Various balloon features and fixes

On Tue, Jan 04, 2011 at 11:43:14AM +0000, Ian Campbell wrote:
> 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
> > > > <konrad.wilk@...cle.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
> > > > >> <konrad.wilk@...cle.com> 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 2.6.36.2 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.

I agree with Ian. However, I think that if it will be expected
by community I could prepare backport of final upstream version
and publish it as "unofficial" version.

Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/