linux-kernel - Re: [PATCH v6 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <92bdfd0d-f208-eeea-4d03-0dfddd467338@redhat.com>
Date:   Wed, 28 Jun 2017 16:20:35 +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:17, Wanpeng Li wrote:
>> 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.
> Radim explains why we at least needs nested_apf here:
> 
>> nested_apf is not #PF: if we didn't pass nested_apf, then the exception would be injected as #PF to L2 after migration.

Yes, but migration of a L1 hypervisor is broken anyway.

> Do you mean we can ignore it here and depends on Jim's patches to
> completely handle it?

Ignore it here, remember it when someone picks up Jim's patches, and
also serialize nested_apf_token.

Paolo