| 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
| ||
|
Date: Tue, 4 Aug 2015 07:21:58 +0000 From: "Zhang, Yang Z" <yang.z.zhang@...el.com> To: Paolo Bonzini <pbonzini@...hat.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org> CC: "alex.williamson@...hat.com" <alex.williamson@...hat.com>, "srutherford@...el.com" <srutherford@...el.com>, "Gudimetla, Giridhar Kumar" <giridhar.kumar.gudimetla@...el.com> Subject: RE: [PATCH 1/2] KVM: x86: set TMR when the interrupt is accepted Paolo Bonzini wrote on 2015-08-04: > > > On 04/08/2015 02:46, Zhang, Yang Z wrote: >>> It is a problem for split irqchip, where the EOI exit bitmap can be >>> inferred from the IOAPIC routes but the TMR cannot. The hardware >>> behavior on the other hand can be implemented purely within the LAPIC. >> >> So updating the TMR within LAPIC is the only solution to handle it? > > It's the simplest and the one that makes most sense. Considering that > TMR is a pretty obscure feature, it's unlikely that it will be > accelerated in the future. You may be right. It is safe if no future hardware plans to use it. Let me check with our hardware team to see whether it will be used or not in future. > > Paolo Best regards, Yang -- 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