From: Paolo Bonzini <pbonzini@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>, "Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH v6 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async_pf
Date: Wed, 28 Jun 2017 16:11:23 +0200 [thread overview]
Message-ID: <810b3613-72e8-4f34-2757-e622f922ae03@redhat.com> (raw)
In-Reply-To: <CANRm+CzKKmdarg3NxVC+mem+DKPhayN5v1wcqfiOMXakaqt4fw@mail.gmail.com>
On 28/06/2017 16:09, Wanpeng Li wrote:
>> Yes, this was my question essentially. I would still migrate
>> nested_apf_token (as part of nested virt state), and then clear it in
>> KVM when doing the async-pf broadcast.
> Do you mean I should save nested_apf_token by GET_VCPU_EVENTS and
> restore it by SET_VCPU_EVENTS? I utilize the place of "u8 pad" in
> kvm_vcpu_events to hold nested_apf, however nested_apf_token is
> unsigned long.
If for now we can leave out the GET/SET_VCPU_EVENTS changes, that would
be best. nested_apf and nested_apf_token should be migrated together
with the rest of the nested virt state.
Paolo
next prev parent reply other threads:[~2017-06-28 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 12:25 [PATCH v6 0/4] KVM: async_pf: Fix async pf exception injection Wanpeng Li
2017-06-28 12:25 ` [PATCH v6 1/4] KVM: x86: Simple kvm_x86_ops->queue_exception parameter Wanpeng Li
2017-06-28 12:25 ` [PATCH v6 2/4] KVM: async_pf: Add L1 guest async_pf #PF vmexit handler Wanpeng Li
2017-06-28 12:25 ` [PATCH v6 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async_pf Wanpeng Li
2017-06-28 12:56 ` Paolo Bonzini
2017-06-28 13:38 ` Radim Krčmář
2017-06-28 13:48 ` Paolo Bonzini
2017-06-28 14:09 ` Wanpeng Li
2017-06-28 14:11 ` Paolo Bonzini [this message]
2017-06-28 14:17 ` Wanpeng Li
2017-06-28 14:20 ` Paolo Bonzini
2017-06-28 14:23 ` Wanpeng Li
2017-06-28 12:25 ` [PATCH v6 4/4] KVM: async_pf: Let host know whether the guest support delivery async_pf as #PF vmexit Wanpeng Li
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=810b3613-72e8-4f34-2757-e622f922ae03@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.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®