mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@maven.pl>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: "Wahlig, Elsie" <elsie.wahlig@amd.com>, linux-kernel@vger.kernel.org
Subject: Re: Opteron Rev E has a bug ... a locked instruction doesn't act as a read-acquire barrier (confirmed)
Date: Mon, 11 Aug 2008 19:03:06 +0200	[thread overview]
Message-ID: <200808111903.06953.arekm@maven.pl> (raw)
In-Reply-To: <18585.64037.521673.362547@alkaid.it.uu.se>

On Wednesday 06 August 2008, Mikael Pettersson wrote:
> On Wed, 6 Aug 2008 19:13:34 +0200, Arkadiusz Miskiewicz wrote:
> >On Wednesday 06 August 2008, Wahlig, Elsie wrote:
> >> Your issue may be one that has been seen on 1st generation
> >> AMD Opteron processor's with cpuid family 0Fh, cpuid model's
> >> < 40h with the code sequence that performs a read-modify write
> >> operation after acquiring a semaphore.
[...]
> Also I think I'll start by writing a user-space test program that
> does a stress-test of the plain lock;rmw;unlobk sequence to see if
> it can break it. (Locks/mutexes are also used in user-space.)

Bugreported so hopefully it won't be lost.

http://bugzilla.kernel.org/show_bug.cgi?id=11305

> /Mikael

-- 
Arkadiusz Miśkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/

      parent reply	other threads:[~2008-08-11 17:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CB2417C2B1152C41919D5B9DE58840FA72D828@sausexmb5.amd.com>
2008-08-06 17:13 ` Arkadiusz Miskiewicz
2008-08-06 19:23   ` Mikael Pettersson
2008-08-06 21:18     ` Wahlig, Elsie
2008-08-11 17:03     ` Arkadiusz Miskiewicz [this message]

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=200808111903.06953.arekm@maven.pl \
    --to=arekm@maven.pl \
    --cc=elsie.wahlig@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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

all inboxes | Powered by JetHome®