linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Meelis Roos <mroos@linux.ee>
To: Joerg Roedel <jroedel@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, Andrea Arcangeli <aarcange@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 32-bit PTI with THP = userspace corruption
Date: Tue, 11 Sep 2018 14:58:10 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1809111454100.29433@math.ut.ee> (raw)
In-Reply-To: <20180911114927.gikd3uf3otxn2ekq@suse.de>

> 	4) Disable PTI support on 2-level paging by making it dependent
> 	   on CONFIG_X86_PAE. This is, imho, the least ugly option
> 	   because the machines that do not support PAE are most likely
> 	   too old to be affected my Meltdown anyway. We might also
> 	   consider switching i386_defconfig to PAE?
> 
> Any other thoughts?

The machines where I have PAE off are the ones that have less memory. 
PAE is off just for performance reasons, not lack of PAE. PAE should be 
present on all of my affected machines anyway and current distributions 
seem to mostly assume 686 and PAE anyway for 32-bit systems.

-- 
Meelis Roos (mroos@ut.ee)      http://www.cs.ut.ee/~mroos/

  reply	other threads:[~2018-09-11 11:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 18:09 32-bit PTI with THP = userspace corruption Meelis Roos
2018-08-30 20:55 ` Joerg Roedel
2018-08-31  4:12   ` Meelis Roos
2018-08-31  7:07     ` Joerg Roedel
2018-09-08 10:24       ` Thomas Gleixner
2018-09-11 11:49         ` Joerg Roedel
2018-09-11 11:58           ` Meelis Roos [this message]
2018-09-11 12:12             ` Joerg Roedel
2018-09-18 13:00               ` Alan Cox
2018-10-21 12:37                 ` Pavel Machek
2018-10-22  7:56                   ` Joerg Roedel
2018-10-22 18:48                     ` Alan Cox
2018-10-23  9:11                       ` Not-so-old machines without PAE was " Pavel Machek
2018-10-22 20:56                     ` Pavel Machek
2018-09-11 18:20           ` Linus Torvalds
2018-08-31  7:10   ` Meelis Roos

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=alpine.LRH.2.21.1809111454100.29433@math.ut.ee \
    --to=mroos@linux.ee \
    --cc=aarcange@redhat.com \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tglx@linutronix.de \
    --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).