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, 27 Jun 2008 10:18:08 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Joerg Roedel <joerg.roedel@....com>
Cc:	tglx@...utronix.de, mingo@...hat.com, linux-kernel@...r.kernel.org,
	iommu@...ts.linux-foundation.org, bhavna.sarathy@....com,
	Sebastian.Biemueller@....com, robert.richter@....com,
	joro@...tes.org
Subject: Re: [PATCH 00/34] AMD IOMMU driver


* Joerg Roedel <joerg.roedel@....com> wrote:

> Hi,
> 
> this is the first post of the initial driver for AMD IOMMU hardware. 
> The driver is tested on hardware with various loads (disk and network) 
> and showed no problems.
> 
> It currently supports DMA remapping using the dma_ops API in the x86 
> architecture code. It also supports isolation of device DMA address 
> spaces as far as the hardware allows that (means each device can get 
> its own DMA address space and can't access the DMA memory of other 
> devices).

the code looks very clean. I guess down the line we might want to think 
about making all the externally visible knobs transparent: there should 
be only one way to disable the iommu via the boot command line (be that 
an AMD or Intel one), etc.

i have created a new -tip topic for this: tip/x86/amd-iommu and have 
applied your patches there - thanks Joerg. You can pick up the 
integrated tree via:

  http://people.redhat.com/mingo/tip.git/README

please check whether the integrated end result still works fine.
[ Obviously nobody but you can test this on real hw ;-) ]

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