Port-xen archive

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

Re: Xen headers: Update to Xen 3.3 headers



On Thu, Aug 21, 2008 at 12:58:10AM +0200, Christoph Egger wrote:
> >then this has to be documented, in the same way I've (just) documented that
> >Xen 2.0.x is deprecated.
> 
> Looking into pkgsrc, w/o the Xen2 packages Xen 3.1. are the oldest ones.
> Why don't we have Xen 3.1 hypercalls implicitely with the deprecation of
> Xen 2 ?

Because there may be NetBSD guests running on linux dom0 with a Xen 3.0.x
hypervisor. There are still linux distribs shipping and maintaining
xen 3.0.x.

> 
> BTW: Which format is this src/distrib/notes/common/main using?

troff

> How do I view the content?

I think 'make' in src/distrib/notes will generate the files (text, html and
ps formats). Or grab the install notes from one of the autobuild
output :)

> 
> >>[...]
> >>>I don't think will make the same thing. Specifically, I don't think 
> >>>barrier
> >>>will prevent the compiler from caching a memory value in a register;
> >>>this is what volatile is for. Unless I missed a compiler directive which
> >>>would do that, we need to keep the volatile here.
> >>Ok, I will try again getting this upstream.
> >
> >Or keep it in our tree if they don't want it.
> >
> >>>>[...]
> >>>>    Therefore, the attached patch as a standalone breaks the build of 
> >>>>    the
> >>>>    xbd backend driver. There's a need for a second patch which re-adds 
> >>>>    the
> >>>>    missing structures in a NetBSD/Xen MD header similar to what is 
> >>>>    Linux
> >>>>    doing to keep things building.
> >>>I don't like it; if we go this route it should be inclued from one of the
> >>>existing MD header in xen3-public/
> >>How should I explain that XenSource ?
> >
> >Why explain to them ? it's our source tree, we can keep local files or
> >local patches if we want, isn't it ?
> 
> Sure, I just wanted to make the required effort for updating the headers
> as small as possible - in particular the merging part.

merging isn't so hard when using the CVS vendor branch, and the changes
are constrained to a few portion of files.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--


Home | Main Index | Thread Index | Old Index