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] PCI delegation works, access to the delegated NIC doesn'


On 8 Mar 2006, at 23:05, Ryan wrote:

That is true. However, it seems to me that most people don't put the
driver alone in the driver domain. Rather, they put the device in a domU
they wish to run many applications in. If the domain is compromised, an
attacker could cause a *little* bit of havoc on the pci bus (affecting
devices in other domains) by messing with registers like the BARs or
possibly DoS other devices by changing the interrupt pin.

I guess that is true for some users, even though it was never our model for driver domains. Of course the BARs are actually off limits, since you have explicit handlers for those. :-) But your point is taken. Having explicit handlers at least for some common devices is not a bad idea, to allow some common system configurations to run without needing to set permissive mode.

 -- Keir


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