From: Avi Kivity <avi@redhat.com> To: Gleb Natapov <gleb@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 12/12] Send async PF when guest is not in userspace too. Date: Tue, 24 Aug 2010 12:36:10 +0300 [thread overview] Message-ID: <4C73928A.4040601@redhat.com> (raw) In-Reply-To: <1279553462-7036-13-git-send-email-gleb@redhat.com> On 07/19/2010 06:31 PM, Gleb Natapov wrote: > If guest indicates that it can handle async pf in kernel mode too send > it, but only if interrupt are enabled. > > Reviewed-by: Rik van Riel<riel@redhat.com> > Signed-off-by: Gleb Natapov<gleb@redhat.com> > --- > arch/x86/kvm/mmu.c | 8 +++++++- > 1 files changed, 7 insertions(+), 1 deletions(-) > > diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c > index 12d1a7b..ed87b1c 100644 > --- a/arch/x86/kvm/mmu.c > +++ b/arch/x86/kvm/mmu.c > @@ -2361,7 +2361,13 @@ static bool can_do_async_pf(struct kvm_vcpu *vcpu) > if (!vcpu->arch.apf_data || kvm_event_needs_reinjection(vcpu)) > return false; > > - return !!kvm_x86_ops->get_cpl(vcpu); > + if (vcpu->arch.apf_send_user_only) > + return !!kvm_x86_ops->get_cpl(vcpu); cpl is not a bool. Compare it with 0. > + > + if (!kvm_x86_ops->interrupt_allowed(vcpu)) > + return false; > + > + return true; > } Should have commented before, but get_cpl() is not accurate when doing nested virtualization. When L1 intercepts page faults, being in L2 is equivalent to CPL 3. But we need to get the apf information to L1 somehow. -- error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com> To: Gleb Natapov <gleb@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 12/12] Send async PF when guest is not in userspace too. Date: Tue, 24 Aug 2010 12:36:10 +0300 [thread overview] Message-ID: <4C73928A.4040601@redhat.com> (raw) In-Reply-To: <1279553462-7036-13-git-send-email-gleb@redhat.com> On 07/19/2010 06:31 PM, Gleb Natapov wrote: > If guest indicates that it can handle async pf in kernel mode too send > it, but only if interrupt are enabled. > > Reviewed-by: Rik van Riel<riel@redhat.com> > Signed-off-by: Gleb Natapov<gleb@redhat.com> > --- > arch/x86/kvm/mmu.c | 8 +++++++- > 1 files changed, 7 insertions(+), 1 deletions(-) > > diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c > index 12d1a7b..ed87b1c 100644 > --- a/arch/x86/kvm/mmu.c > +++ b/arch/x86/kvm/mmu.c > @@ -2361,7 +2361,13 @@ static bool can_do_async_pf(struct kvm_vcpu *vcpu) > if (!vcpu->arch.apf_data || kvm_event_needs_reinjection(vcpu)) > return false; > > - return !!kvm_x86_ops->get_cpl(vcpu); > + if (vcpu->arch.apf_send_user_only) > + return !!kvm_x86_ops->get_cpl(vcpu); cpl is not a bool. Compare it with 0. > + > + if (!kvm_x86_ops->interrupt_allowed(vcpu)) > + return false; > + > + return true; > } Should have commented before, but get_cpl() is not accurate when doing nested virtualization. When L1 intercepts page faults, being in L2 is equivalent to CPL 3. But we need to get the apf information to L1 somehow. -- error compiling committee.c: too many arguments to function -- 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-24 9:37 UTC|newest] Thread overview: 82+ 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 ` 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 ` Gleb Natapov 2010-07-19 15:30 ` [PATCH v5 02/12] Add PV MSR to enable asynchronous page faults delivery Gleb Natapov 2010-07-19 15:30 ` Gleb Natapov 2010-08-23 15:22 ` Avi Kivity 2010-08-23 15:22 ` Avi Kivity 2010-08-23 15:29 ` Gleb Natapov 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 15:30 ` Gleb Natapov 2010-07-19 19:52 ` Rik van Riel 2010-07-19 19:52 ` Rik van Riel 2010-08-23 15:26 ` Avi Kivity 2010-08-23 15:26 ` Avi Kivity 2010-08-23 15:35 ` Gleb Natapov 2010-08-23 15:35 ` Gleb Natapov 2010-08-23 16:08 ` Christoph Lameter 2010-08-23 16:08 ` Christoph Lameter 2010-08-23 16:10 ` Gleb Natapov 2010-08-23 16:10 ` Gleb Natapov 2010-08-23 16:19 ` Avi Kivity 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-07-19 15:30 ` Gleb Natapov 2010-08-23 15:48 ` Avi Kivity 2010-08-23 15:48 ` Avi Kivity 2010-08-23 15:52 ` Rik van Riel 2010-08-23 15:52 ` Rik van Riel 2010-08-23 16:22 ` Avi Kivity 2010-08-23 16:22 ` Avi Kivity 2010-08-24 7:31 ` Gleb Natapov 2010-08-24 7:31 ` Gleb Natapov 2010-08-24 9:02 ` Avi Kivity 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 ` 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-07-19 15:30 ` Gleb Natapov 2010-08-23 15:50 ` Avi Kivity 2010-08-23 15:50 ` Avi Kivity 2010-07-19 15:30 ` [PATCH v5 07/12] Maintain memslot version number Gleb Natapov 2010-07-19 15:30 ` Gleb Natapov 2010-08-23 15:53 ` Avi Kivity 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-07-19 15:30 ` Gleb Natapov 2010-08-23 16:17 ` Avi Kivity 2010-08-23 16:17 ` Avi Kivity 2010-08-24 7:52 ` Gleb Natapov 2010-08-24 7:52 ` Gleb Natapov 2010-08-24 9:04 ` Avi Kivity 2010-08-24 9:04 ` Avi Kivity 2010-08-24 12:28 ` Gleb Natapov 2010-08-24 12:28 ` Gleb Natapov 2010-08-24 12:33 ` Avi Kivity 2010-08-24 12:33 ` Avi Kivity 2010-07-19 15:30 ` [PATCH v5 09/12] Retry fault before vmentry Gleb Natapov 2010-07-19 15:30 ` Gleb Natapov 2010-08-24 9:25 ` Avi Kivity 2010-08-24 9:25 ` Avi Kivity 2010-08-24 9:33 ` Gleb Natapov 2010-08-24 9:33 ` Gleb Natapov 2010-08-24 9:38 ` Avi Kivity 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-07-19 15:31 ` Gleb Natapov 2010-08-24 9:30 ` Avi Kivity 2010-08-24 9:30 ` Avi Kivity 2010-08-24 9:36 ` Gleb Natapov 2010-08-24 9:36 ` Gleb Natapov 2010-08-24 9:46 ` Avi Kivity 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-07-19 15:31 ` Gleb Natapov 2010-08-24 9:31 ` Avi Kivity 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-07-19 15:31 ` Gleb Natapov 2010-08-24 9:36 ` Avi Kivity [this message] 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=4C73928A.4040601@redhat.com \ --to=avi@redhat.com \ --cc=a.p.zijlstra@chello.nl \ --cc=cl@linux-foundation.org \ --cc=gleb@redhat.com \ --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: linkBe 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.