RE: [PATCH] iommu/vt-d: Handle hotplug devices' default identity mapping setting

2019-02-24 Thread James Dong via iommu
Baolu: Yes, it is a generic issue for hotplug devices with current Intel IOMMU driver, as reported in this thread as well. The patch you provided does the job in our case. Please update this thread once your patch is merged. Thanks. Best Regards, James On 2/23/19 12:56 AM, Lu Baolu wrote > >

RE: [PATCH] iommu/vt-d: Handle hotplug devices' default identity mapping setting

2019-02-22 Thread James Dong via iommu
Baolu: The reproduction depends on devices. HW passthrough PCIe devices with default identity map could have the issue. Make sure that messages like following came out in dmesg and their mapping does not change after booting: [ 10.167809] DMAR: Hardware identity mapping for device

RE: [PATCH] iommu/vt-d: Handle hotplug devices' default identity mapping setting

2019-02-21 Thread James Dong via iommu
Baolu: Sorry that my last reply email seems not text format. Resend it now. Thanks for your comments and your patch. Please find below our responses to each of your comments: > What does "I/O operation won't work" exactly mean here? Do you see any > IOMMU fault message? Or, something doesn't

Re: [PATCH] iommu/vt-d: Handle hotplug devices' default identity mapping setting

2019-02-21 Thread James Dong via iommu
Baolu: Thanks for your comments and your patch. Please find below our responses to each of your comments: > What does "I/O operation won't work" exactly mean here? Do you see any > IOMMU fault message? Or, something doesn't work as expected? Yes, DMAR fault messages as following came out: [

[PATCH] iommu/vt-d: Handle hotplug devices' default identity mapping setting

2019-02-21 Thread James Dong via iommu
With specific Linux command line option such as "iommu=pt", some types of hotplug devices will be assigned to the static 1:1 iommu domain by default during kernel init. If such a hotplug device is rescanned after being removed, for example, with following sample commands: echo 1 >