linux-kernel - Re: [PATCH RFC] x86/kvm/lapic: always disable MMIO interface in x2APIC mode

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 for Android: free password hash cracker in your pocket

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

Message-ID: <8db7b58a-0b20-e587-a215-996ada83bc4c@redhat.com>
Date:   Thu, 2 Aug 2018 15:34:37 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Vitaly Kuznetsov <vkuznets@...hat.com>
Cc:     Jim Mattson <jmattson@...gle.com>, kvm list <kvm@...r.kernel.org>,
        Radim Krčmář <rkrcmar@...hat.com>,
        the arch/x86 maintainers <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] x86/kvm/lapic: always disable MMIO interface in
 x2APIC mode

On 02/08/2018 15:30, Vitaly Kuznetsov wrote:
> 
>> Vitaly, perhaps you could resubmit this patch, and provide a
>> KVM_CAP_DISABLE_QUIRKS switch that would make apic_mmio_{read,write}
>> return -EOPNOTSUPP in this case?
> Just to make sure I understand,
> 
> we introduce a KVM_QUIRK_LAPIC_DISABLED_MMIO bit and will be emulating
> MMIO hole in KVM till Qemu is able to deal with reads/writes passed to
> it correctly?

Yes, or forever, whichever comes first.

Paolo