From: Roman Kagan <rkagan@virtuozzo.com>
To: "Mika Penttilä" <mika.penttila@nextfour.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/5] kvm/x86: fix inversed check for async_pf MSR
Date: Fri, 2 Dec 2016 15:05:45 +0300 [thread overview]
Message-ID: <20161202120545.GC18706@rkaganb.sw.ru> (raw)
In-Reply-To: <3f646c3d-5514-727c-4059-b417ff09886d@nextfour.com>
On Fri, Dec 02, 2016 at 12:45:28PM +0200, Mika Penttilä wrote:
> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > index bf11fe4..14a46e9 100644
> > --- a/arch/x86/kvm/x86.c
> > +++ b/arch/x86/kvm/x86.c
> > @@ -8402,7 +8402,7 @@ void kvm_arch_async_page_present(struct kvm_vcpu *vcpu,
> > bool kvm_arch_can_inject_async_page_present(struct kvm_vcpu *vcpu)
> > {
> > if (!(vcpu->arch.apf.msr_val & KVM_ASYNC_PF_ENABLED))
> > - return true;
> > + return false;
> >
> >
> Why do you make this change?
Because the code does the opposite of what it's meant to do.
> I think kvm_arch_async_page_present() is not
> ever called now and neither kvm_del_async_pf_gfn(vcpu, work->arch.gfn);
I wonder how you came to such a conclusion? I certainly see them called
on my test machine (you need to have the guest memory swapped out for
that, that can be forced e.g. using a memory cgroup).
Roman.
next prev parent reply other threads:[~2016-12-02 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a237e9b7-8155-5006-81b1-ac77a5efd13d@nextfour.com>
2016-12-02 10:45 ` [PATCH 1/5] kvm/x86: fix inversed check for async_pf MSR Mika Penttilä
2016-12-02 12:05 ` Roman Kagan [this message]
2016-12-02 15:24 Mika Penttilä
2016-12-02 17:02 ` Roman Kagan
-- strict thread matches above, loose matches on Subject: below --
2016-12-02 14:14 Mika Penttilä
2016-12-02 14:31 ` Roman Kagan
2016-12-02 8:47 [PATCH 0/5] kvm: avoid delaying async_pf ready delivery Roman Kagan
2016-12-02 8:47 ` [PATCH 1/5] kvm/x86: fix inversed check for async_pf MSR Roman Kagan
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=20161202120545.GC18706@rkaganb.sw.ru \
--to=rkagan@virtuozzo.com \
--cc=kvm@vger.kernel.org \
--cc=mika.penttila@nextfour.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