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-users

Re: [Xen-users] [XCP] domain 0 kernel patch queue published

To: "Ian Campbell" <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-users] [XCP] domain 0 kernel patch queue published
From: "Matthew Law" <matt@xxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Mar 2010 15:52:49 -0000
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 11 Mar 2010 07:54:00 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
In-reply-to: <1268320075.10129.1431.camel@xxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1268320075.10129.1431.camel@xxxxxxxxxxxxxxxxxxxxxx>
Reply-to: matt@xxxxxxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: SquirrelMail/1.4.19
Ian,

out of interest, what is covered by "those which are not upstreamable"? -
IIRC, there is code in XCP that forces an I/O flush for consistent
snapshots which is of particular value.  Will the likes of this be pushed
up into the pv ops tree?

Thanks,

Matt

On Thu, March 11, 2010 3:07 pm, Ian Campbell wrote:
> The kernel patch queue used by the Xen Cloud Platform domain 0 has been
> published at:
>         http://xenbits.xen.org/XCP/linux-2.6.27.pq.hg
>
> This kernel has been the recipient of extensive testing and performance
> optimization and is actively maintained with the latest stable drivers.
>
> There is ongoing work to merge patches which are not currently upstream
> into the paravirtops tree or to remove the need for those which are not
> upstreamable.
>
> In order to avoid further divergence we would ask that any submissions
> to this tree take the form of a backport from something which is already
> committed to the pvops kernel. XCP will be moving to 2.6.32 the based
> PVops kernel once it achieves a similar level of testing/performance to
> the existing kernel.
>
> The patch queue is developed against the "v2.6.27" tag in
> http://kernel.org/hg/linux-2.6/ using the mercurial mq extension:
>         $ hg clone http://kernel.org/hg/linux-2.6/ linux-2.6.hg
>         $ cd linux-2.6.hg
>         $ hg clone http://xenbits.xen.org/XCP/linux-2.6.27.pq.hg
> .hg/patches
>         $ hg update v2.6.27
>         $ hg qpush -a
>
> Other patch management systems seem to work although these will be
> subject to the foibles of the different tools with regard to accepted
> levels of fuzz etc.
>
> The queue current applies using guilt against the "v2.6.27" tag in
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git iff
> you have a guilt recent enough to ignore comments at the end of lines in
> the series file (0.30 from Debian Lenny is not new enough, 0.32.2 from
> Debian Sid is) and manually touch the status file.
>         $ git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> linux-2.6.git
>         $ cd linux-2.6.git
>         $ mkdir .git/patches
>         $ hg clone http://xenbits.xen.org/XCP/linux-2.6.27.pq.hg
> .git/patches/master
>         $ touch .git/patches/status
>         $ git reset --hard v2.6.27
>         $ guilt push -a
>
> Using quilt against
> http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.27.tar.bz2.
> appears to work but requires you to allow additional fuzz e.g.
> "QUILT_PATCH_OPTS=-F3 quilt push -a".
>
> Ian.


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

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