From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
<x86@kernel.org>, <bp@suse.de>, <bhelgaas@google.com>,
<linux-kernel@vger.kernel.org>, <Suravee.Suthikulpanit@amd.com>,
<joro@8bytes.org>
Subject: Re: [PATCH] x86, aperture: Check for GART before accessing GART registers
Date: Thu, 2 Apr 2015 11:23:17 -0500 [thread overview]
Message-ID: <551D6CF5.1010604@amd.com> (raw)
In-Reply-To: <20150402160634.GB8045@gmail.com>
On 4/2/2015 11:06 AM, Ingo Molnar wrote:
>
>
> We get "AGP:" messages on kernel logs like this-
> [ 0.000000] AGP: Node 0: aperture [bus addr 0x00000000-0x01ffffff] (32MB)
> [ 0.000000] AGP: Your BIOS doesn't leave a aperture memory hole
> [ 0.000000] AGP: Please enable the IOMMU option in the BIOS setup
> [ 0.000000] AGP: This costs you 64MB of RAM
> [ 0.000000] AGP: Mapping aperture over RAM [mem 0xd4000000-0xd7ffffff]
> (65536KB)
>
> These are just noise on processors which have no GART.
> agreed.
>
>> We can avoid calling allocate_aperture() and would not have to
>> memblock_reserve() 64MB of RAM.
>> Also, we can avoid having to loop through all PCI buses, devices (twice)
>> searching for AGP bridge if we bail out early.
> Makes sense. Mind adding this info to the changelog and resend?
>
>
Sure, will do that and resend.
Thanks,
-Aravind.
next prev parent reply other threads:[~2015-04-02 16:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 14:32 [PATCH] x86, aperture: Check for GART before accessing GART registers Aravind Gopalakrishnan
2015-04-02 6:59 ` Borislav Petkov
2015-04-02 10:01 ` Ingo Molnar
2015-04-02 15:54 ` Aravind Gopalakrishnan
2015-04-02 16:06 ` Ingo Molnar
2015-04-02 16:23 ` Aravind Gopalakrishnan [this message]
2015-04-02 16:53 ` Borislav Petkov
2015-04-02 17:04 ` Aravind Gopalakrishnan
2015-04-02 17:17 ` Borislav Petkov
2015-04-02 18:19 ` Ingo Molnar
2015-04-06 23:10 ` Aravind Gopalakrishnan
2015-04-07 12:34 ` Borislav Petkov
2015-04-07 14:46 ` Aravind Gopalakrishnan
2015-04-07 14:57 ` Borislav Petkov
2015-04-07 20:34 ` Aravind Gopalakrishnan
2015-04-08 7:25 ` Borislav Petkov
2015-04-14 11:15 ` Jörg-Volker Peetz
2015-04-14 11:33 ` Borislav Petkov
2015-04-14 18:22 ` Jörg-Volker Peetz
2015-04-14 18:36 ` Borislav Petkov
2015-05-04 11:11 ` Joerg Roedel
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=551D6CF5.1010604@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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