linux-kernel - Re: Aperture memory hole on x86

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

Message-ID: <86802c440804211403x2f6a3989w7f691be4cf0071b9@mail.gmail.com>
Date:	Mon, 21 Apr 2008 14:03:35 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	Alan <alan@...eserver.org>, "Andi Kleen" <andi@...stfloor.org>,
	"Ingo Molnar" <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Aperture memory hole on x86_64

On Mon, Apr 21, 2008 at 1:42 PM, Alan <alan@...eserver.org> wrote:
>
> > On Mon, Apr 21, 2008 at 12:13 PM, Alan <alan@...eserver.org> wrote:
>  >> Something I noticed on my new AMD64 laptop with 4 gigs of RAM and a
>  >> 256meg
>  >>  video card.
>  >>
>  >>  I am running 2.6.25 from Fedora 9 beta.
>  >>
>  >>  When i boot, I get the following messages:
>  >>
>  >>  Checking aperture...
>  >>  Node 0: aperture @ 9816000000 size 32 MB
>  >>  Aperture beyond 4GB. Ignoring.
>  >>  No AGP bridge found
>  >>  Your BIOS doesn't leave a aperture memory hole
>  >>  Please enable the IOMMU option in the bios setup
>  >>  Mapping aperture over 65536 KB of RAM @ c000000
>  >>
>  >>  Is this a bug or is the x86_64 supposed to map the video aperture into
>  >>  something that is 32bit addressable?
>  >>
>  >>  Also, there is no video settings at all on this particular laptop in
>  >> bios.
>  >>   (It is an HP dv6700 with almost everything maxed out.)
>  >>
>  >>  Just curious if this is correct behavior or not. (Since I am using the
>  >>  xorg nv driver, it may not make any difference.)
>  >
>  > you have 4G ram installed, and hw mem hole is enabled, so you memory
>  > top is above 4g.
>  > and kernel need to use gart for iommu.
>  >
>  > and you bios didn't setup your gart because you didn't have agp..
>  >
>  > please check if you BIOS have setup for gart, and you can set size to
>  > 64M, and then you could get 64M ram back.
>
>  There is no memory or video related setting options in the bios at all.
>  It is about as barebones as you can get.
>
>  If you want, I can send the output of dmesg or other diagnostics for this
>  machine.

that is ok.

because get that from RAM is safe.

or some day we can treat GART in amd NB as unassigned resource, and
assign some mmio resource to it...
so you can get 64M back. --- but that not 100% safe.

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