From: Andi Kleen <ak@suse.de>
To: richard.brunner@amd.com
Cc: prandal@herefordshire.gov.uk, sowadski@umr.edu,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 amd speculative caching
Date: 22 Feb 2003 06:25:33 +0100 [thread overview]
Message-ID: <p73vfzc999u.fsf@amdsimf.suse.de> (raw)
In-Reply-To: richard.brunner@amd.com's message of "22 Feb 2003 01:14:46 +0100"
richard.brunner@amd.com writes:
> The best and reliable way to go is by the output of CPUID
> (or cat /proc/cpuinfo)
>
> if (((family == 6) && (model >= 6)) || (family == 15)) {
> printk(KERN_INFO "Advanced speculative caching feature present\n");
> return 1;
> }
>
> If your AMD processor meets the above CPUID family and model, then
> you need the patch. The decoder ring from any random
> Product name to CPUID family and model number is not yet available ;-)
>
When you have such a CPU you either need the old patch or the new patch
for change_page_attr which is in since 2.4.20 and fixes the underlying
bug of linux using conflicting cache attributes. The change_page_attr
solution is much faster because it doesn't prevent the kernel from
using 4MB pages (= less tlb misses) and also of course because it won't
cripple your CPU by disabling hardware prefetch.
However when the change_page_attr() approach is used you need to make
sure that the the agpgart driver that comes with the kernel is used
(which actually calls change_page_attr). Unfortunately it looks like
some versions of the ATI binary 3d driver install their own agpgart driver
and they don't have the change_page_attr() fixes.
So when you use the ATI driver with 2.4.20+ you need to make sure you
don't use their agpgart driver. Better would be to get ATI to fix their
agpgart included or better not ship an own agpgart at all for these
kernels.
Really there isn't much the linux kernel can do about third
party vendors replacing working included drivers with buggy own drivers.
If someone has contacts at ATI it would be good to ask them
to release a new driver with this issue fixed.
-Andi
next parent reply other threads:[~2003-02-22 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99F2150714F93F448942F9A9F112634C013857BF@txexmtae.amd.com.suse.lists.linux.kernel>
2003-02-22 5:25 ` Andi Kleen [this message]
2003-02-24 19:32 2.4.20 amd speculative caching Sowadski, Craig Harold (UMR-Student)
-- strict thread matches above, loose matches on Subject: below --
2003-02-22 0:11 richard.brunner
2003-02-20 18:48 Sowadski, Craig Harold (UMR-Student)
2003-02-20 17:07 Alastair Stevens
2003-02-20 16:49 Randal, Phil
2003-02-19 19:13 Sowadski, Craig Harold (UMR-Student)
2003-02-20 16:53 ` Dave Jones
[not found] <A5D66E6B6F478B48A3CEF22AA4B9FCA3012E54@umr-mail1.umr.edu.suse.lists.linux.kernel>
2003-02-19 17:53 ` Andi Kleen
2003-02-19 16:28 Sowadski, Craig Harold (UMR-Student)
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=p73vfzc999u.fsf@amdsimf.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=prandal@herefordshire.gov.uk \
--cc=richard.brunner@amd.com \
--cc=sowadski@umr.edu \
/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