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.

Sign up for GitHub

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

Jump to bottom

[Feature] Add Process Context Identifier (PCID) support #319

Open
wipawel opened this issue Nov 4, 2023 · 0 comments
Open

[Feature] Add Process Context Identifier (PCID) support #319

wipawel opened this issue Nov 4, 2023 · 0 comments
Assignees
@sktt
Labels
feature New feature or request improvement A small enhancement, that makes already implemented features better Priority: 3 Regular feature

Comments

@wipawel
Copy link
Contributor

wipawel commented Nov 4, 2023

Is your feature request related to a problem? Please describe.

Modern x86 CPUs have support for PCID for each individual address space for different tasks and contexts. Add support for it to further enhance KTF's TLB performance optimization (again quite irrelevant), but also enable new tests.

Describe the solution you'd like

Add function to enable PCID via setting CR4.PCIDE and kernel cmdline option to control enablement of the feature.
Add allocation, deallocation and maintenance functionality for active/inactive PCIDs. Preferably via existing bitmap API and a single 4K frame allocation (PCID space is 12bit wide).
Make sure each contexts has individual PCID allocated and used.
@wipawel wipawel added feature New feature or request improvement A small enhancement, that makes already implemented features better Priority: 3 Regular feature labels Nov 4, 2023
@sktt sktt self-assigned this Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sktt sktt

Labels
feature New feature or request improvement A small enhancement, that makes already implemented features better Priority: 3 Regular feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sktt @wipawel