linux-kernel - iommu mess: is there a better way?

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

Message-ID: <20080526185713.GA17523@elf.ucw.cz>
Date:	Mon, 26 May 2008 20:57:13 +0200
From:	Pavel Machek <pavel@...e.cz>
To:	kernel list <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Dave Jones <davej@...emonkey.org.uk>,
	Andi Kleen <andi@...stfloor.org>
Subject: iommu mess: is there a better way?

Hi!

aperture_64.c is basically a subset of drivers/char/agp/amd64-agp.c
... with the exception that it uses hand-coded pci access so that it
can run early... because it needs to allocate 64MB of ram.

Could we simply always allocate 64MB of ram for agp, and then free
them from amd64-agp.c if they are not needed?

I'm not quite sure how pci-gart_64.c fits into the picture. It seems
to duplicate the other half of amd64-agp.c...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/