Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: [patch] M2P/P2M abstraction



On Mon, May 11, 2009 at 02:15:45PM +0200, Christoph Egger wrote:
> On Monday 11 May 2009 14:01:27 Manuel Bouyer wrote:
> > On Mon, May 11, 2009 at 01:57:54PM +0200, Jean-Yves Migeon wrote:
> > > Manuel Bouyer wrote:
> > >> On Mon, May 11, 2009 at 01:08:32PM +0200, Jean-Yves Migeon wrote:
> > >>> I told christoph privately that I will wait on the forthcoming Xen
> > >>> clean-up (where Xen 2 and Xen 3.0 support are dropped), as this will
> > >>> simplify a lot of the Xen code, including the use of XPMAP_OFFSET.
> > >>> Then  I will revisit it later.
> > >>
> > >> From memory, XPMAP_OFFSET is still used for Xen-3 ...
> > >
> > > Only if you wish to keep Xen 3 code with XEN_COMPAT_030001. IIRC, at
> > > least, Xen 3.0.1 and below should not be supported after NetBSD-5.
> >
> > Why ? Some major linux vendors are still using xen 3.0.x in their
> > distribution.
> 
> If you're talking about RHEL, then this is wrong. RHEL 5.3 have their
> xen tools and xen kernel patched very heavily.
> xen tools are 3.0.1 + thousands of patches
> xen kernel is 3.1.2 + thousands of patches
> 
> All in all, RHEL's xen version is effectively a hybrid of Xen 3.1
> and Xen 3.3.

older RHEL versions are still supported. but maybe dropping XPMAP_OFFSET
is doable. Not that it's going to make things so mych easier, most of its
use is hidden in macros, and Xen3 uses it in only 6 files.

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index