mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Nick Lowe <nick.lowe@gmail.com>
Cc: Hans-Peter Jansen <hpj@urpla.net>, linux-kernel@vger.kernel.org
Subject: Re: AMD Geode NOPL emulation for kernel 2.6.36-rc2
Date: Wed, 8 Sep 2010 18:56:05 +0100	[thread overview]
Message-ID: <20100908185605.55671889@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTi=U40mzeMh-UJJy=ggVDry2qDWW-MYYyBhS_Kex@mail.gmail.com>

> If a process crashes because of NOPL usage, you get the feedback loop to fix it.

Trouble is that means rebuilding entire distributios, who don't
neccessarily care about Geode. We had the same problem before with cmov
and the VIA processors, GCC programmers didn't read the Intel PPro
manual and got it wrong but it was the end users who suffered, and most of
them were not in a position to rebuild their distro (and every security
update, and test them all ...) and their distro didn't care.

So lots of people ran a kernel with a CMOV hack in it - never got
mainstream which is unfortunate because if it had it would have helped
a lot more people and had the hole in it fixed.

> The beauty of open source is that we can recompile to correct the bad
> assumption; the latest version of binutils (GAS) finally corrects the
> bad semantic that generic i686 includes NOPL.

And the reality is that this won't happen. Yes you can do it but it's an
enormously slow and inefficient way to tackle the problem.

So the patch (corrected) makes complete sense.

Alan

  parent reply	other threads:[~2010-09-08 17:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fmbxh-5N8-41@gated-at.bofh.it>
2010-09-07 15:57 ` Nick Lowe
2010-09-08  9:15   ` Hans-Peter Jansen
2010-09-08 11:34     ` Nick Lowe
2010-09-08 11:55       ` Nick Lowe
2010-09-08 17:56       ` Alan Cox [this message]
2010-09-08 17:51         ` Nick Lowe
2010-09-08 19:07           ` Alan Cox
2010-09-08 19:44             ` Nick Lowe
2010-09-08 21:11               ` Alan Cox
2010-09-08 21:05                 ` H. Peter Anvin
2010-09-08 21:07                 ` Nick Lowe
2010-08-27 18:07 Matteo Croce
2010-08-27 18:48 ` H. Peter Anvin
2010-08-27 20:15   ` Matteo Croce
2010-08-27 20:49     ` Thomas Backlund
2010-08-27 21:32       ` Matteo Croce
2010-08-27 22:16         ` Matteo Croce
2010-08-27 22:19           ` Matteo Croce
2010-08-27 23:07         ` H. Peter Anvin
2010-08-29 12:52           ` Avi Kivity
2010-08-29 13:39           ` Matteo Croce
2010-09-08 20:59             ` H. Peter Anvin
2010-08-27 20:54     ` H. Peter Anvin

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=20100908185605.55671889@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=hpj@urpla.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick.lowe@gmail.com \
    /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®