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] [day] [month] [year] [list]

Date:	Wed, 8 Sep 2010 22:07:13 +0100
From:	Nick Lowe <nick.lowe@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: AMD Geode NOPL emulation for kernel 2.6.36-rc2

Okay, you win! :)

Were some form of this patch to be merged in the future, the bintutils
fix is likely to result in it never being hit anyway, so I suppose it
doesn't matter much.
In the long run, it could probably be removed.

I still think it's an incredibly ugly hack! :P

Cheers,

Nick

On Wed, Sep 8, 2010 at 10:11 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
>> 1) Those enterprise long term distributions aren't going to be
>> targeting the Crusoe or Geode. It's not their market. Would they even
>
> See this is the problem. You've forgotten *users*. It's easy to roll a
> special kernel, its hell on earth
>
>> 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.)
>
> Wrong for some packages - and enough to break things. Bits like glibc for
> example and chunks of X and proprietary apps.
>
>>. (Again, hypothetical, as they're not targeted at i686!)
>
> See above
>
>> 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.
>
> Lots used -i686 because the compiler people said its faster and it works
> on all 686 platforms. Neither of which it turns out is exactly true in
> many cases.
>
>> 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.
>
> s/we/you
>
> Getting the stuff right in the current kernel makes it easier to backport
> and fix and do tidily. It's not as if NOPL is complicated to emulate.
>
--
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/