linux-kernel - Re: [PATCH 0/9] AMD IOMMU Updates for v4.1

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] [day] [month] [year] [list]

Date:	Wed, 1 Apr 2015 14:11:57 -0500
From:	Suravee Suthikulanit <suravee.suthikulpanit@....com>
To:	Joerg Roedel <joro@...tes.org>, <iommu@...ts.linux-foundation.org>
CC:	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/9] AMD IOMMU Updates for v4.1

On 4/1/2015 7:58 AM, Joerg Roedel wrote:
> Hi,
>
> here are a few fixes and enhancements for the AMD IOMMU
> driver for the next merge window. They are tested on
> different versions of AMD IOMMUs. Please review.
>
> Thanks,
>
> 	Joerg
>
> Joerg Roedel (9):
>    iommu/amd: Use BUS_NOTIFY_REMOVED_DEVICE
>    iommu/amd: Ignore BUS_NOTIFY_UNBOUND_DRIVER event
>    iommu/amd: Don't allocate with __GFP_ZERO in alloc_coherent
>    iommu/amd: Add support for contiguous dma allocator
>    iommu/amd: Return the pte page-size in fetch_pte
>    iommu/amd: Optimize iommu_unmap_page for new fetch_pte interface
>    iommu/amd: Optimize alloc_new_range for new fetch_pte interface
>    iommu/amd: Optimize amd_iommu_iova_to_phys for new fetch_pte interface
>    iommu/amd: Correctly encode huge pages in iommu page tables
>
>   drivers/iommu/amd_iommu.c       | 166 +++++++++++++++++++---------------------
>   drivers/iommu/amd_iommu_types.h |   6 ++
>   2 files changed, 83 insertions(+), 89 deletions(-)
>

Tested-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>

Thanks,

Suravee

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