From: Arnd Bergmann <arnd@arndb•de>
To: Jan Kratochvil <jan.kratochvil@redhat•com>
Cc: linuxppc-dev@ozlabs•org, Paul Mackerras <paulus@samba•org>,
Roland McGrath <roland@redhat•com>
Subject: Re: PPC upstream kernel ignored DABR bug
Date: Wed, 28 Nov 2007 13:28:48 +0100 [thread overview]
Message-ID: <200711281328.50386.arnd@arndb.de> (raw)
In-Reply-To: <20071128085907.GA19651@host0.dyn.jankratochvil.net>
On Wednesday 28 November 2007, Jan Kratochvil wrote:
> Please be aware DABR works fine if the same code runs just 1 (always) or
> 2 (sometimes) threads. =C2=A0It starts failing with too many threads runn=
ing:
>=20
> $ ./dabr-lost
> TID 32725: DABR 0x1001279f NIP 0xfecf41c
> TID 32726: DABR 0x1001279f NIP 0xfecf41c
> TID 32725: hitting the variable
> variable found =3D -1, caught TID =3D 32725
> TID 32726: hitting the variable
> variable found =3D -1, caught TID =3D 32726
> The kernel bug did not get reproduced - increase THREADS.
>=20
> As I did not find any code in that kernel touching DABRX its value should=
not
> be dependent on the number of threads running.
>=20
Right, this is a different problem from the one reported by Uli.
=46rom what I can tell, your problem is that you set the DABR only
in one thread, so the other threads don't see it. DABR is saved
in the thread_struct, so setting it in one thread doesn't have
an impact on any other thread.
Arnd <><
next prev parent reply other threads:[~2007-11-28 12:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 22:02 PPC upstream kernel ignored DABR bug Jan Kratochvil
2007-11-27 22:35 ` Arnd Bergmann
2007-11-28 8:59 ` Jan Kratochvil
2007-11-28 12:28 ` Arnd Bergmann [this message]
2007-11-28 12:45 ` Jan Kratochvil
2007-11-28 22:59 ` Geoff Levand
2007-11-29 0:13 ` Arnd Bergmann
2008-03-10 0:53 ` Luis Machado
2008-03-10 14:01 ` Jens Osterkamp
2008-03-10 15:13 ` Luis Machado
2008-03-10 19:19 ` Roland McGrath
2008-03-10 19:36 ` Luis Machado
2008-03-10 19:50 ` Olof Johansson
2008-03-10 19:54 ` Roland McGrath
2008-03-10 22:06 ` Segher Boessenkool
2008-03-12 17:51 ` Luis Machado
2008-03-12 22:30 ` Jens Osterkamp
2008-03-13 1:47 ` Roland McGrath
2008-03-13 22:20 ` Segher Boessenkool
2008-03-13 22:42 ` Roland McGrath
2008-03-14 2:11 ` Segher Boessenkool
2008-03-14 7:45 ` Roland McGrath
2008-03-14 8:42 ` Segher Boessenkool
2008-03-16 20:38 ` Benjamin Herrenschmidt
2008-03-16 20:37 ` Benjamin Herrenschmidt
2008-03-26 20:57 ` Josh Boyer
2008-03-27 1:47 ` Josh Boyer
2008-03-13 13:13 ` Luis Machado
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=200711281328.50386.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=jan.kratochvil@redhat$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=roland@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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