From: "Wu, Feng" <feng.wu@intel.com>
To: "dwmw2@infradead.org" <dwmw2@infradead.org>,
"joro@8bytes.or" <joro@8bytes.or>
Cc: "jiang.liu@linux.intel.com" <jiang.liu@linux.intel.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wu, Feng" <feng.wu@intel.com>
Subject: RE: [v4 0/8] Add VT-d Posted-Interrupts support - IOMMU part
Date: Mon, 2 Feb 2015 08:17:17 +0000 [thread overview]
Message-ID: <E959C4978C3B6342920538CF579893F00239BA27@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1422864114-19324-1-git-send-email-feng.wu@intel.com>
Made a mistake with Joro's address, will resend this series again, Sorry for this!
Thanks,
Feng
> -----Original Message-----
> From: Wu, Feng
> Sent: Monday, February 02, 2015 4:02 PM
> To: dwmw2@infradead.org; joro@8bytes.or
> Cc: jiang.liu@linux.intel.com; iommu@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org; Wu, Feng
> Subject: [v4 0/8] Add VT-d Posted-Interrupts support - IOMMU part
>
> 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
>
> This series was part of
> http://thread.gmane.org/gmane.linux.kernel.iommu/7708. To make things
> clear, send out IOMMU part here.
>
> v3->v4:
> * Change capability to a int variant flags instead of a function call
> * Add hotplug case for VT-d PI
>
> Feng Wu (8):
> 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
> 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: Setup Posted-Interrupts capability for Intel iommu
> iommu, x86: define irq_remapping_cap()
> iommu, x86: Properly handler PI for IOMMU hotplug
>
> arch/x86/include/asm/irq_remapping.h | 11 +++++
> drivers/iommu/intel_irq_remapping.c | 78
> +++++++++++++++++++++++++++++++++-
> drivers/iommu/irq_remapping.c | 11 +++++
> drivers/iommu/irq_remapping.h | 6 +++
> include/linux/dmar.h | 32 ++++++++++++++
> include/linux/intel-iommu.h | 1 +
> 6 files changed, 138 insertions(+), 1 deletions(-)
next prev parent reply other threads:[~2015-02-02 8:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 8:01 [v4 0/8] Add VT-d Posted-Interrupts support - IOMMU part Feng Wu
2015-02-02 8:01 ` [v4 1/8] iommu: Add new member capability to struct irq_remap_ops Feng Wu
2015-02-02 8:01 ` [v4 2/8] iommu, x86: Define new irte structure for VT-d Posted-Interrupts Feng Wu
2015-02-02 8:01 ` [v4 3/8] iommu, x86: Implement irq_set_vcpu_affinity for intel_ir_chip Feng Wu
2015-02-02 8:01 ` [v4 4/8] iommu, x86: No need to migrating irq for VT-d Posted-Interrupts Feng Wu
2015-02-02 8:01 ` [v4 5/8] iommu, x86: Add cap_pi_support() to detect VT-d PI capability Feng Wu
2015-02-02 8:01 ` [v4 6/8] iommu, x86: Setup Posted-Interrupts capability for Intel iommu Feng Wu
2015-02-02 8:01 ` [v4 7/8] iommu, x86: define irq_remapping_cap() Feng Wu
2015-02-02 8:01 ` [v4 8/8] iommu, x86: Properly handler PI for IOMMU hotplug Feng Wu
2015-02-02 8:17 ` Wu, Feng [this message]
2015-02-02 8:06 [v4 0/8] Add VT-d Posted-Interrupts support - IOMMU part Feng Wu
2015-04-02 11:28 ` Joerg Roedel
2015-04-03 8:12 ` Li, ZhenHua
2015-04-07 5:02 ` Wu, Feng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E959C4978C3B6342920538CF579893F00239BA27@SHSMSX103.ccr.corp.intel.com \
--to=feng.wu@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jiang.liu@linux.intel.com \
--cc=joro@8bytes.or \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).