From: Sean Christopherson <seanjc@google.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Sean Christopherson <seanjc@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] KVM: VMX: More brown paper bags! NOM NOM NOM
Date: Fri, 8 Apr 2022 20:28:15 +0000 [thread overview]
Message-ID: <20220408202815.386932-1-seanjc@google.com> (raw)
Add a missing declaration that got dropped between my inline patch[1] and
what actually got posted[2].
In file included from arch/x86/kvm/mmu/mmu.c:4279:
arch/x86/kvm/mmu/paging_tmpl.h: In function ‘ept_walk_addr_generic’:
arch/x86/kvm/mmu/paging_tmpl.h:496:50: error: ‘EPT_VIOLATION_RWX_SHIFT’ undeclared
(first use in this function); did you mean ‘EPT_VIOLATION_RWX_MASK’?
496 | EPT_VIOLATION_RWX_SHIFT;
| ^~~~~~~~~~~~~~~~~~~~~~~
| EPT_VIOLATION_RWX_MASK
[1] https://lore.kernel.org/all/Yj0NOQOYEAG+Dz7+@google.com
[2] https://lore.kernel.org/all/20220329030108.97341-3-darcy.sh@antgroup.com
Fixes: 68ca1f59584e ("KVM: x86/mmu: Derive EPT violation RWX bits from EPTE RWX bits")
Signed-off-by: Sean Christopherson <seanjc@google.com>
---
Please squash, thanks!
arch/x86/include/asm/vmx.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/vmx.h b/arch/x86/include/asm/vmx.h
index 46bc7072f6a2..6c343c6a1855 100644
--- a/arch/x86/include/asm/vmx.h
+++ b/arch/x86/include/asm/vmx.h
@@ -543,6 +543,7 @@ enum vm_entry_failure_code {
#define EPT_VIOLATION_ACC_READ_BIT 0
#define EPT_VIOLATION_ACC_WRITE_BIT 1
#define EPT_VIOLATION_ACC_INSTR_BIT 2
+#define EPT_VIOLATION_RWX_SHIFT 3
#define EPT_VIOLATION_GVA_IS_VALID_BIT 7
#define EPT_VIOLATION_GVA_TRANSLATED_BIT 8
#define EPT_VIOLATION_ACC_READ (1 << EPT_VIOLATION_ACC_READ_BIT)
base-commit: 59d9e75d641565603e7c293f4cec182d86db8586
--
2.35.1.1178.g4f1659d476-goog
reply other threads:[~2022-04-08 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220408202815.386932-1-seanjc@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®