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: AW: [Xen-devel] PCI bus emulation?

To: "Neugebauer, Rolf" <rolf.neugebauer@xxxxxxxxx>
Subject: Re: AW: [Xen-devel] PCI bus emulation?
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Fri, 5 Aug 2005 01:40:58 +0100
Cc: "Retzki, Sascha \[Xplain\]" <sascha.retzki@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Stefan Berger <stefanb@xxxxxxxxxx>
Delivery-date: Fri, 05 Aug 2005 00:39:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <39CC97884CA19A4D8D6296FE94357BCB02C86867@swsmsx404>
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: <39CC97884CA19A4D8D6296FE94357BCB02C86867@swsmsx404>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.7.1
> > How would config space writes work?  Does Xen 3 understand enough about
> > PCI to
> > implement those itself?
>
> If I remember correctly in 2.0 we don't allow writes to the config space bu
> emulate them through very simple state machine.

IIRC we only emulate those for those parts of config space that describe the 
locations of IO registers - other parts of the config space aren't 
standardised so we have to pass them through.

Cheers,
Mark

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

<Prev in Thread] Current Thread [Next in Thread>