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]
Message-ID: <20141106124248.GM10744@8bytes.org>
Date:	Thu, 6 Nov 2014 13:42:48 +0100
From:	Joerg Roedel <joro@...tes.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Oded.Gabbay@....com, linux-kernel@...r.kernel.org,
	iommu@...ts.linux-foundation.org, Joerg Roedel <jroedel@...e.de>
Subject: Re: [PATCH] iommu/amd: Use new invalidate_range mmu-notifier

Hey Andrew,

On Thu, Nov 06, 2014 at 01:40:08PM +0100, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@...e.de>
> 
> Make use of the new invalidate_range mmu_notifier call-back
> and remove the old logic of assigning an empty page-table
> between invalidate_range_start and invalidate_range_end.
> 
> Tested-by: Oded Gabbay <oded.gabbay@....com>
> Signed-off-by: Joerg Roedel <jroedel@...e.de>
> ---
>  drivers/iommu/amd_iommu_v2.c | 61 +++++++-------------------------------------
>  1 file changed, 9 insertions(+), 52 deletions(-)

This patch depends on the mmu_notifier_invalidate_range patches in your
mm-tree. It converts the AMD IOMMUv2 driver to make use of it and is
tested by AMD. Can you please carry this patch in the mm-tree too?

Thanks,

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ