| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH 0/5] pciback: new configuration space fields, per
On 13 Apr 2006, at 16:40, Ryan wrote:
, I thought that someday when MSI is supported in Xen, perhaps
the driver domain's interface for setting up MSI for a device could
happen through these virtual configuration space fields (although I'm
not familiar enough with MSI to know if that is feasible or not)).
For the specific example of MSI this will not happen --- MSI will be
configured (or not) at bind time by domain 0. We will not run the MSI
driver at all outside domain 0 (I need to work out how to arrange for
the MSI driver to not activate outside domain0 though).
Is it appropriate for xend to read/write a configuration file? xend's
clients (xm) are the ones that do the processing of config. files now
and I wasn't sure if it was acceptable to have xend reach into a
configuration file (say /etc/xen/pci_permissive_ids.conf). I believe it
must happen on xend, but if it's not hard-coded in, what would be the
appropriate place to read the config file from?
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?...
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home