From: Jamie Lokier <jamie@shareable.org>
To: Dave Jones <davej@redhat.com>,
akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
richard.brunner@amd.com
Subject: Re: [PATCH] Mutilated form of Andi Kleen's AMD prefetch errata patch
Date: Wed, 1 Oct 2003 00:55:28 +0100 [thread overview]
Message-ID: <20030930235528.GA32209@mail.shareable.org> (raw)
In-Reply-To: <20030930172618.GE5507@redhat.com>
Dave Jones wrote:
> Which gets us back to the question of why this is needed at all ?
> You said earlier "In case you hadn't fully grokked it, my code doesn't
> disable the workaround!" So why do you need this ?
To change the prefetch workaround from a critical requirement to an
optimisation knob.
X86_USE_3DNOW is very similar: if it's enabled, the kernel has some
extra code to make certain CPUs run faster, but they also run fine
without it. X86_OOSTORE is another.
What I'd really like your opinion on is the appropriate userspace
behaviour. If we don't care about fixing up userspace, then
__ex_table is a much tidier workaround for the prefetch bug. If we do
care about fixing up userspace, then do we need a policy decision that
says it's not acceptable to run on AMD without userspace fixups from
2.6.0 onwards - it must fixup userspace or refuse to run?
-- Jamie
next prev parent reply other threads:[~2003-09-30 23:58 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 7:38 [PATCH] Mutilated form of Andi Kleen's AMD prefetch errata patch Jamie Lokier
2003-09-30 8:01 ` Nick Piggin
2003-09-30 13:22 ` Dave Jones
2003-09-30 13:39 ` Jamie Lokier
2003-09-30 13:53 ` Dave Jones
2003-09-30 14:45 ` Jamie Lokier
2003-09-30 15:08 ` Dave Jones
2003-09-30 16:54 ` Jamie Lokier
2003-09-30 17:26 ` Dave Jones
2003-09-30 23:55 ` Jamie Lokier [this message]
2003-10-01 0:27 ` Andrew Morton
[not found] <20030930073814.GA26649@mail.jlokier.co.uk.suse.lists.linux.kernel>
[not found] ` <20030930132211.GA23333@redhat.com.suse.lists.linux.kernel>
[not found] ` <20030930133936.GA28876@mail.shareable.org.suse.lists.linux.kernel>
[not found] ` <20030930135324.GC5507@redhat.com.suse.lists.linux.kernel>
[not found] ` <20030930144526.GC28876@mail.shareable.org.suse.lists.linux.kernel>
[not found] ` <20030930150825.GD5507@redhat.com.suse.lists.linux.kernel>
[not found] ` <20030930165450.GF28876@mail.shareable.org.suse.lists.linux.kernel>
[not found] ` <20030930172618.GE5507@redhat.com.suse.lists.linux.kernel>
2003-09-30 19:08 ` Andi Kleen
2003-09-30 20:08 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-10-01 1:54 Nakajima, Jun
2003-10-01 2:07 ` Andrew Morton
2003-10-01 2:08 ` Mike Fedyk
2003-10-01 2:23 Nakajima, Jun
2003-10-01 2:51 ` Jamie Lokier
2003-10-01 3:14 ` Andrew Morton
2003-10-01 4:30 Nakajima, Jun
2003-10-01 5:38 ` Jamie Lokier
2003-10-01 5:48 ` Andrew Morton
2003-10-01 6:13 ` Jamie Lokier
2003-10-01 6:32 ` Andrew Morton
2003-10-01 6:57 ` Jamie Lokier
[not found] <7F740D512C7C1046AB53446D3720017304AFCF@scsmsx402.sc.intel.com.suse.lists.linux.kernel>
[not found] ` <20031001053833.GB1131@mail.shareable.org.suse.lists.linux.kernel>
[not found] ` <20030930224853.15073447.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20031001061348.GE1131@mail.shareable.org.suse.lists.linux.kernel>
[not found] ` <20030930233258.37ed9f7f.akpm@osdl.org.suse.lists.linux.kernel>
2003-10-01 6:47 ` Andi Kleen
2003-10-01 7:00 ` Andrew Morton
2003-10-01 7:06 ` Andi Kleen
2003-10-01 7:31 ` Jamie Lokier
2003-10-01 7:41 ` Andi Kleen
2003-10-01 8:02 ` Hugh Dickins
2003-10-01 8:49 ` Andi Kleen
2003-10-01 9:33 ` Jamie Lokier
2003-10-01 14:51 ` Andrew Morton
2003-10-01 14:56 ` Andi Kleen
2003-10-01 15:19 ` Andrew Morton
2003-10-01 15:24 ` Andi Kleen
2003-10-01 16:18 ` Jamie Lokier
2003-10-01 7:20 ` Jamie Lokier
2003-10-01 7:39 ` Andi Kleen
2003-10-01 8:20 ` Jamie Lokier
[not found] ` <20031001065705.GI1131@mail.shareable.org.suse.lists.linux.kernel>
2003-10-01 7:15 ` Andi Kleen
2003-10-01 7:24 ` Andi Kleen
2003-10-01 7:55 ` Jamie Lokier
2003-10-01 8:00 ` Andi Kleen
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=20030930235528.GA32209@mail.shareable.org \
--to=jamie@shareable.org \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.brunner@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.