Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754866AbaLHNgw (ORCPT ); Mon, 8 Dec 2014 08:36:52 -0500 Received: from mga09.intel.com ([134.134.136.24]:13976 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751030AbaLHNgu convert rfc822-to-8bit (ORCPT ); Mon, 8 Dec 2014 08:36:50 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.07,538,1413270000"; d="scan'208";a="650271146" From: "Wu, Feng" To: "tglx@linutronix.de" , "mingo@redhat.com" , "hpa@zytor.com" , "x86@kernel.org" , "gleb@kernel.org" , "pbonzini@redhat.com" , "dwmw2@infradead.org" , "joro@8bytes.org" , "alex.williamson@redhat.com" , "jiang.liu@linux.intel.com" CC: "linux-kernel@vger.kernel.org" , "iommu@lists.linux-foundation.org" , "kvm@vger.kernel.org" , "Wu, Feng" Subject: RE: [v2 00/25] Add VT-d Posted-Interrupts support Thread-Topic: [v2 00/25] Add VT-d Posted-Interrupts support Thread-Index: AQHQDs27F9SGRimPb0i2ZDWck2E9SpyFni/Q Date: Mon, 8 Dec 2014 13:36:43 +0000 Message-ID: References: <1417592394-24343-1-git-send-email-feng.wu@intel.com> In-Reply-To: <1417592394-24343-1-git-send-email-feng.wu@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ping... Thanks, Feng > -----Original Message----- > From: Wu, Feng > Sent: Wednesday, December 03, 2014 3:39 PM > To: tglx@linutronix.de; mingo@redhat.com; hpa@zytor.com; x86@kernel.org; > gleb@kernel.org; pbonzini@redhat.com; dwmw2@infradead.org; > joro@8bytes.org; alex.williamson@redhat.com; jiang.liu@linux.intel.com > Cc: linux-kernel@vger.kernel.org; iommu@lists.linux-foundation.org; > kvm@vger.kernel.org; Wu, Feng > Subject: [v2 00/25] Add VT-d Posted-Interrupts support > > VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt. > With VT-d Posted-Interrupts enabled, external interrupts from > direct-assigned devices can be delivered to guests without VMM > intervention when guest is running in non-root mode. > > You can find the VT-d Posted-Interrtups Spec. in the following URL: > http://www.intel.com/content/www/us/en/intelligent-systems/intel-technolog > y/vt-directed-io-spec.html > > v1->v2: > * Use VFIO framework to enable this feature, the VFIO part of this series is > base on Eric's patch "[PATCH v3 0/8] KVM-VFIO IRQ forward control" > * Rebase this patchset on > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git, > then revise some irq logic based on the new hierarchy irqdomain patches > provided > by Jiang Liu > > This patch series is made of the following groups: > 1-6: Some preparation changes in iommu and irq component, this is based on > the > new hierarchy irqdomain logic. > 7-9, 25: IOMMU changes for VT-d Posted-Interrupts, such as, feature detection, > command line parameter. > 10-16, 21-24: Changes related to KVM itself. > 17-19: Changes in VFIO component, this part was previously sent out as > "[RFC PATCH v2 0/2] kvm-vfio: implement the vfio skeleton for VT-d > Posted-Interrupts" > 20: x86 irq related changes > > Feng Wu (25): > genirq: Introduce irq_set_vcpu_affinity() to target an interrupt to a > VCPU > iommu: Add new member capability to struct irq_remap_ops > iommu, x86: Define new irte structure for VT-d Posted-Interrupts > iommu, x86: Implement irq_set_vcpu_affinity for intel_ir_chip > x86, irq: Implement irq_set_vcpu_affinity for pci_msi_ir_controller > iommu, x86: No need to migrating irq for VT-d Posted-Interrupts > iommu, x86: Add cap_pi_support() to detect VT-d PI capability > iommu, x86: Add intel_irq_remapping_capability() for Intel > iommu, x86: define irq_remapping_cap() > KVM: change struct pi_desc for VT-d Posted-Interrupts > KVM: Add some helper functions for Posted-Interrupts > KVM: Initialize VT-d Posted-Interrupts Descriptor > KVM: Define a new interface kvm_find_dest_vcpu() for VT-d PI > KVM: Get Posted-Interrupts descriptor address from struct kvm_vcpu > KVM: Make struct kvm_irq_routing_table accessible > KVM: make kvm_set_msi_irq() public > KVM: kvm-vfio: User API for VT-d Posted-Interrupts > KVM: kvm-vfio: implement the VFIO skeleton for VT-d Posted-Interrupts > KVM: x86: kvm-vfio: VT-d posted-interrupts setup > x86, irq: Define a global vector for VT-d Posted-Interrupts > KVM: Update Posted-Interrupts descriptor during vCPU scheduling > KVM: Change NDST field after vCPU scheduling > KVM: Add the handler for Wake-up Vector > KVM: Suppress posted-interrupt when 'SN' is set > iommu/vt-d: Add a command line parameter for VT-d posted-interrupts > > Documentation/kernel-parameters.txt | 1 + > Documentation/virtual/kvm/devices/vfio.txt | 9 + > arch/x86/include/asm/entry_arch.h | 2 + > arch/x86/include/asm/hardirq.h | 1 + > arch/x86/include/asm/hw_irq.h | 2 + > arch/x86/include/asm/irq_remapping.h | 11 ++ > arch/x86/include/asm/irq_vectors.h | 1 + > arch/x86/include/asm/kvm_host.h | 14 ++ > arch/x86/kernel/apic/msi.c | 1 + > arch/x86/kernel/entry_64.S | 2 + > arch/x86/kernel/irq.c | 27 +++ > arch/x86/kernel/irqinit.c | 2 + > arch/x86/kvm/Makefile | 2 +- > arch/x86/kvm/kvm_vfio_x86.c | 68 ++++++++ > arch/x86/kvm/vmx.c | 251 > +++++++++++++++++++++++++++- > arch/x86/kvm/x86.c | 38 ++++- > drivers/iommu/intel_irq_remapping.c | 64 +++++++ > drivers/iommu/irq_remapping.c | 24 +++- > drivers/iommu/irq_remapping.h | 8 + > include/linux/dmar.h | 32 ++++ > include/linux/intel-iommu.h | 1 + > include/linux/irq.h | 7 + > include/linux/kvm_host.h | 43 +++++ > include/uapi/linux/kvm.h | 10 + > kernel/irq/chip.c | 14 ++ > kernel/irq/manage.c | 20 +++ > virt/kvm/irq_comm.c | 43 +++++- > virt/kvm/irqchip.c | 11 -- > virt/kvm/kvm_main.c | 14 ++ > virt/kvm/vfio.c | 103 ++++++++++++ > 30 files changed, 799 insertions(+), 27 deletions(-) > create mode 100644 arch/x86/kvm/kvm_vfio_x86.c -- 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/