linux-kernel - Re: AMD Geode NOPL emulation for kernel 2.6.36-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTi=FNFKmBgobH4q-GHguHM-0UOCQpa7JhPhyZZHG@mail.gmail.com>
Date:	Wed, 8 Sep 2010 20:44:58 +0100
From:	Nick Lowe <nick.lowe@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Hans-Peter Jansen <hpj@...la.net>, linux-kernel@...r.kernel.org
Subject: Re: AMD Geode NOPL emulation for kernel 2.6.36-rc2

Hi,

It's still not making any sense to me what-so-ever. And I'm really
trying to be open minded!

1) Those enterprise long term distributions aren't going to be
targeting the Crusoe or Geode. It's not their market. Would they even
back port, therefore, if it was an issue?
(This hypothetical anyway as it assuming they have an i686 targeted
build already. Who does? Centos, RHEL and SUSE Enterprise are all i386
targeted at the moment for x86.)

2) Nor is it likely, considering their focus, that end users will want
to run them on their Crusoe or Geode hardware if they were i686
targeted. (Again, hypothetical, as they're not targeted at i686!)

3) Distributions that specifically target the Crusoe or Geode already,
by definition, won't be using an i686 targeted build at the moment.

4) As for proprietary apps, again, is it likely that they're targeting
i686 already? Or is it far more likely they're compiled for i386 et.
al.

5) If they are targeting i686 already, end users won't have been able
to run them on their Crusoe or Geode hardware before so they're not
going to miss them now.

6) What we are talking about is future distributions, whatever they
are, that are now or are changing to target i686 which end users will
ultimately want to migrate to and run.
Again, at the moment, most are i386 targeted, so they all work regardless.
(They'll need to recompile everything anyway if they decide to move,
so it's completely moot surely...)

Thanks,

Nick

On Wed, Sep 8, 2010 at 8:07 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>> 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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/