[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <810b3613-72e8-4f34-2757-e622f922ae03@redhat.com>
Date: Wed, 28 Jun 2017 16:11:23 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Wanpeng Li <kernellwp@...il.com>
Cc: Radim Krčmář <rkrcmar@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kvm <kvm@...r.kernel.org>, Wanpeng Li <wanpeng.li@...mail.com>
Subject: Re: [PATCH v6 3/4] KVM: async_pf: Force a nested vmexit if the
injected #PF is async_pf
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
Powered by blists - more mailing lists