linux-kernel - Re: [v9 0/9] Add VT-d Posted-Interrupts support

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 5 Jun 2015 15:33:33 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Feng Wu <feng.wu@...el.com>, dwmw2@...radead.org,
	jiang.liu@...ux.intel.com, iommu@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org
Subject: Re: [v9 0/9] Add VT-d Posted-Interrupts support - IOMMU part

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@...utronix.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@...e.de>

for those.


	Joerg
--
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/