Skip to content
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

pcie_check: will continue instead of return if PCI cap is 0xff #401

Merged
merged 3 commits into from
Sep 13, 2024

Conversation

xupengfe
Copy link
Contributor

@xupengfe xupengfe commented Sep 9, 2024

Will continue instead of return if PCI cap is 0xff. Add more description info for pcie check.

Reported-by: Yi Lai [email protected]

Will continue instead of return if PCI cap is 0xff.
Add more description info for pcie check.

Reported-by: Yi Lai <[email protected]>
Signed-off-by: Pengfei Xu <[email protected]>
@xupengfe
Copy link
Contributor Author

xupengfe commented Sep 9, 2024

All " WARNING: Prefer kstrto to single variable sscanf", it's user space code, so this warning is useless.

Thanks!

Add the judgment that PCI capability is 0, it will not show unavailable PCI
or PCIe info in the list.

Reported-by: Yi Lai <[email protected]>
Signed-off-by: Pengfei Xu <[email protected]>
Remove MMIO base address detection by dmesg way, because in CXL QEMU
environment, dmesg shows incorrect MMIO base address "0xffc00000":
"
[    0.000000] efi: Remove mem128: MMIO range=[0xffc00000-0xffffffff] (4MB) from e820 map
"
And use MCFG way directly and it could detect correct MMIO base address
"0xe0000000" for CXL QEMU environment.

Signed-off-by: Pengfei Xu <[email protected]>
@ysun ysun merged commit 54ecaf1 into intel:main Sep 13, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants