From: Joerg Roedel <joro@8bytes.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Feng Wu <feng.wu@intel.com>,
dwmw2@infradead.org, jiang.liu@linux.intel.com,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [v9 0/9] Add VT-d Posted-Interrupts support - IOMMU part
Date: Fri, 5 Jun 2015 15:33:33 +0200 [thread overview]
Message-ID: <20150605133333.GU20384@8bytes.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1506051343510.7723@nanos>
On Fri, Jun 05, 2015 at 01:47:06PM +0200, Thomas Gleixner wrote:
> On Fri, 5 Jun 2015, Feng Wu wrote:
> > Divide the whole series which contain multiple components into three parts:
> > - Prerequisite changes to irq subsystem (already merged in tip tree x86/apic branch)
> > - IOMMU part (in this series)
>
> Please add
>
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
>
> Which tree should this go through? It depends on tip/x86/apic AFAICT,
> so we can take it through that, if Joerg provides his ACK.
Yeah, these changes depend on tip/x86/apic, so it doesn't make sense to
send them through the iommu tree. There will be some conflicts when
merging tip/x86/apic and the iommu tree together, though, mainly because
of the vt-d kdump fixing patches I have in my tree. The conflicts are
spread over 3 files, but not too serious and easy to resolve.
Anyway, you have my
Acked-by: Joerg Roedel <jroedel@suse.de>
for those.
Joerg
next prev parent reply other threads:[~2015-06-05 13:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 5:42 [v9 0/9] Add VT-d Posted-Interrupts support - IOMMU part Feng Wu
2015-06-05 5:42 ` [v9 1/9] iommu: Add new member capability to struct irq_remap_ops Feng Wu
2015-06-08 13:42 ` [tip:x86/apic] " tip-bot for Feng Wu
2015-06-05 5:42 ` [v9 2/9] iommu: dmar: Extend struct irte for VT-d Posted-Interrupts Feng Wu
2015-06-08 13:43 ` [tip:x86/apic] " tip-bot for Thomas Gleixner
2015-06-05 5:42 ` [v9 3/9] iommu, x86: Implement irq_set_vcpu_affinity for intel_ir_chip Feng Wu
2015-06-08 13:43 ` [tip:x86/apic] " tip-bot for Feng Wu
2015-06-05 5:42 ` [v9 4/9] iommu, x86: Save the mode (posted or remapped) of an IRTE Feng Wu
2015-06-08 13:44 ` [tip:x86/apic] " tip-bot for Feng Wu
2015-06-05 5:42 ` [v9 5/9] iommu, x86: No need to migrating irq for VT-d Posted-Interrupts Feng Wu
2015-06-08 13:44 ` [tip:x86/apic] iommu, x86: Avoid migrating VT-d posted interrupts tip-bot for Feng Wu
2015-06-05 5:42 ` [v9 6/9] iommu, x86: Add cap_pi_support() to detect VT-d PI capability Feng Wu
2015-06-08 13:44 ` [tip:x86/apic] " tip-bot for Feng Wu
2015-06-05 5:42 ` [v9 7/9] iommu, x86: Setup Posted-Interrupts capability for Intel iommu Feng Wu
2015-06-08 13:45 ` [tip:x86/apic] " tip-bot for Feng Wu
2015-06-05 5:42 ` [v9 8/9] iommu, x86: define irq_remapping_cap() Feng Wu
2015-06-08 13:45 ` [tip:x86/apic] iommu, x86: Provide irq_remapping_cap() interface tip-bot for Feng Wu
2015-06-05 5:42 ` [v9 9/9] iommu, x86: Properly handler PI for IOMMU hotplug Feng Wu
2015-06-08 13:45 ` [tip:x86/apic] iommu, x86: Properly handle posted interrupts " tip-bot for Feng Wu
2015-06-05 11:47 ` [v9 0/9] Add VT-d Posted-Interrupts support - IOMMU part Thomas Gleixner
2015-06-05 13:33 ` Joerg Roedel [this message]
2015-06-08 1:23 ` 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=20150605133333.GU20384@8bytes.org \
--to=joro@8bytes.org \
--cc=dwmw2@infradead.org \
--cc=feng.wu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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