Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753678AbbG2Nhl (ORCPT ); Wed, 29 Jul 2015 09:37:41 -0400 Received: from mail-wi0-f179.google.com ([209.85.212.179]:35274 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750839AbbG2Nhj (ORCPT ); Wed, 29 Jul 2015 09:37:39 -0400 From: Paolo Bonzini To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: alex.williamson@redhat.com, yang.z.zhang@intel.com, srutherford@intel.com Subject: [PATCH 0/2] KVM: x86: limit interactions between IOAPIC and LAPIC Date: Wed, 29 Jul 2015 15:37:33 +0200 Message-Id: <1438177055-26764-1-git-send-email-pbonzini@redhat.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1364 Lines: 36 Inspired by the split irqchip patches, this series limits the IOAPIC<->LAPIC to the EOI exit bitmap that is inferred from the redirection table. TMR is entirely handled within the local APIC, and no global copy of the IOAPIC-handled vectors is necessary anymore. This makes it simpler to introduce a userspace IOAPIC. Tested with ioapic.flat for now, planning to do more complete tests tomorrow. The most interesting test to do here is an assigned device that uses INTX, so I am CCing Alex Williamson for a heads up. Paolo Paolo Bonzini (2): KVM: x86: set TMR when the interrupt is accepted KVM: x86: store IOAPIC-handled vectors in each VCPU arch/x86/include/asm/kvm_host.h | 3 ++- arch/x86/kvm/ioapic.c | 27 ++++----------------------- arch/x86/kvm/ioapic.h | 11 +---------- arch/x86/kvm/lapic.c | 29 ++++++++++++++++++----------- arch/x86/kvm/lapic.h | 1 - arch/x86/kvm/svm.c | 2 +- arch/x86/kvm/vmx.c | 3 ++- arch/x86/kvm/x86.c | 11 +++-------- 8 files changed, 31 insertions(+), 56 deletions(-) -- 1.8.3.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/