tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: basic support for (software concept) "pci domains" in the MI pci code

Manuel Bouyer wrote:
> On Sun, Aug 23, 2009 at 11:39:23PM +0200, Christoph Egger wrote:
>> Manuel Bouyer wrote:
>>> On Mon, Aug 24, 2009 at 05:06:07AM +1000, matthew green wrote:
>>>> when constructing a "unique" name the card.  my understanding is
>>>> that xen wants to have a domain concept available for both
>>>> presenting a full topology to the userland as well as helping pci
>>>> passthru, but i do not really understand what the use there is.
>>> AFAIK Xen doesn't need it, it just wants access to the different PCI
>>> busses. It just needs to uniquely identify a device, the autoconf
>>> index of the parent is enough for this.
>> Manuel: How do you enlist all PCI devices in userland to be used in
>> xen python code ?
> something like:
> for i in /dev/pci*; do
>     pcictl $i list
> done
> This is basically what the patch in xentools3 does for PCI access.

What does 'xm pci-list' and 'xm pci-list-assignable-devices' print
on your machines ?


Home | Main Index | Thread Index | Old Index