Re: unbind xen3 frontend drivers

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Sat, Oct 25, 2008 at 08:41:32PM +0200, Christoph Egger wrote:
> Manuel Bouyer wrote:
> > On Sat, Oct 25, 2008 at 12:43:43PM +0200, Jean-Yves Migeon wrote:
> >> Christoph Egger wrote:
> >>> Xen supports ia64 aside of x86. It allows to run
> >>> both HVM and PV guests.
> >>> HVM guests may also use PV drivers.
> >>>
> >>> In order to make PV drivers available for NetBSD
> >>> as HVM guest, I have to unbind the xen3 frontend
> >>> drivers from the PV guest only context.
> >>>
> >>> This means, I need to move the following files
> >>> into a seperate directory:
> >>>
> >>> if_xennet_xenbus.c
> >>> xbd_xenbus.c
> >>> xennet_checksum.c
> >>>
> >>> In my working tree, I moved them to
> >>> sys/arch/xen/dev
> >>>
> >>> Is this directory ok or
> >>> should I move them
> >>> to sys/dev/xen/xen and xenbus to sys/dev/xen/xenbus ?
> >> While I am not the one who can make this decision, I prefer to have MI 
> >> code under sys/dev/xen.
> >>
> >> Thing is, take if_xennet_xenbus.c for example, it relies on MD 
> >> functions, like x86 barriers and P2M translations. As a consequence, I 
> >> am not sure that sys/dev/xen is a good candidate; it stays pretty close 
> >> to x86, and not suitable for sys/dev/xen yet.
> > 
> > Yes, the code in arch/xen/xen is not ready to be MI yet (although I tried to
> > not put too much MD code in there) ... I'd prefer to keep in arch/xen
> > for now, and I can't see a need to move it to arch/xen/dev at this time.
> 
> That's mainly because I need a files.xendev to use for non-XEN kernel
> configs.

It could be in xen/conf for now.

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