From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test3-mm1: scheduling while atomic (ext3?)
Date: 13 Aug 2003 13:17:18 +0200 [thread overview]
Message-ID: <p73adad7qo1.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <1060772769.8009.4.camel@localhost.localdomain.suse.lists.linux.kernel>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> Put the likely(pos) in the asm/prefetch for Athlon until someone can
out what is going on with some specific Athlons, 2.6 and certain
> kernels (notably 4G/4G)
You can use the same workaround as x86-64. add an exception handler and
just jump back. Advantage is that it is completely outside the fast path.
But note you also have to add runtime sorting of __ex_table when you
do this, otherwise the __ex_table becomes unsorted when someone uses
list_for_each (which does prefetch) in a __init function
(all code is available in x86-64, just needs to be ported over)
-Andi
next parent reply other threads:[~2003-08-13 11:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030813045638.GA9713@middle.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20030813014746.412660ae.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20030813091958.GA30746@gates.of.nowhere.suse.lists.linux.kernel>
[not found] ` <20030813025542.32429718.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <1060772769.8009.4.camel@localhost.localdomain.suse.lists.linux.kernel>
2003-08-13 11:17 ` Andi Kleen [this message]
[not found] ` <20030813042544.5064b3f4.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <1060774803.8008.24.camel@localhost.localdomain.suse.lists.linux.kernel>
2003-08-13 12:10 ` 2.6.0-test3-mm1: scheduling while atomic (ext3?) Andi Kleen
2003-08-13 12:48 ` Alan Cox
2003-08-13 13:14 ` Andi Kleen
2003-08-13 14:09 ` Alan Cox
2003-08-13 14:20 ` Andi Kleen
2003-08-13 15:20 ` Alan Cox
2003-08-13 15:32 ` Andi Kleen
2003-08-13 18:44 ` Alan Cox
2003-08-13 18:53 ` Andi Kleen
2003-08-13 16:39 ` Dave Jones
2003-08-13 18:34 ` Alan Cox
2003-08-13 20:12 ` Dave Jones
2003-08-13 18:37 ` Alan Cox
2003-08-13 18:59 richard.brunner
-- strict thread matches above, loose matches on Subject: below --
2003-08-13 4:56 Jurriaan
2003-08-13 8:47 ` Andrew Morton
2003-08-13 9:19 ` Jurriaan on adsl-gate
2003-08-13 9:55 ` Andrew Morton
2003-08-13 11:06 ` Alan Cox
2003-08-13 11:25 ` Andrew Morton
2003-08-13 11:40 ` Alan Cox
2003-08-18 12:08 ` Pavel Machek
2003-08-13 11:06 ` 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=p73adad7qo1.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).