From: Paolo Bonzini <pbonzini@redhat.com>
To: Yuan Yao <yuan.yao@intel.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
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>,
Kai Huang <kai.huang@intel.com>,
Yuan Yao <yuan.yao@linux.intel.com>
Subject: Re: [PATCH 1/1] KVM: x86/mmu: Set memory encryption "value", not "mask", in shadow PDPTRs
Date: Wed, 8 Jun 2022 14:37:27 +0200 [thread overview]
Message-ID: <6a9e17c5-c49a-e5c4-b74b-b8a97f7dc675@redhat.com> (raw)
In-Reply-To: <20220608012015.19566-1-yuan.yao@intel.com>
On 6/8/22 03:20, Yuan Yao wrote:
> Assign shadow_me_value, not shadow_me_mask, to PAE root entries,
> a.k.a. shadow PDPTRs, when host memory encryption is supported. The
> "mask" is the set of all possible memory encryption bits, e.g. MKTME
> KeyIDs, whereas "value" holds the actual value that needs to be
> stuffed into host page tables.
>
> Using shadow_me_mask results in a failed VM-Entry due to setting
> reserved PA bits in the PDPTRs, and ultimately causes an OOPS due to
> physical addresses with non-zero MKTME bits sending to_shadow_page()
> into the weeds:
>
> set kvm_intel.dump_invalid_vmcs=1 to dump internal KVM state.
> BUG: unable to handle page fault for address: ffd43f00063049e8
> PGD 86dfd8067 P4D 0
> Oops: 0000 [#1] PREEMPT SMP
> RIP: 0010:mmu_free_root_page+0x3c/0x90 [kvm]
> kvm_mmu_free_roots+0xd1/0x200 [kvm]
> __kvm_mmu_unload+0x29/0x70 [kvm]
> kvm_mmu_unload+0x13/0x20 [kvm]
> kvm_arch_destroy_vm+0x8a/0x190 [kvm]
> kvm_put_kvm+0x197/0x2d0 [kvm]
> kvm_vm_release+0x21/0x30 [kvm]
> __fput+0x8e/0x260
> ____fput+0xe/0x10
> task_work_run+0x6f/0xb0
> do_exit+0x327/0xa90
> do_group_exit+0x35/0xa0
> get_signal+0x911/0x930
> arch_do_signal_or_restart+0x37/0x720
> exit_to_user_mode_prepare+0xb2/0x140
> syscall_exit_to_user_mode+0x16/0x30
> do_syscall_64+0x4e/0x90
> entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> Fixes: e54f1ff244ac ("KVM: x86/mmu: Add shadow_me_value and repurpose shadow_me_mask")
> Signed-off-by: Yuan Yao <yuan.yao@intel.com>
> Reviewed-by: Kai Huang <kai.huang@intel.com>
> ---
> arch/x86/kvm/mmu/mmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/mmu/mmu.c b/arch/x86/kvm/mmu/mmu.c
> index efe5a3dca1e0..6bd144f1e60c 100644
> --- a/arch/x86/kvm/mmu/mmu.c
> +++ b/arch/x86/kvm/mmu/mmu.c
> @@ -3411,7 +3411,7 @@ static int mmu_alloc_direct_roots(struct kvm_vcpu *vcpu)
> root = mmu_alloc_root(vcpu, i << (30 - PAGE_SHIFT),
> i << 30, PT32_ROOT_LEVEL, true);
> mmu->pae_root[i] = root | PT_PRESENT_MASK |
> - shadow_me_mask;
> + shadow_me_value;
> }
> mmu->root.hpa = __pa(mmu->pae_root);
> } else {
Queued, thanks.
Paolo
next prev parent reply other threads:[~2022-06-08 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 1:20 Yuan Yao
2022-06-08 12:37 ` Paolo Bonzini [this message]
2022-06-08 22:53 ` Yuan Yao
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=6a9e17c5-c49a-e5c4-b74b-b8a97f7dc675@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=yuan.yao@intel.com \
--cc=yuan.yao@linux.intel.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®