> >> > Thank you for reporting it and helping me with the XenStore output to > >> > narrow down the culprit! > >> > >> The thing i don't understand then is: > >> How is it different for the last (or all ) device(s) ? > >> (since the last device (or removing all devices) before doing the > >> assignable-remove doesn't trigger the warning) > >> > >> Or does the complete removal of the pci-part of the tree in xenstore > >> trigger something ? > > > Yup. It removes the whole 'pci' directory in XenStore which triggers > > in Xen pciback the code to deal with that. > So that essentially needs to be changed to watch the individual devices in > the > xenstore tree instead of the whole pci stuff.
Correct. Thought instead of watching it will just compare with what it had assigned to a guest and what it currently has exposed in XenStore. And then whatever is not on the list (exposed in XenStore) is going to be reaped. > Then it all makes sense :-) Until you find another bug :-) > > >> You know if you got a patch cooked up, i'm more than happy to test ! > > > Hehe! > >> > >> -- > >> Sander > >> > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
