From: Tang Chen <tangchen@cn.fujitsu.com>
To: <gleb@kernel.org>, <mtosatti@redhat.com>
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: [PATCH 0/4] kvm, mem-hotplug: Do not pin ept identity pagetable and apic access page.
Date: Wed, 2 Jul 2014 17:00:12 +0800 [thread overview]
Message-ID: <1404291616-15007-1-git-send-email-tangchen@cn.fujitsu.com> (raw)
Hi Gleb, Marcelo,
Please help to review this patch-set.
NOTE: This patch-set doesn't work properly.
ept identity pagetable and apic access page in kvm are pinned in memory.
As a result, they cannot be migrated/hot-removed.
But actually they don't need to be pinned in memory.
This patch-set introduces two new vcpu requests: KVM_REQ_MIGRATE_EPT and KVM_REQ_MIGRATE_APIC.
These two requests are made when the two pages are migrated by the mmu_notifier
to reset the related variable to unusable value. And will also be made when
ept violation happens to reset new pages.
[Known problem]
After this patch-set applied, the two pages can be migrated/hot-removed.
But after migrating apic access page, the guest died.
The host physical address of apic access page is stored in VMCS. I reset
it to 0 to stop guest from accessing it when it is unmapped by
kvm_mmu_notifier_invalidate_page(). And reset it to new page's host physical
address in tdp_page_fault(). But it seems that guest will access apic page
directly by the host physical address.
Tang Chen (4):
kvm: Add gfn_to_page_no_pin()
kvm: Add macro VMX_APIC_ACCESS_PAGE_ADDR
kvm, memory-hotplug: Update ept identity pagetable when it is
migrated.
kvm, mem-hotplug: Update apic access page when it is migrated.
arch/x86/include/asm/kvm_host.h | 3 +++
arch/x86/include/asm/vmx.h | 2 +-
arch/x86/kvm/mmu.c | 26 ++++++++++++++++++++++++++
arch/x86/kvm/svm.c | 3 ++-
arch/x86/kvm/vmx.c | 17 +++++++++++++----
arch/x86/kvm/x86.c | 36 ++++++++++++++++++++++++++++++++++++
include/linux/kvm_host.h | 3 +++
virt/kvm/kvm_main.c | 38 +++++++++++++++++++++++++++++++++++++-
8 files changed, 121 insertions(+), 7 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-07-02 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 9:00 Tang Chen [this message]
2014-07-02 9:00 Tang Chen
2014-07-03 1:17 ` Tang Chen
2014-07-03 6:04 ` Gleb Natapov
2014-07-04 6:41 ` 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=1404291616-15007-1-git-send-email-tangchen@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=kvm@vger.kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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®