linux-kernel - Re: [PATCH 0/28] AMD IOMMU interrupt remapping 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, 6 Jul 2012 16:08:27 +0200
From:	Joerg Roedel <joro@...tes.org>
To:	Joerg Roedel <joerg.roedel@....com>
Cc:	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/28] AMD IOMMU interrupt remapping support

On Thu, Jul 05, 2012 at 02:36:20PM +0200, Joerg Roedel wrote:
> Hi,
> 
> this patch-set adds support for IRQ remapping to the AMD IOMMU driver in
> Linux. It works similar to the already present IRQ remapping code for
> VT-d. The IOAPIC, HPET and MSI interrupts have a fixed setup to index an
> interrupt remapping table entry and the real vector and destination is
> only configured in the IRQ remapping table. This means that also the IRQ
> affinity is only changed in the IOMMU. The code was heavily
> stress-tested on a lot of machines and no known issues are left.
> 
> I also pushed this code into a branch of the IOMMU tree:
> 
> 	git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git irq-remapping

Okay, I updated this branch (non-fast-forward) with my current state. It
includes the fixes for Joe's objection and for all problems reported by
Fengguang Wu. While at it I added a patch to fix most of the other
sparse warnings in the AMD IOMMU driver. Thanks again for the reports
guys :)

I will wait for more comments and fixes to come up (including the
rewrite of patch 3 as requested by Ingo) and repost the patch-set some
time next week.

Thanks so far,

       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/