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 20:07:15 +0100 [thread overview]
Message-ID: <20100908200715.2e56d0be@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <AANLkTi=khD7fSVv_tC6TogimjJshEErj6Em8mCcDF+SM@mail.gmail.com>
> And nobody has answered what happens when NOPLs are used to
> synchronise with something else? Surely that can lead to subtle, hard
> to debug breakage? Isn't that plain worse than refusing to run or
> breaking out of execution?
NOPL for synchronisation - of user space. I'd say thats sufficiently
unlikely not to care. It's still an improvement on crashing.
The other point you make is a good one but it's not clear that all the
proprietary apps for example will get recompiled, so to many users its
not a solution. Similarly the long term stable distros aren't going to
recompile everything and invalidate all their test data, so I doubt that
things like Centos will.
Alan
next prev parent reply other threads:[~2010-09-08 18:47 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
2010-09-08 17:51 ` Nick Lowe
2010-09-08 19:07 ` Alan Cox [this message]
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=20100908200715.2e56d0be@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
Powered by JetHome