linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olivier Galibert <galibert@pobox.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jikos@suse.cz
Subject: Re: Linux 4.15-rc7
Date: Thu, 11 Jan 2018 12:29:41 +0100	[thread overview]
Message-ID: <CAMFK0guEASKq1zS3S3u=e7TAAYTvmfWfWe5k+X+hKV6RTpyw_Q@mail.gmail.com> (raw)
In-Reply-To: <20180110233252.GA14739@amd>

Wasn't/Isn't the 4G/4G  memory layout for 32 bits essentially KPTI?

  OG.


On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
>> The one thing I want to do now that Meltdown and Spectre are public,
>> is to give a *big* shout-out to the x86 people, and Thomas Gleixner in
>> particular for really being on top of this.  It's been one huge
>> annoyance, and honestly, Thomas really went over and beyond in this
>> whole mess.  A lot of other people have obviously been involved too,
>
> As I understand it: KPTI prevents Meltdown attack on x86-64, but
> Spectre means even x86-64 is not expected to be safe?
>
> Ok, so Meltdown is public... And I still have some nice 32-bit
> machines I'd like to keep working.
>
> Proof of concept is out, https://github.com/IAIK/meltdown/ .
>
> Is anyone working on KPTI for x86-32? SLES11 should still be
> supported, and that should have x86-32 version; any chance SUSE can
> share some patches?
>
> Thanks,
>                                                                         Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2018-01-11 11:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 22:55 Linux 4.15-rc7 Linus Torvalds
2018-01-08  7:20 ` Thomas Gleixner
2018-01-10 23:32 ` Pavel Machek
2018-01-11 11:29   ` Olivier Galibert [this message]
2018-01-11 14:06     ` Nikolay Borisov
2018-01-12 11:06     ` Pavel Machek
2018-01-12 13:23       ` Arnd Bergmann
2018-01-12 14:43         ` Pavel Machek
2018-01-12 17:20         ` vcaputo
2018-01-12 20:11           ` Arnd Bergmann
2018-01-12 22:04             ` vcaputo
2018-01-12 22:08               ` Arnd Bergmann
2018-01-12 22:58                 ` vcaputo
2018-01-12 17:34         ` Linus Torvalds
2018-01-12 19:38           ` Pavel Machek
2018-01-12 19:44             ` Linus Torvalds
2018-01-12 20:41               ` Pavel Machek
2018-01-13 12:52               ` kernel page table isolation for x86-32 was " Pavel Machek
2018-01-11 14:07   ` Jiri Kosina
2018-01-19 10:28     ` Pavel Machek

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='CAMFK0guEASKq1zS3S3u=e7TAAYTvmfWfWe5k+X+hKV6RTpyw_Q@mail.gmail.com' \
    --to=galibert@pobox.com \
    --cc=jikos@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).