[Xen-devel] Re: [PATCH][RFC] fix some spinlock issues in vmsi

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 06/03/2009 17:43, "Qing He" <qing.he@xxxxxxxxx> wrote:

>> Do you mean deinitialised and unloaded the device driver?
> 
> Yes, the racey condition we just talked happens here. Consider
> the following case, when remove_pci_device is called, the device
> data structure is removed by the hypervisor. But there is no
> guarauntee in the hypervisor that guest already has knowledge,
> for example the guest may continue to access the device resources.
> It's in this case msixtbl_{read,write} has a little racey condition.
> 
> I don't think this scenario is desirable, but does it happen in the
> current logic?

Uh, well since dom0 is in fact mostly in charge of PCI access, there's not
much we can do in Xen to enforce this. At that level we kind of have to
assume that dom0 has sequenced hotplug/hotunplug sensibly.

 -- Keir



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