public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "R. J. Wysocki" <rjwysocki@sisk.pl>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: Opteron bug
Date: Sun, 20 Jun 2004 15:49:55 +0200	[thread overview]
Message-ID: <20040620154955.46ffe864.ak@suse.de> (raw)
In-Reply-To: <200406201347.17967.rjwysocki@sisk.pl>

On Sun, 20 Jun 2004 13:47:17 +0200
"R. J. Wysocki" <rjwysocki@sisk.pl> wrote:

> On Sunday 20 of June 2004 15:22, Andi Kleen wrote:
> > On Sat, 19 Jun 2004 22:29:14 +0200
> >
> > "R. J. Wysocki" <rjwysocki@sisk.pl> wrote:
> > > Hi,
> > >
> > > I hope everyone interested in the development for Opteron is aware of the
> > > bug described here:
> > >
> > > http://www.3dchips.net/content/story.php?id=3927
> >
> > The kernel never uses backwards REP prefixes.
> 
> So it doesn't matter. :-)

Some user space program could still use it.

You'll have to live with that. CPUs like all other complex
systems have bugs.
 
> Well, is there any case in which the gcc can produce such stuff?

With inline assembly only I guess.

-Andi


  parent reply	other threads:[~2004-06-20 11:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-19 20:29 Opteron bug R. J. Wysocki
2004-06-20 13:22 ` Andi Kleen
2004-06-20 11:47   ` R. J. Wysocki
2004-06-20 12:02     ` Jakub Jelinek
     [not found]       ` <200406210254.53124.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-21  5:29         ` Jakub Jelinek
2004-06-20 13:49     ` Andi Kleen [this message]
2004-07-12 17:34   ` [discuss] " H. Peter Anvin
2004-07-12 18:57     ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2004-06-20 13:07 Manfred Spraul
2004-06-20 21:49 ` 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=20040620154955.46ffe864.ak@suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjwysocki@sisk.pl \
    /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