linux-kernel - Re: amd64 agpgart aperture base value

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]

Message-ID: <20061215000250.GB18456@redhat.com>
Date:	Thu, 14 Dec 2006 19:02:50 -0500
From:	Dave Jones <davej@...hat.com>
To:	Daniel Drake <dsd@...too.org>
Cc:	linux list <linux-kernel@...r.kernel.org>
Subject: Re: amd64 agpgart aperture base value

On Thu, Dec 14, 2006 at 06:35:30PM -0500, Daniel Drake wrote:

 > So, you think that the aperture moving to a different location on every 
 > boot is what the BIOS desires? Is it normal for it to move so much?

Beats me. I gave up trying to understand BIOS authors motivations years ago.

 > The current patch drops the upper bits and results in the aperture 
 > always being in the same place, and this appears to work. If the BIOS 
 > did really put the aperture beyond 4GB but my patch is making Linux put 
 > it somewhere else, does it surprise you that things are still working 
 > smoothly?

Does it survive a run of testgart when masking out the high bits?
It could be that you're right, and the upper bits being reported really
are garbage.

 > Is it even possible for the aperture to start beyond 4GB when the system 
 > has less than 4GB of RAM?

The amount of RAM is irrelevant, it can appear anywhere in the address space,
which on 64bit, is pretty darned huge.  The aperture isn't backed by RAM,
it's a 'virtual window' of sorts. When you write to an address in that range, it
gets transparently remapped to somewhere else in the address space.
The window is the 'aperture', where it remaps to is controlled by a translation
table called the GATT (which does live in real memory).

That's pretty much all there is to AGP. It's just a really dumb MMU of sorts.

		Dave

-- 
http://www.codemonkey.org.uk
-
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/