From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Yamahata, Isaku" <isaku.yamahata@intel.com>
Cc: "seanjc@google.com" <seanjc@google.com>,
"Huang, Kai" <kai.huang@intel.com>,
"federico.parola@polito.it" <federico.parola@polito.it>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"isaku.yamahata@gmail.com" <isaku.yamahata@gmail.com>,
"dmatlack@google.com" <dmatlack@google.com>,
"michael.roth@amd.com" <michael.roth@amd.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [PATCH v2 07/10] KVM: x86: Always populate L1 GPA for KVM_MAP_MEMORY
Date: Mon, 15 Apr 2024 19:37:52 +0000 [thread overview]
Message-ID: <245f8011e1f8cccb16a25f080d9521376172f909.camel@intel.com> (raw)
In-Reply-To: <2f1de1b7b6512280fae4ac05e77ced80a585971b.1712785629.git.isaku.yamahata@intel.com>
On Wed, 2024-04-10 at 15:07 -0700, isaku.yamahata@intel.com wrote:
> @@ -5882,18 +5884,40 @@ int kvm_arch_vcpu_map_memory(struct kvm_vcpu *vcpu,
> if (!tdp_enabled)
> return -EOPNOTSUPP;
>
> + /* Force to use L1 GPA despite of vcpu MMU mode. */
> + is_smm = !!(vcpu->arch.hflags & HF_SMM_MASK);
> + if (is_smm ||
> + vcpu->arch.mmu != &vcpu->arch.root_mmu ||
> + vcpu->arch.walk_mmu != &vcpu->arch.root_mmu) {
> + vcpu->arch.hflags &= ~HF_SMM_MASK;
> + mmu = vcpu->arch.mmu;
> + walk_mmu = vcpu->arch.walk_mmu;
> + vcpu->arch.mmu = &vcpu->arch.root_mmu;
> + vcpu->arch.walk_mmu = &vcpu->arch.root_mmu;
> + kvm_mmu_reset_context(vcpu);
> + }
> +
> /* reload is optimized for repeated call. */
After the kvm_mmu_reset_context(), what benefit is there to the operation? And
it happening for every call of kvm_arch_vcpu_map_memory()?
> kvm_mmu_reload(vcpu);
next prev parent reply other threads:[~2024-04-15 19:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 22:07 [PATCH v2 00/10] KVM: Guest Memory Pre-Population API isaku.yamahata
2024-04-10 22:07 ` [PATCH v2 01/10] KVM: Document KVM_MAP_MEMORY ioctl isaku.yamahata
2024-04-15 23:27 ` Edgecombe, Rick P
2024-04-15 23:47 ` Isaku Yamahata
2024-04-17 11:56 ` Paolo Bonzini
2024-04-10 22:07 ` [PATCH v2 02/10] KVM: Add KVM_MAP_MEMORY vcpu ioctl to pre-populate guest memory isaku.yamahata
2024-04-16 14:20 ` Edgecombe, Rick P
2024-04-10 22:07 ` [PATCH v2 03/10] KVM: x86/mmu: Extract __kvm_mmu_do_page_fault() isaku.yamahata
2024-04-16 8:22 ` Chao Gao
2024-04-16 23:43 ` Isaku Yamahata
2024-04-16 14:36 ` Edgecombe, Rick P
2024-04-16 23:52 ` Isaku Yamahata
2024-04-17 15:41 ` Paolo Bonzini
2024-04-10 22:07 ` [PATCH v2 04/10] KVM: x86/mmu: Make __kvm_mmu_do_page_fault() return mapped level isaku.yamahata
2024-04-16 14:40 ` Edgecombe, Rick P
2024-04-16 23:59 ` Isaku Yamahata
2024-04-10 22:07 ` [PATCH v2 05/10] KVM: x86/mmu: Introduce kvm_tdp_map_page() to populate guest memory isaku.yamahata
2024-04-16 14:46 ` Edgecombe, Rick P
2024-04-17 18:39 ` Isaku Yamahata
2024-04-17 7:04 ` Chao Gao
2024-04-17 18:44 ` Isaku Yamahata
2024-04-10 22:07 ` [PATCH v2 06/10] KVM: x86: Implement kvm_arch_vcpu_map_memory() isaku.yamahata
2024-04-16 15:12 ` Edgecombe, Rick P
2024-04-17 7:20 ` Chao Gao
2024-04-17 12:18 ` Paolo Bonzini
2024-04-10 22:07 ` [PATCH v2 07/10] KVM: x86: Always populate L1 GPA for KVM_MAP_MEMORY isaku.yamahata
2024-04-15 19:12 ` Edgecombe, Rick P
2024-04-15 21:17 ` Sean Christopherson
2024-04-15 21:36 ` Edgecombe, Rick P
2024-04-15 22:59 ` Sean Christopherson
2024-04-16 1:49 ` Isaku Yamahata
2024-04-16 14:22 ` Sean Christopherson
2024-04-16 21:41 ` Paolo Bonzini
2024-04-16 23:00 ` Sean Christopherson
2024-04-17 10:28 ` Paolo Bonzini
2024-04-15 19:37 ` Edgecombe, Rick P [this message]
2024-04-16 17:11 ` Edgecombe, Rick P
2024-04-10 22:07 ` [PATCH v2 08/10] KVM: x86: Add a hook in kvm_arch_vcpu_map_memory() isaku.yamahata
2024-04-16 14:57 ` Edgecombe, Rick P
2024-04-17 12:26 ` Paolo Bonzini
2024-04-10 22:07 ` [PATCH v2 09/10] KVM: SVM: Implement pre_mmu_map_page() to refuse KVM_MAP_MEMORY isaku.yamahata
2024-04-10 22:07 ` [PATCH v2 10/10] KVM: selftests: x86: Add test for KVM_MAP_MEMORY isaku.yamahata
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=245f8011e1f8cccb16a25f080d9521376172f909.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=dmatlack@google.com \
--cc=federico.parola@polito.it \
--cc=isaku.yamahata@gmail.com \
--cc=isaku.yamahata@intel.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
Powered by JetHome