-
Notifications
You must be signed in to change notification settings - Fork 489
the output of pcm-iio on EMR may not be correct #946
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Are you using the latest version of pcm? |
Yes, the latest version also has such issue. |
we have a fix which should be merged soon |
fixed in the master branch now |
I tried the latest master. It includes the fixings mentioned above. But the issue is still there. |
@wangyi4 thank you for your feedback. Could you please share the current output from your system and the expected output from your point of view? |
The output is the same as what I reported before. |IIO Stack 0 - IDX0 |IB write|IB read|OB read|OB write|IOTLB Lookup|IOTLB Miss|Ctxt Cache Hit|256T Cache Hit|512G Cache Hit|1G Cache Hit|2M Cache Hit|IOMMU Mem Access| Correct me if my understanding is wrong. On GNR-SP , I saw QAT was connected to HCx. |IIO Stack 1 - HCx0 |IB write|IB read|OB read|OB write|IOTLB Lookup|IOTLB Miss|Ctxt Cache Hit|256T Cache Hit|512G Cache Hit|1G Cache Hit|2M Cache Hit|IOMMU Mem Access| |
Hi @wangyi4, |
I ran pcm-iio on EMR6554s. It seems the output from pcm-iio program is not correct. QAT are connected to PCIe1 and PCIe4.
|IIO Stack 4 - PCIe1 |
|0000:6F:01.0|Gen0 x0 |8086:0B25 Intel Corporation unknown device; Part: 0, 1, 2, ��
|0000:70:00.0|Gen1 x1 |8086:4940 Intel Corporation 4xxx Series QAT; Part: 4, ��
|0000:72:00.0|Gen0 x0 |8086:2710 Intel Corporation unknown device; Part: 5, ��
|IIO Stack 9 - PCIe4|
|0000:79:01.0|Gen0 x0 |8086:0B25 Intel Corporation unknown device; Part: 0, 1, 2, ��
|0000:7A:00.0|Gen1 x1 |8086:4940 Intel Corporation 4xxx Series QAT; Part: 4, ��
|0000:7C:00.0|Gen0 x0 |8086:2710 Intel Corporation unknown device; Part: 5, ��
The text was updated successfully, but these errors were encountered: