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

x86 fails all tests if CONFIG_X86_KPTI is disabled #29175

Closed
andrewboie opened this issue Oct 13, 2020 · 0 comments · Fixed by #29411
Closed

x86 fails all tests if CONFIG_X86_KPTI is disabled #29175

andrewboie opened this issue Oct 13, 2020 · 0 comments · Fixed by #29411
Assignees
Labels
area: Memory Protection area: X86 x86 Architecture (32-bit) area: X86_64 x86-64 Architecture (64-bit) bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug

Comments

@andrewboie
Copy link
Contributor

andrewboie commented Oct 13, 2020

Describe the bug
If kernel page table isolation (KPTI) is disabled, the memory management code doesn't work. This may have been bit-rotten for a while, we were lacking test coverage.

To Reproduce
This PR illustrates the problem:
#28800

Build tests with the new qemu_x86_nokpti or qemu_x86_64_nokpti targets.

Expected behavior
All tests pass.

Impact
x86 CPUs not susceptible to Meltdown cannot disable this feature and enjoy the considerable performance benefits.

@andrewboie andrewboie added bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug area: X86 x86 Architecture (32-bit) area: Memory Protection area: X86_64 x86-64 Architecture (64-bit) labels Oct 13, 2020
@andrewboie andrewboie self-assigned this Oct 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Memory Protection area: X86 x86 Architecture (32-bit) area: X86_64 x86-64 Architecture (64-bit) bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant