From mboxrd@z Thu Jan 1 00:00:00 1970 From: tangchen Subject: Re: [PATCH v3 6/6] kvm, mem-hotplug: Reload L1's apic access page if it is migrated when L2 is running. Date: Tue, 29 Jul 2014 18:56:54 -0400 Message-ID: <53D826B6.6010804@cn.fujitsu.com> References: <1406144530-23002-1-git-send-email-tangchen@cn.fujitsu.com> <1406144530-23002-7-git-send-email-tangchen@cn.fujitsu.com> <53D36A51.1050000@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-15"; format=flowed Content-Transfer-Encoding: 7bit Cc: , , , , , To: Jan Kiszka , , , Return-path: Received: from cn.fujitsu.com ([59.151.112.132]:38280 "EHLO heian.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752841AbaG2K5P (ORCPT ); Tue, 29 Jul 2014 06:57:15 -0400 In-Reply-To: <53D36A51.1050000@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On 07/26/2014 04:44 AM, Jan Kiszka wrote: > On 2014-07-23 21:42, Tang Chen wrote: >> This patch only handle "L1 and L2 vm share one apic access page" situation. >> >> When L1 vm is running, if the shared apic access page is migrated, mmu_notifier will >> request all vcpus to exit to L0, and reload apic access page physical address for >> all the vcpus' vmcs (which is done by patch 5/6). And when it enters L2 vm, L2's vmcs >> will be updated in prepare_vmcs02() called by nested_vm_run(). So we need to do >> nothing. >> >> When L2 vm is running, if the shared apic access page is migrated, mmu_notifier will >> request all vcpus to exit to L0, and reload apic access page physical address for >> all L2 vmcs. And this patch requests apic access page reload in L2->L1 vmexit. > Shouldn't this patch come before we allow apic access page migration? Yes, it should come before patch 5. Thanks.