From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mingo@elte.hu,
a.p.zijlstra@chello.nl, tglx@linutronix.de, hpa@zytor.com,
riel@redhat.com, cl@linux-foundation.org, mtosatti@redhat.com
Subject: Re: [PATCH v5 03/12] Add async PF initialization to PV guest.
Date: Mon, 23 Aug 2010 18:35:49 +0300 [thread overview]
Message-ID: <20100823153549.GU10499@redhat.com> (raw)
In-Reply-To: <4C729342.6070205@redhat.com>
On Mon, Aug 23, 2010 at 06:26:58PM +0300, Avi Kivity wrote:
> On 07/19/2010 06:30 PM, Gleb Natapov wrote:
> >Enable async PF in a guest if async PF capability is discovered.
> >
> >Signed-off-by: Gleb Natapov<gleb@redhat.com>
> >---
> > arch/x86/include/asm/kvm_para.h | 5 +++
> > arch/x86/kernel/kvm.c | 68 +++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 73 insertions(+), 0 deletions(-)
> >
> >diff --git a/arch/x86/include/asm/kvm_para.h b/arch/x86/include/asm/kvm_para.h
> >index 5b05e9f..f1662d7 100644
> >--- a/arch/x86/include/asm/kvm_para.h
> >+++ b/arch/x86/include/asm/kvm_para.h
> >@@ -65,6 +65,11 @@ struct kvm_mmu_op_release_pt {
> > __u64 pt_phys;
> > };
> >
> >+struct kvm_vcpu_pv_apf_data {
> >+ __u32 reason;
> >+ __u32 enabled;
> >+};
> >+
>
> The guest will have to align this on a 64 byte boundary, should this
> be marked __aligned(64) here?
>
I do __aligned(64) when I declare variable of that type:
static DEFINE_PER_CPU(struct kvm_vcpu_pv_apf_data, apf_reason) __aligned(64);
> >@@ -231,12 +235,72 @@ static void __init paravirt_ops_setup(void)
> > #endif
> > }
> >
> >+void __cpuinit kvm_guest_cpu_init(void)
> >+{
> >+ if (!kvm_para_available())
> >+ return;
> >+
> >+ if (kvm_para_has_feature(KVM_FEATURE_ASYNC_PF)) {
> >+ u64 pa = __pa(&__get_cpu_var(apf_reason));
> >+
> >+ if (native_write_msr_safe(MSR_KVM_ASYNC_PF_EN,
> >+ pa | KVM_ASYNC_PF_ENABLED, pa>> 32))
> >+ return;
> >+ __get_cpu_var(apf_reason).enabled = 1;
> >+ printk(KERN_INFO"KVM setup async PF for cpu %d\n",
> >+ smp_processor_id());
> >+ }
> >+}
>
> Need a way to disable apf from the guest kernel command line.
>
OK.
> >+
> >+static int __cpuinit kvm_cpu_notify(struct notifier_block *self,
> >+ unsigned long action, void *hcpu)
> >+{
> >+ switch (action) {
> >+ case CPU_ONLINE:
> >+ case CPU_ONLINE_FROZEN:
> >+ kvm_guest_cpu_init();
> >+ break;
> >+ default:
> >+ break;
>
> Should we disable apf if the cpu is dying here?
>
Why? Can CPU die with outstanding sleeping tasks?
> >+ }
> >+ return NOTIFY_OK;
> >+}
> >+
>
> --
> error compiling committee.c: too many arguments to function
--
Gleb.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-08-23 15:36 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 15:30 [PATCH v5 00/12] KVM: Add host swap event notifications for PV guest Gleb Natapov
2010-07-19 15:30 ` [PATCH v5 01/12] Move kvm_smp_prepare_boot_cpu() from kvmclock.c to kvm.c Gleb Natapov
2010-07-19 15:30 ` [PATCH v5 02/12] Add PV MSR to enable asynchronous page faults delivery Gleb Natapov
2010-08-23 15:22 ` Avi Kivity
2010-08-23 15:29 ` Gleb Natapov
2010-07-19 15:30 ` [PATCH v5 03/12] Add async PF initialization to PV guest Gleb Natapov
2010-07-19 19:52 ` Rik van Riel
2010-08-23 15:26 ` Avi Kivity
2010-08-23 15:35 ` Gleb Natapov [this message]
2010-08-23 16:08 ` Christoph Lameter
2010-08-23 16:10 ` Gleb Natapov
2010-08-23 16:19 ` Avi Kivity
2010-07-19 15:30 ` [PATCH v5 04/12] Provide special async page fault handler when async PF capability is detected Gleb Natapov
2010-08-23 15:48 ` Avi Kivity
2010-08-23 15:52 ` Rik van Riel
2010-08-23 16:22 ` Avi Kivity
2010-08-24 7:31 ` Gleb Natapov
2010-08-24 9:02 ` Avi Kivity
2010-07-19 15:30 ` [PATCH v5 05/12] Export __get_user_pages_fast Gleb Natapov
2010-07-19 15:30 ` [PATCH v5 06/12] Add get_user_pages() variant that fails if major fault is required Gleb Natapov
2010-08-23 15:50 ` Avi Kivity
2010-07-19 15:30 ` [PATCH v5 07/12] Maintain memslot version number Gleb Natapov
2010-08-23 15:53 ` Avi Kivity
2010-07-19 15:30 ` [PATCH v5 08/12] Inject asynchronous page fault into a guest if page is swapped out Gleb Natapov
2010-08-23 16:17 ` Avi Kivity
2010-08-24 7:52 ` Gleb Natapov
2010-08-24 9:04 ` Avi Kivity
2010-08-24 12:28 ` Gleb Natapov
2010-08-24 12:33 ` Avi Kivity
2010-07-19 15:30 ` [PATCH v5 09/12] Retry fault before vmentry Gleb Natapov
2010-08-24 9:25 ` Avi Kivity
2010-08-24 9:33 ` Gleb Natapov
2010-08-24 9:38 ` Avi Kivity
2010-07-19 15:31 ` [PATCH v5 10/12] Handle async PF in non preemptable context Gleb Natapov
2010-08-24 9:30 ` Avi Kivity
2010-08-24 9:36 ` Gleb Natapov
2010-08-24 9:46 ` Avi Kivity
2010-07-19 15:31 ` [PATCH v5 11/12] Let host know whether the guest can handle async PF in non-userspace context Gleb Natapov
2010-08-24 9:31 ` Avi Kivity
2010-07-19 15:31 ` [PATCH v5 12/12] Send async PF when guest is not in userspace too Gleb Natapov
2010-08-24 9:36 ` Avi Kivity
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=20100823153549.GU10499@redhat.com \
--to=gleb@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@redhat.com \
--cc=cl@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/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).