linux-kernel - Re: [PATCH 2/2] iommu: dmar -- reserve mmio space used by IOMMU

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 06 Jun 2012 09:45:29 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Don Dutile <ddutile@...hat.com>, iommu@...ts.linux-foundation.org,
	mingo@...e.hu, linux-kernel@...r.kernel.org, chrisw@...hat.com,
	suresh.b.siddha@...el.com
Subject: Re: [PATCH 2/2] iommu: dmar -- reserve mmio space used by IOMMU

On Wed, 2012-06-06 at 10:29 +0200, Ingo Molnar wrote:
> So for all practical purposes we get 99% of the warning power 
> without going into chicken-and-egg problems like how do we 
> determine that there's an IOMMU area there if there's no IOMMU 
> aware code in the kernel, right? 

That's not a chicken-and-egg problem. It's hardly difficult to see the
DMAR ACPI table and take a *basic* look at the DRHD entries. You don't
even need to fully parse it.

Doing it even without *ACPI* in your kernel would be a different
matter :)

-- 
dwmw2

Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (6171 bytes)