All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tang Chen <tangchen@cn.fujitsu.com>
To: Gleb Natapov <gleb@kernel.org>
Cc: Jan Kiszka <jan.kiszka@web.de>, <mtosatti@redhat.com>,
	<nadav.amit@gmail.com>, <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 v2 5/5] kvm, mem-hotplug: Do not pin apic access page in memory.
Date: Tue, 15 Jul 2014 20:28:22 +0800	[thread overview]
Message-ID: <53C51E66.7030208@cn.fujitsu.com> (raw)
In-Reply-To: <20140715120921.GT18167@minantech.com>

On 07/15/2014 08:09 PM, Gleb Natapov wrote:
> On Tue, Jul 15, 2014 at 01:52:40PM +0200, Jan Kiszka wrote:
......
>>
>> I cannot follow your concerns yet. Specifically, how should
>> APIC_ACCESS_ADDR (the VMCS field, right?) change while L2 is running? We
>> currently pin/unpin on L1->L2/L2->L1, respectively. Or what do you mean?
>>
> I am talking about this case:
>           if (cpu_has_secondary_exec_ctrls()) {a
>           } else {
>               exec_control |=
>                  SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES;
>              vmcs_write64(APIC_ACCESS_ADDR,
>                  page_to_phys(vcpu->kvm->arch.apic_access_page));
>           }
> We do not pin here.
>

Hi Gleb,


7905                 if (exec_control & 
SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES) {
......
7912                         if (vmx->nested.apic_access_page) /* 
shouldn't happen */
7913 
nested_release_page(vmx->nested.apic_access_page);
7914                         vmx->nested.apic_access_page =
7915                                 nested_get_page(vcpu, 
vmcs12->apic_access_addr);

I thought you were talking about the problem here. We pin 
vmcs12->apic_access_addr
in memory. And I think we should do the same thing to this page as to L1 
vm.
Right ?

......
7922                         if (!vmx->nested.apic_access_page)
7923                                 exec_control &=
7924 
~SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES;
7925                         else
7926                                 vmcs_write64(APIC_ACCESS_ADDR,
7927 
page_to_phys(vmx->nested.apic_access_page));
7928                 } else if 
(vm_need_virtualize_apic_accesses(vmx->vcpu.kvm)) {
7929                         exec_control |=
7930 
SECONDARY_EXEC_VIRTUALIZE_APIC_ACCESSES;
7931                         vmcs_write64(APIC_ACCESS_ADDR,
7932 
page_to_phys(vcpu->kvm->arch.apic_access_page));
7933                 }

And yes, we have the problem you said here. We can migrate the page 
while L2 vm is running.
So I think we should enforce L2 vm to exit to L1. Right ?

Thanks.

  reply	other threads:[~2014-07-15 12:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 13:01 [PATCH v2 0/5] kvm, mem-hotplug: Do not pin ept identity pagetable and apic access page Tang Chen
2014-07-08 13:01 ` [PATCH v2 1/5] kvm: Add gfn_to_page_no_pin() to translate gfn to page without pinning Tang Chen
2014-07-08 13:01 ` [PATCH v2 2/5] kvm: Use APIC_DEFAULT_PHYS_BASE macro as the apic access page address Tang Chen
2014-07-08 13:01 ` [PATCH v2 3/5] kvm, mem-hotplug: Do not pin ept identity pagetable in memory Tang Chen
2014-07-08 13:01 ` [PATCH v2 4/5] kvm: Remove ept_identity_pagetable from struct kvm_arch Tang Chen
2014-07-09  2:06   ` Tang Chen
2014-07-09  2:08   ` [RESEND PATCH " Tang Chen
2014-07-12  7:44     ` Gleb Natapov
2014-07-14  9:17       ` Tang Chen
2014-07-14 14:27         ` Gleb Natapov
2014-07-15 10:39           ` Tang Chen
2014-07-08 13:01 ` [PATCH v2 5/5] kvm, mem-hotplug: Do not pin apic access page in memory Tang Chen
2014-07-12  8:04   ` Gleb Natapov
2014-07-14  7:57     ` Tang Chen
2014-07-14 14:58       ` Gleb Natapov
2014-07-15 11:52         ` Jan Kiszka
2014-07-15 12:09           ` Gleb Natapov
2014-07-15 12:28             ` Tang Chen [this message]
2014-07-15 12:40               ` Gleb Natapov
2014-07-15 12:54                 ` Tang Chen
2014-07-15 14:40                   ` Gleb Natapov
2014-07-17  9:22                     ` Tang Chen
2014-07-15 13:10                 ` Jan Kiszka
2014-07-15 14:04                   ` Gleb Natapov
2014-07-17 13:34                 ` Tang Chen
2014-07-17 13:57                   ` Gleb Natapov
2014-07-18  9:05                     ` Tang Chen
2014-07-18 11:21                       ` Gleb Natapov
2014-07-15 12:11           ` Tang Chen
2014-07-09  1:20 ` [PATCH v2 0/5] kvm, mem-hotplug: Do not pin ept identity pagetable and apic access page Tang Chen
2014-07-11  6:23 ` Tang Chen

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=53C51E66.7030208@cn.fujitsu.com \
    --to=tangchen@cn.fujitsu.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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.