On 2014/8/25 17:15, Joerg Roedel wrote:
> [Adding the Emulex driver developers to Cc for some input on the device,
> and why it might use wrong request ids]
Thanks!
>
> On Mon, Aug 25, 2014 at 02:44:59PM +0800, Yijing Wang wrote:
>> We found some strange devices in HP C7000 and Huawei Storage Server. These
...
>> [ 1438.703851] DMAR:[fault reason 02] Present bit in context entry is clear
>>
>> This patch add a kernel boot command parameter iommu=pt_force=domain:busnum
>> that based iommu identity mapping and force to create identity for all devfn
>> in
>> the specific bus number to fix this issue.
>
> No! If the device really uses request-ids it shouldn't use please add a
> DMA alias quirk instead. A new kernel parameter will not work out of the
> box for other users of this device.
Hi Joerg, It seems not wrong request id of the physical device.
Because I configured the eth4(pci id is 04:00.1), and the network is good, no
problems found.
If eth4(04:00.1) use the wrong request-id, I think network dma should be
blocked by IOMMU, but it not.
So I don't know where the request-id 04:00.4/5/6/7 come from. Maybe Sathya can
help me to find that. :)
\-[0000:00]-+-00.0 Intel Corporation Xeon E5/Core i7 DMI2
+-01.0-[11]--
+-01.1-[02]--
+-02.0-[04]--+-00.0 Emulex Corporation OneConnect 10Gb NIC (be3)
| +-00.1 Emulex Corporation OneConnect 10Gb NIC (be3)
| +-00.2 Emulex Corporation OneConnect 10Gb iSCSI
Initiator (be3)
| \-00.3 Emulex Corporation OneConnect 10Gb iSCSI
Initiator (be3)
>
>
> Joerg
>
>
> .
>
--
Thanks!
Yijing
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
