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] Move some of the PCI device manage/control into pciback?

To: Shohei Fujiwara <fujiwara-sxa@xxxxxxxxxxxxxxx>, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Subject: Re: [Xen-devel] Move some of the PCI device manage/control into pciback?
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 15 Jan 2009 11:04:43 +0000
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 15 Jan 2009 03:04:50 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090115191318.2D5A.CB716985@xxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acl3ARGOElD8xodYiEqGOngli7SaRw==
Thread-topic: [Xen-devel] Move some of the PCI device manage/control into pciback?
User-agent: Microsoft-Entourage/12.15.0.081119
On 15/01/2009 10:17, "Shohei Fujiwara" <fujiwara-sxa@xxxxxxxxxxxxxxx> wrote:

> In case of HVM domain with stub domain, I'm considering direct access
> from ioemu to configuration space.  We can achieve this by mapping the
> subset of MMCFG to stub domain. This will improve the scalability of PCI
> pass-through and reduce the responsibility of dom0.
> 
> My model is the following.
> 
>     1. PCI back driver resets the device and setups it.
>     2. PCI back driver passes the responsibility of configuration
>        space of device to ioemu.
>     3. Ioemu reads/writes configuration space of the device,
>        responding guest OS.
>     4. When ioemu exits, pci back driver gets the responsibility of
>        configuration space of device.
>     5. PCI back driver resets device (and put D3hot state if possible)
> 
> As you know, current xend reads/writes configuration space. If xend
> doesn't reads/writes, the architecture becomes simpler.
> 
> What do you think about this?

I'd rather have all accesses mediated through pciback. I don't think PCI
config accesses should be on any data path anyway, and you've already taken
the hit of trapping to qemu in that case.

 -- Keir



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