* Chris Wright ([email protected]) wrote: > * Hao, Xudong ([email protected]) wrote: > > Yes, Chris, thanks your comments. > > How about this one? > > Yes, it gets the locking right.
Sorry, I missed one other problem on the error path. You need to also update pdev->dev.archdata.iommu to NULL (otherwise it is left pointing to freed memory). > Also makes host device and guest assigned device go through the same order: > > alloc_devinfo and init > lock; place info on lists; unlock > domain_context_mapping() > > The patch itself is whitespace damaged and does not apply. Please fix > and feel free to add my: > > Acked-by: Chris Wright <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
