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

tdx-compliance: kprobe #320

Merged
merged 2 commits into from
Jul 11, 2024
Merged

tdx-compliance: kprobe #320

merged 2 commits into from
Jul 11, 2024

Conversation

haoliang-Zhu
Copy link
Contributor

  1. Use the kprobe method to capture the return value of handle_cpuid, and determine whether #VE or #GP is triggered based on the return value.
  2. Also can modify the detection functions, such as hanlde_cpuid, read_msr, write_msr, handle_mmio, handle_io, etc. Only need to modify the value of .kp.symbol_name.

1. Use the kprobe method to capture the return value of handle_cpuid, and determine whether #VE or #GP is triggered based on the return value.
2. Also can modify the detection functions, such as hanlde_cpuid, read_msr, write_msr, handle_mmio, handle_io, etc. Only need to modify the value of .kp.symbol_name.

Signed-off-by: Haoliang Zhu <[email protected]>
1. Dynamic registration of kretprobe.
2. Trigger cupid in kernel space.
3. Dump the number of VE and GP triggered by cpuid in dmesg.
4. Improve the readme and fix some compiled warnings.

Signed-off-by: Haoliang Zhu <[email protected]>
@haoliang-Zhu haoliang-Zhu force-pushed the tdx-compliance-kprobe branch from 7cfd742 to 606df6b Compare July 10, 2024 08:11
@ysun ysun merged commit 2b9c893 into intel:main Jul 11, 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