linux-kernel - Re: [RFC PATCH] Utilize the PCI API in the AGP framework.

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, 07 Dec 2010 10:02:06 +1000
From:	Dave Airlie <airlied@...hat.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	airlied@...ux.ie, tglx@...utronix.de, hpa@...or.com,
	linux-kernel@...r.kernel.org, konrad@...nel.org,
	Jeremy Fitzhardinge <jeremy@...p.org>
Subject: Re: [RFC PATCH] Utilize the PCI API in the AGP framework.

On Mon, 2010-12-06 at 18:24 -0500, Konrad Rzeszutek Wilk wrote:
> Attached is a set of RFC patches that make it possible for AGP graphic drivers to
> work under Xen. The major problem that Linux kernel has when running under Xen
> is that the usage of "virt_to_phys(x) >> PAGE_SIZE" to get the DMA address is not
> applicable. That is due to the fact that the PFN value is not the real Machine
> Frame Number (MFN), hence virt_to_phys(x) >> PAGE_SIZE ends up pointing to a
> random physical address. But if you use the PCI API, then the DMA (bus) address
> returned is a valid MFN.

Can I ask you to go back a step and address what the use case for all of
this is, the patch description doesn't address why anyone cares about
AGP in 2010, esp with Xen. Virtualising hw  drivers for the sake of it
is all well and good, but since most of these drivers are for really
legacy systems I can't imagine we are going to see a lot of regression
testing before they hit distros like Debian two years from now, though
maybe Gentoo might pick up some, (is anyone even running IA64?).

I can maybe imagine the Intel GTT being cared about but we've already
addressed the issues in it from what I can see.

Also the X server use case is still possibly valid for a lot of the
systems here, its userspace ABI so it can't just end up broken. The move
to TTM/DRM being the main user didn't suddenly remove the use of the X
server case on older systems which don't have a TTM/DRM layer.

Other than that the idea seems sane, I just hate having to upgrade large
parts of the subsystem without some reasonable justification that
someone out there is going to use it. If it allows some major cleanup
else where that would also be a possibly good justification.

Dave.

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