Closed adlazar closed 4 years ago
@adlazar the kvmi-v7
has been pushed based on this PR.
I changed the base to this branch, so it doesn't create any conflict.
Now, we only have the changes to libkvmi.c: new functions for SPP, EPT-views, VMFUNC, #VE, two bug-fixes and a small documentation update.
@adlazar I think I had a better idea for people to view the changes from this PR.
I will rewrite the branch that I have already pushed (kvmi-v7
) to point to your base commit: cff670b3eb68257029e2977a6bfeac7d9b829e9a
(v5.4.24
).
Therefore in this PR we will see your commits only, without those from the KVM/Linux community. What do you think ?
Basically:
git branch -f kvmi-v7 cff670b3eb68257029e2977a6bfeac7d9b829e9a
git push origin kvmi-v7 --force
Great!
Okay, this looks much better now.
We can see your 190
commits on top of 5.4.24
@adlazar can I merged this PR, or you are still adding new commits as kvmi-v7
and you prefer to keep it opened ?
@Wenzel, you can merge this PR, thanks.
This PR has the basic introspection patches kvmi-v7 submitted on kvm list with some fixes on top of Linux 5.4.24 (commit cff670b3eb68, tag v5.4.24 from git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git), plus:
The kernel KVMI headers from tools/kvm/kvmi are kept in the kvmi-v6 format (eg. kvmi_inject_exception instead of kvmi_vcpu_inject_exception). However, one structure is not binary compatible (kvmi_event_trap) and you need to rebuild the userspace tools or change the headers used to build the kernel.
I didn't test the kvmi_test.c tool yet.