linux-kernel - Re: [PATCH 0/9] AMD IOMMU cleanups, fixes and IVRS bug workarounds

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:	Sat, 13 Apr 2013 23:06:22 +0800
From:	Andrew Cooks <acooks@...il.com>
To:	Joerg Roedel <joro@...tes.org>
Cc:	Shuah Khan <shuahkhan@...il.com>,
	"open list:INTEL IOMMU (VT-d)" <iommu@...ts.linux-foundation.org>,
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/9] AMD IOMMU cleanups, fixes and IVRS bug workarounds

On Fri, Apr 12, 2013 at 4:06 PM, Joerg Roedel <joro@...tes.org> wrote:
> Hi Shuah,
>
> On Wed, Apr 10, 2013 at 10:06:02AM -0600, Shuah Khan wrote:
>> On Tue, Apr 9, 2013 at 2:12 PM, Joerg Roedel <joro@...tes.org> wrote:
>> >  Documentation/kernel-parameters.txt |   14 ++++
>> >  drivers/iommu/amd_iommu.c           |   79 +++++++-----------
>> >  drivers/iommu/amd_iommu_init.c      |  151 +++++++++++++++++++++++++++++++----
>> >  drivers/iommu/amd_iommu_types.h     |    1 +
>> >  4 files changed, 182 insertions(+), 63 deletions(-)
>
>> Reviewed all the patches in this set. No longer have access to test machine. :(
>
> Oh, that's sad. You were the only one having a machine wich actually has
> unity-mapped ranges defined in the BIOS table. The code for those
> mappings was basically untested before you ran it on that machine.
>
What is the machine in question? Maybe someone else has access to one,
if it's not too exotic.

--
a.
--
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/