From: Paolo Bonzini <pbonzini@redhat.com>
To: Tang Chen <tangchen@cn.fujitsu.com>,
gleb@kernel.org, mtosatti@redhat.com, nadav.amit@gmail.com,
jan.kiszka@web.de
Cc: kvm@vger.kernel.org, laijs@cn.fujitsu.com,
isimatu.yasuaki@jp.fujitsu.com, guz.fnst@cn.fujitsu.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 7/7] kvm, mem-hotplug: Unpin and remove nested_vmx->apic_access_page.
Date: Thu, 11 Sep 2014 11:33:35 +0200 [thread overview]
Message-ID: <54116C6F.8030300@redhat.com> (raw)
In-Reply-To: <1410413886-32213-8-git-send-email-tangchen@cn.fujitsu.com>
Il 11/09/2014 07:38, Tang Chen ha scritto:
> Just like we removed kvm_arch->apic_access_page, nested_vmx->apic_access_page
> becomes useless for the same reason. This patch removes nested_vmx->apic_access_page,
> and use gfn_to_page() to pin it in memory when we need it, and unpin it after then.
>
> Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
> ---
> arch/x86/kvm/vmx.c | 31 +++++++++----------------------
> 1 file changed, 9 insertions(+), 22 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 058c373..4aa73cb 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -374,11 +374,6 @@ struct nested_vmx {
> u64 vmcs01_tsc_offset;
> /* L2 must run next, and mustn't decide to exit to L1. */
> bool nested_run_pending;
> - /*
> - * Guest pages referred to in vmcs02 with host-physical pointers, so
> - * we must keep them pinned while L2 runs.
> - */
> - struct page *apic_access_page;
> u64 msr_ia32_feature_control;
>
> struct hrtimer preemption_timer;
> @@ -6154,11 +6149,6 @@ static void free_nested(struct vcpu_vmx *vmx)
> nested_release_vmcs12(vmx);
> if (enable_shadow_vmcs)
> free_vmcs(vmx->nested.current_shadow_vmcs);
> - /* Unpin physical memory we referred to in current vmcs02 */
> - if (vmx->nested.apic_access_page) {
> - nested_release_page(vmx->nested.apic_access_page);
> - vmx->nested.apic_access_page = 0;
> - }
>
> nested_free_all_saved_vmcss(vmx);
> }
> @@ -7983,28 +7973,31 @@ static void prepare_vmcs02(struct kvm_vcpu *vcpu, struct vmcs12 *vmcs12)
> exec_control |= vmcs12->secondary_vm_exec_control;
>
> if (exec_control & SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES) {
> + struct page *page;
> /*
> * Translate L1 physical address to host physical
> * address for vmcs02. Keep the page pinned, so this
> * physical address remains valid. We keep a reference
> * to it so we can release it later.
> */
> - if (vmx->nested.apic_access_page) /* shouldn't happen */
> - nested_release_page(vmx->nested.apic_access_page);
> - vmx->nested.apic_access_page =
> - nested_get_page(vcpu, vmcs12->apic_access_addr);
> + page = nested_get_page(vcpu, vmcs12->apic_access_addr);
> /*
> * If translation failed, no matter: This feature asks
> * to exit when accessing the given address, and if it
> * can never be accessed, this feature won't do
> * anything anyway.
> */
> - if (!vmx->nested.apic_access_page)
> + if (!page)
> exec_control &=
> ~SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES;
> else
> vmcs_write64(APIC_ACCESS_ADDR,
> - page_to_phys(vmx->nested.apic_access_page));
> + page_to_phys(page));
> + /*
> + * Do not pin nested vm's apic access page in memory so
> + * that memory hotplug process is able to migrate it.
> + */
> + put_page(page);
> } else if (vm_need_virtualize_apic_accesses(vmx->vcpu.kvm)) {
> struct page *page = gfn_to_page(vmx->vcpu.kvm,
> APIC_DEFAULT_PHYS_BASE >> PAGE_SHIFT);
> @@ -8807,12 +8800,6 @@ static void nested_vmx_vmexit(struct kvm_vcpu *vcpu, u32 exit_reason,
> /* This is needed for same reason as it was needed in prepare_vmcs02 */
> vmx->host_rsp = 0;
>
> - /* Unpin physical memory we referred to in vmcs02 */
> - if (vmx->nested.apic_access_page) {
> - nested_release_page(vmx->nested.apic_access_page);
> - vmx->nested.apic_access_page = 0;
> - }
> -
> /*
> * Do not call kvm_reload_apic_access_page() because we are now
> * running, mmu_notifier will force to reload the page's hpa for L2
>
This patch is not against the latest KVM tree. The call to
nested_get_page is now in nested_get_vmcs12_pages, and you have to
handle virtual_apic_page in a similar manner.
Paolo
next prev parent reply other threads:[~2014-09-11 9:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 5:37 [PATCH v5 0/7] kvm, mem-hotplug: Do not pin ept identity pagetable and apic access page Tang Chen
2014-09-11 5:38 ` [PATCH v5 1/7] kvm: Use APIC_DEFAULT_PHYS_BASE macro as the apic access page address Tang Chen
2014-09-11 9:10 ` Paolo Bonzini
2014-09-11 5:38 ` [PATCH v5 2/7] kvm: Remove ept_identity_pagetable from struct kvm_arch Tang Chen
2014-09-11 9:14 ` Paolo Bonzini
2014-09-11 5:38 ` [PATCH v5 3/7] kvm: Make init_rmode_identity_map() return 0 on success Tang Chen
2014-09-11 9:17 ` Paolo Bonzini
2014-09-11 10:26 ` tangchen
2014-09-11 5:38 ` [PATCH v5 4/7] kvm, mem-hotplug: Reload L1' apic access page on migration in vcpu_enter_guest() Tang Chen
2014-09-11 9:21 ` Paolo Bonzini
2014-09-11 10:12 ` Gleb Natapov
2014-09-11 10:47 ` Paolo Bonzini
2014-09-11 11:30 ` Gleb Natapov
2014-09-11 13:05 ` Paolo Bonzini
2014-09-11 13:59 ` Gleb Natapov
2014-09-11 14:06 ` Paolo Bonzini
2014-09-11 14:21 ` Gleb Natapov
2014-09-11 14:24 ` Paolo Bonzini
2014-09-11 14:31 ` Gleb Natapov
2014-09-11 14:37 ` Paolo Bonzini
2014-09-11 14:47 ` Gleb Natapov
2014-09-12 3:32 ` tangchen
2014-09-12 3:36 ` tangchen
2014-09-11 10:20 ` tangchen
2014-09-11 10:39 ` Paolo Bonzini
2014-09-11 5:38 ` [PATCH v5 5/7] kvm, mem-hotplug: Reload L1's apic access page on migration when L2 is running Tang Chen
2014-09-11 9:28 ` Paolo Bonzini
2014-09-11 5:38 ` [PATCH v5 6/7] kvm, mem-hotplug: Unpin and remove kvm_arch->apic_access_page Tang Chen
2014-09-11 9:34 ` Paolo Bonzini
2014-09-11 5:38 ` [PATCH v5 7/7] kvm, mem-hotplug: Unpin and remove nested_vmx->apic_access_page Tang Chen
2014-09-11 9:33 ` Paolo Bonzini [this message]
2014-09-11 9:43 ` tangchen
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=54116C6F.8030300@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=tangchen@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).