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/
Home Products Support Community News


RE: [Xen-devel] Experimental PCI Emulation Layer for XEN x86(32)

To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Experimental PCI Emulation Layer for XEN x86(32)
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Fri, 19 Aug 2005 13:30:08 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 Aug 2005 18:28:24 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282C22@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx> wrote on 08/19/2005 11:47:07 AM:

> > -  The best: Running a domain 0 kernel as a user domain
> > kernel also works ! The bootup messages (dmesg) can be seen
> > under (**) below
> >    - With some further exploration this could be leading to a
> > unified build process and kernel for domain 0 and user
> > domains which I think would be 'good'.
> ? You can already use a xen0 kernel as a xenU kernel just fine. That's
> what al distros do.
> Having two kernels is just for developer's convenience.

I thought that the arch/xen/Kconfig.drivers file was really necessary to build domUs. I guess this is not true then.

> See the -xen default config which compiles everything as modules.

I see.

> Ian
Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>