From: John Bradford <john@grabjohn.com>
To: Jamie Lokier <jamie@shareable.org>, akpm@osdl.org
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org
Date: Tue, 30 Sep 2003 09:17:16 +0100 [thread overview]
raw)
richard.brunner@amd.com
In-Reply-To: <20030930073814.GA26649@mail.jlokier.co.uk>
References: <20030930073814.GA26649@mail.jlokier.co.uk>
Subject: Re: [PATCH] Mutilated form of Andi Kleen's AMD prefetch errata patch
Quote from Jamie Lokier <jamie@shareable.org>:
> 2. Nevertheless, when a kernel _not_ optimised for those AMD processors
> is run on one, the "alternative" mechanism now correctly replaces
> prefetch instructions with nops.
> It's a reasonable argument that if a kernel version, say 2.6.0, promises
> to hide the errata from _userspace_ programs, then the generic or
> not-AMD-optimised kernels should do that too. Otherwise userspace may
> as well provide the workaround itself, by catching SIGSEGV - because it
> is perfectly normal and common to run a generic kernel on an AMD.
This problem, and others like it, would be solved for ever with
Adrian's bitmap-of-supported-cpus patch, though. With that, there is
no 'generic' kernel, either it supports Athlons, or it doesn't. 100%
elimination of Athlon specific code for other CPUs. Everybody is
happy.
Of course a kernel compiled strictly for 386s may seem to boot on an
Athlon but not work properly. So what? Just don't run the 'wrong'
kernel.
John.
next reply other threads:[~2003-09-30 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 8:17 John Bradford [this message]
2003-09-30 13:31 ` your mail Dave Jones
2003-09-30 14:06 ` Jamie Lokier
2003-09-30 14:50 ` Dave Jones
2003-09-30 15:30 ` Jamie Lokier
2003-09-30 16:34 ` Adrian Bunk
2003-09-30 14:10 ` John Bradford
2003-09-30 14:58 ` Jamie Lokier
2003-09-30 15:11 ` Dave Jones
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=200309300817.h8U8HGrf000881@81-2-122-30.bradfords.org.uk \
--to=john@grabjohn.com \
--cc=akpm@osdl.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).