WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: SOLVED: Re: [Xen-devel] Issue with pv_ops Kernel 2.6.31.6 and Xen [y

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: SOLVED: Re: [Xen-devel] Issue with pv_ops Kernel 2.6.31.6 and Xen [yinghai@xxxxxxxxxx: [PATCH 01/35] x86: fix sci on ioapic 1]
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 17 Feb 2010 10:33:54 +0200
Cc: Marcial Rion <marcial.rion@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Wed, 17 Feb 2010 00:37:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B7B1349.9020003@xxxxxxxx>
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: <20100210153954.GA9539@xxxxxxxxxxxxxxxxxxx> <4B7731DE.8020905@xxxxxxxxxxxxxx> <20100216181005.GC21067@xxxxxxxxxxxxxxxxxxx> <4B7B1349.9020003@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Tue, Feb 16, 2010 at 01:51:05PM -0800, Jeremy Fitzhardinge wrote:
>>    
>>> Question: Is it known when this piece of code will be introduced in the
>>> "pv_ops Kernel tree"?
>>>      
>> Hmm.. Jeremy's plans are to re-base the pvops changes that went in
>> 2.6.31.6 onto 2.6.32. The reason being that 2.6.32 has been choosen by
>> many distributions as their next vehicle for release. The patches being
>> mostly, if possible, related only to Xen.
>>
>> The patch I forwarded to you is targetted for 2.6.33 so it would not appear
>> normally in 2.6.32 tree unles Greg KH choose to back-port it in. Greg is
>> the maintainer of the 2.6.32 stable tree.
>>
>> I would recommend you e-mail Greg KH with this e-mail, explain your
>> situation  and ask him if he wouldn't mind merging the patch in.
>> Thought you might need to do some of the work yourself
>> (as in, merge the patch in an earlier kernel) - it seems you already
>> have done this so hopefully that shouldn't be a problem.
>>
>> Try it that way, as this way also the distributions will pick up the fix
>> and you would be able to load any new distro on your box without having
>> to manually recompile the kernel and such.
>>    
>
> Is that one change enough to fix the reported problem?  Can we just  
> cherry-pick it over?  Or does it need a lot of supporting patches?
>
>> Then when Jeremy revs up the xen/next tree to next stable rev (I think
>> he will do this, not sure?), it will automatically be picked up (if Greg 
>> picks it up in his tree).
>>    
>
> Yes.  At the moment xen/next is based on plain 2.6.32 because that is  
> also an ancestor version of mainline git development.  Once the 2.6.32  
> tree basically works (which should be close), then I can merge all the  
> stable branch changes onto it and call it "xen/stable" or something.
>

So that means I should try xen/next now? :)

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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