On Fri, Jul 20, 2018 at 03:48:00PM -0700, Paul Rogers wrote:
> I'm not sure I'm clear on this. Yes, Core 2 Duo's run either 64 or 32 bit
> code. Linus thinks everybody runs 64-bit code. I've gotten the impression
> from the KPTI thing early in the year that kernel devs aren't spending much
> time at all on 32-bit code in the kernel. I've been hoping for KPTI
> mitigation for 32-bit kernels, but mostly have lost hope.
>
Queued in the tip tree this week, should be in 4.19 and then will
presumably get backported to the still-maintained kernels.
But it is expected to have a big performance impact on the old
machines without a later feature (PCID : Process Context Identifier,
according to wikipedia that was introduced with Westmere, the 32nm
die-shrink of Nehalem).
> So to be clear, are we talking here about running 4.17 in 32-bit mode, or
> just on a Core-2 Duo, which LFS would build in 64-bit mode "unless steps were
> taken" (gmp, et al)?
>
The former - I pasted from a mail showing it was everything 32-bit
in x86 (it used to be called arch/i386, maybe qemu still calls it
that, or maybe the description of the arch has never been updated in
that man's build test infrastructure.
So, inter alia, I think broadwell and opteron were mentioned.
Anyway, fixed in 4.17.8.
ĸen
--
Entropy not found, thump keyboard to continue
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
