linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Olivier Galibert <galibert@pobox.com>
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: Fri, 12 Jan 2018 12:06:24 +0100	[thread overview]
Message-ID: <20180112110624.GA13254@amd> (raw)
In-Reply-To: <CAMFK0guEASKq1zS3S3u=e7TAAYTvmfWfWe5k+X+hKV6RTpyw_Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]

Hi!

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

Good point. Is that still supported? Was it ever?

Umm. I seem to recall that 4G/4G layout was out of tree but never
merged.

High Memory Support
  1. off (NOHIGHMEM)
    2. 4GB (HIGHMEM4G)
    > 3. 64GB (HIGHMEM64G)
    choice[1-3]: 3
    Memory split
    > 1. 3G/1G user/kernel split (VMSPLIT_3G) (NEW)
      2. 2G/2G user/kernel split (VMSPLIT_2G)
      3. 1G/3G user/kernel split (VMSPLIT_1G)
choice[1-3?]:

Does anyone have recent patches?

Best regards,
								Pavel

> 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

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2018-01-12 11:06 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
2018-01-11 14:06     ` Nikolay Borisov
2018-01-12 11:06     ` Pavel Machek [this message]
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=20180112110624.GA13254@amd \
    --to=pavel@ucw.cz \
    --cc=galibert@pobox.com \
    --cc=jikos@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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).