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] [PATCH 0/5] pciback: new configuration space fields, per

On Thu, 2006-04-13 at 17:26 +0100, Keir Fraser wrote:
> xend reads /etc/xen/xend-config.sxp already. I think placing a file in 
> there would be a good idea.
> What do you think about format? File per device type? One file for 
> everything, including devices that are not permissive but have extra 
> filtering rules? One file for permissive ids, and one for devices with 
> extra filtering rules?...

I still need to think about it a bit to see what will work best. My
initial thought was to use s-expressions as the file format and to have
one file for permissive ids and one for the filtering rules (since we
only have one device to support for now). But I'll think about it some
more. I'm not sure what would be a good interface to get this data from
xend to PCI Backend yet...

I'd like to avoid making the PCI Backend dependent on being in the same
domain as xend as it'd be nice to have the option of placing it in its
own driver domain someday. Reading the device's resources through sysfs
and having the permissive flag only in sysfs got away from this goal.
Perhaps having a means to set the permissive flag through XenStore/xend
will correct this issue. Maybe the filtering rules should also get
pushed into the backend through XenStore somehow. I'll need to think
about this some more.


Xen-devel mailing list