Extend ept_access_test_execute_only to cover MBEC EPT --x case, with the caveat that it doesn't actually work as expected. Need a hand with sanity checking this, as both of the commented out test cases produce a tight EPT violation loop on the kernel side, and I'm unsure as of yet if its a test side issue (setup?) or what. Tests pass with both -vmx-mbec and +vmx-mbec (for the case that isn't commented out) Signed-off-by: Jon Kohler --- x86/vmx_tests.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/x86/vmx_tests.c b/x86/vmx_tests.c index e869d702..3705e2ca 100644 --- a/x86/vmx_tests.c +++ b/x86/vmx_tests.c @@ -2856,6 +2856,14 @@ static void ept_access_test_execute_only(void) ept_access_violation(EPT_EA, OP_WRITE, EPT_VLT_WR | EPT_VLT_PERM_EX); ept_access_allowed(EPT_EA, OP_EXEC); + if (is_mbec_supported()) { + // FIXME: this does not produce the expected + // EPT violation, instead we get assert: + // Expected VMX_EPT_VIOLATION, got VMX_VMCALL + // ept_access_violation(EPT_EA, OP_EXEC_USER, + // EPT_VLT_FETCH | + // EPT_VLT_PERM_EX); + } } else { ept_access_misconfig(EPT_EA); } -- 2.43.0