WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] Problem access hardware with xen 3.0 unstable

To: Manuel Bernhardt <mailinglist@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Problem access hardware with xen 3.0 unstable
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 8 Oct 2005 11:49:15 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 08 Oct 2005 10:41:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43479BEC.2020302@xxxxxxxxxxx>
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>
References: <4346E3E6.6090507@xxxxxxxxxxx> <33c739e861969414035002017fb56184@xxxxxxxxxxxx> <43479BEC.2020302@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 8 Oct 2005, at 11:14, Manuel Bernhardt wrote:

Also when i boot an domain with dom0 kernel instead domU kernel ?

manuel

I'm afraid so. We currently have no interface for unprivileged domains to access PCI space. If we gave a domU unfettered access to PCI space and BIOS tables there would be a big conflict betwene that domain and domain0.

This isn't going to be very hard to fix, but stabilisation and domU interface freezes come first.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel