> I'm a bit out of my depth with the xen build process here and perhaps
> someone will correct me but AFAIK, the standard build process in the
> xen-unstable tree will currently just build 2.6.16.13 and it is a manual
> process for someone to make the change in the unstable tree to move
> forwards to a later Linux snapshot.
Yep.
> This should make sense to you if you think that the code in the sparse
> tree and the patches in the patches directory all have to be consistent
> with the version of Linux chosen and changes to Linux are outside the
> control of the Xen developers. So any future version of Linux may
> require changes in the sparse tree and the patches directory before it
> will work correctly.
Yep yep.
> Perhaps someone who knows more would like to comment on support for
> Linux point releases.
The 2.6.x.y releases generally have small changes moving from y -> y+1. As a 
result it's often possible to stick the appropriate patch in the patches/ 
directory (or apply it directly to the build tree and rebuild) and have it 
work.
There are only a few places in generic code where there could be conflicts, 
and often the stable series patches don't touch the arch-specific code at 
all.
Strictly you should check through the patch and look for conflicts with 
Xen-related stuff. However, often (maybe even usually) it'll work, it's just 
not officially supported.
Cheers,
Mark
> > Or is that supported, but using a 2.6.17.x kernel wouldn't be supported?
> >
> > Johnny
> >
> > > Harry.
> > >
> > > On Thu, 2006年06月15日 at 11:47 +0200, Hans-Christian Armingeon wrote:
> > > > Hi Harry,
> > > >
> > > > I wanted mkbuildtree to automatically pick the patches, that are
> > > > needed. Some of the 2.6.16.13 patches seem to be already in the
> > > > mainline kernel tree.
> > > >
> > > > I can cleanly apply rcu_needs_cpu_patch to 2.6.16.20.
> > > >
> > > > Johnny
> > > >
> > > > Am Mittwoch, 14. Juni 2006 12:55 schrieben Sie:
> > > > > There's a patch in patches/linux-2.6.16.13 called
> > > > > rcu_needs_cpu.patch which provides rcu_needs_cpu for the 2.6.16.13
> > > > > kernel which is the one I tested against when I submitted the
> > > > > rcu_needs_cpu_patch.
> > > > >
> > > > > I'm not sure how you are getting the 2.6.16.20 kernel. If this is
> > > > > a standard part of the xen-unstable build that is supposed to work
> > > > > then let me know how to invoke it and I will fix up the problem.
> > > > >
> > > > > But maybe you have pulled 2.6.16.20 manually, applied the 2.6.16.13
> > > > > patches manually and then done an hg pull and got the new patch in
> > > > > the patches directory but failed to apply it to your kernel?
> > > > >
> > > > > Harry
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel 
-- 
Dave: Just a question. What use is a unicyle with no seat? And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel