From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: Alan <alan@clueserver.org>, "Andi Kleen" <andi@firstfloor.org>,
"Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Aperture memory hole on x86_64
Date: Mon, 21 Apr 2008 14:03:35 -0700 [thread overview]
Message-ID: <86802c440804211403x2f6a3989w7f691be4cf0071b9@mail.gmail.com> (raw)
In-Reply-To: <2615.198.182.194.170.1208810542.squirrel@clueserver.org>
On Mon, Apr 21, 2008 at 1:42 PM, Alan <alan@clueserver.org> wrote:
>
> > On Mon, Apr 21, 2008 at 12:13 PM, Alan <alan@clueserver.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
prev parent reply other threads:[~2008-04-21 21:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 19:13 Alan
2008-04-21 19:32 ` Yinghai Lu
2008-04-21 20:42 ` Alan
2008-04-21 21:03 ` Yinghai Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86802c440804211403x2f6a3989w7f691be4cf0071b9@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=alan@clueserver.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®