Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756390Ab1BCPQj (ORCPT ); Thu, 3 Feb 2011 10:16:39 -0500 Received: from router-fw.net-space.pl ([89.174.63.77]:33559 "EHLO router-fw.net-space.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756325Ab1BCPQi (ORCPT ); Thu, 3 Feb 2011 10:16:38 -0500 Date: Thu, 3 Feb 2011 16:14:50 +0100 From: Daniel Kiper To: Ian Campbell Cc: Pasi K?rkk?inen , Daniel Kiper , "jeremy@goop.org" , "xen-devel@lists.xensource.com" , "haicheng.li@linux.intel.com" , Konrad Rzeszutek Wilk , Dan Magenheimer , Vasiliy G Tolstov , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "andi.kleen@intel.com" , "akpm@linux-foundation.org" , "fengguang.wu@intel.com" Subject: Re: [Xen-devel] Re: [PATCH 2/3] drivers/xen/balloon.c: Various balloon features and fixes Message-ID: <20110203151450.GA1364@router-fw-old.local.net-space.pl> References: <20101220134724.GC6749@router-fw-old.local.net-space.pl> <20101227150847.GA3728@dumpdata.com> <947c7677e042b3fd1ca22d775ca9aeb9@imap.selfip.ru> <20101227163918.GB7189@dumpdata.com> <92e9dd494cc640c04fdac03fa6d10e8d@imap.selfip.ru> <20101229164910.GD2743@router-fw-old.local.net-space.pl> <20101231112043.GZ2754@reaktio.net> <1294141394.3831.183.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1294141394.3831.183.camel@zakaz.uk.xensource.com> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2714 Lines: 56 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 > > > > 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 > > > > >> 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/