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:	Tue, 3 Aug 2010 01:01:08 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	hpa@...or.com
Cc:	fujita.tomonori@....ntt.co.jp, jeremy@...p.org,
	Ian.Campbell@...rix.com, konrad.wilk@...cle.com,
	albert_herranz@...oo.es, x86@...nel.org,
	linux-kernel@...r.kernel.org, jbarnes@...tuousgeek.org,
	iommu@...ts.linux-foundation.org, tglx@...utronix.de
Subject: Re: [PATCH 9/9] x86: Detect whether we should use Xen SWIOTLB.

On Mon, 02 Aug 2010 08:47:53 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> On 08/02/2010 08:43 AM, FUJITA Tomonori wrote:
> > 
> > That's the difficult part because IOMMUs are not
> > interdependent. Hardware IOMMUs are related with swiotlb. GART and
> > AMD-IOMMU are too.
> > 
> > We could invent sorta IOMMU register interface and driver-ize IOMMUs
> > but they can't be interdependent completely.
> 
> Of course.  However, we need there to be as much structure to it as
> there can be.

Ok, let's see if Konrad can invent something clean.

But his attempt to create "swiotlb iommu function array" and "hardware
iommu function array" looks like to makes the code more unreadable.
--
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