This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: [GIT PULL] (xen) pm-bug-fixes for 2.6.32

To: Shriram Rajagopalan <rshriram@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [GIT PULL] (xen) pm-bug-fixes for 2.6.32
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 22 Mar 2011 16:45:44 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Delivery-date: Tue, 22 Mar 2011 18:24:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1ED784B4-2821-4B8D-A240-D29EF88A9FAE@xxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AANLkTinNsuuAQxzAc=-PK6tCEbEBJNaPgK0xV0r=DofT@xxxxxxxxxxxxxx> <4D877AE3.5070202@xxxxxxxx> <AANLkTini_bB73-EP44b9iE-_gdZdhmK8DAVMFQaQcoxP@xxxxxxxxxxxxxx> <1300801435.21142.28.camel@xxxxxxxxxxxxxxxxxxxxxx> <1ED784B4-2821-4B8D-A240-D29EF88A9FAE@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.9
On 03/22/2011 02:15 PM, Shriram Rajagopalan wrote:
> On 2011-03-22, at 6:43 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>> On Mon, 2011-03-21 at 23:10 +0000, Shriram Rajagopalan wrote:
>>> On Mon, Mar 21, 2011 at 9:20 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx>
>>> wrote:
>>>        On 03/21/2011 03:13 AM, Shriram Rajagopalan wrote:
>>>> Hi Jeremy,
>>>> Can you please pull
>>>> git://athos.nss.cs.ubc.ca/linux-2.6-pvops.git
>>>> <http://athos.nss.cs.ubc.ca/linux-2.6-pvops.git>
>>>        xen/pm-bug-fix
>>>> #xen/pm-bug-fix is based off xen/next-2.6.32,
>>>> commit ea954f6ff4ff5c15c9e2120e86335f6d6490ae0f
>>>> "Merge commit 'konrad-xen/for-2.6.32/bug-fixes~1' into
>>>        xen/next-2.6.32"
>>>> All patches in this branch have been merged into upstream
>>>        kernel.
>>>        Are they marked to go into the stable/longterm tree, or are we
>>>        just
>>>        going to maintain them separately?
>>> I think these should go into the longterm tree. I am a bit clueless as
>>> to what you
>>> exactly mean by "maintaining them separately". I thought next-2.6.32
>>> was meant 
>>> as a staging area, that later gets pushed to stable-2.6.32.x
>> I think Jeremy is asking whether these should go in via the upstream
>> "longterm" 2.6.32.y branch rather than only going into the
>> xen/next-2.6.32 branch.
> Thanks Ian. 
> Jeremy, I am not sure when/if these are going to go into the longterm branch. 
> But I think these should go into xen/next-2.6.32 atleast for the benefit of 
> folks who build both dom0 & domU out of your tree(the "make kernels" target 
> in xen source).

I just pulled it into xen/next-2.6.32 since it seems too fiddly properly
backport it to plain 2.6.32 and it doesn't really affect many users
(since as I understand it these just fix checkpoints, which have
probably been broken for a long time without complaints).


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>