From: Borislav Petkov <bp@alien8.de>
To: "Jörg-Volker Peetz" <jvpeetz@web.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, bhelgaas@google.com,
Suravee.Suthikulpanit@amd.com, joro@8bytes.org
Subject: Re: [PATCH] x86, aperture: Check for GART before accessing GART registers
Date: Tue, 14 Apr 2015 13:33:49 +0200 [thread overview]
Message-ID: <20150414113349.GA26075@pd.tnic> (raw)
In-Reply-To: <552CF6DF.3000002@web.de>
On Tue, Apr 14, 2015 at 01:15:43PM +0200, Jörg-Volker Peetz wrote:
> Hi,
Hi,
please do not top-post.
> tried this patch on my HP Pavilion notebook wiht AMD Phenom II processor. The
> BIOS has no IOMMU option.
> With this patch I'm still seeing the AGP messages mention in the patch description.
> Is this processor affected at all?
Your CPU has an AGP bridge but the BIOS doesn't leave an aperture so the
kernel has to do it. Read the message.
> /proc/cpuinfo says "cpu family" 16. That is 10h?
Yes.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-04-14 11:36 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
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 [this message]
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=20150414113349.GA26075@pd.tnic \
--to=bp@alien8.de \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=bhelgaas@google.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=jvpeetz@web.de \
--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