| 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
| ||
|
Message-ID: <5453A589.6040308@redhat.com> Date: Fri, 31 Oct 2014 16:06:49 +0100 From: Paolo Bonzini <pbonzini@...hat.com> To: Radim Krčmář <rkrcmar@...hat.com>, linux-kernel@...r.kernel.org CC: kvm@...r.kernel.org, Gleb Natapov <gleb@...nel.org>, Marcelo Tosatti <mtosatti@...hat.com> Subject: Re: [PATCH 0/3] kvm: APICv register write workaround On 30/10/2014 15:06, Radim Krčmář wrote: > APICv traps register writes, so we can't retrieve previous value, but > our code depends on detecting changes. Applied, thanks. Paolo > Apart from disabling APIC register virtualization, we can detect the > change by using extra memory. One value history is enough, but we still > don't want to keep it for every APIC register, for performance reasons. > This leaves us with either a new framework, or exceptions ... > The latter options fits KVM's path better [1,2]. > > And when we already mirror a part of registers, optimizing access is > acceptable [3]. (Squashed to keep bisecters happy.) > > --- > Radim Krčmář (3): > KVM: x86: detect SPIV changes under APICv > KVM: x86: detect LVTT changes under APICv > KVM: x86: optimize some accesses to LVTT and SPIV > > arch/x86/kvm/lapic.c | 32 +++++++++++++++++--------------- > arch/x86/kvm/lapic.h | 8 +++++--- > 2 files changed, 22 insertions(+), 18 deletions(-) > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists