Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964798AbeALOng (ORCPT + 1 other); Fri, 12 Jan 2018 09:43:36 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:55781 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933873AbeALOne (ORCPT ); Fri, 12 Jan 2018 09:43:34 -0500 Date: Fri, 12 Jan 2018 15:43:32 +0100 From: Pavel Machek To: Arnd Bergmann Cc: Olivier Galibert , Linus Torvalds , Linux Kernel Mailing List , jikos@suse.cz Subject: Re: Linux 4.15-rc7 Message-ID: <20180112144332.GA28083@amd> References: <20180110233252.GA14739@amd> <20180112110624.GA13254@amd> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > I think that's correct: it was in RHEL3 and RHEL4 but never merged > upstream. Too bad. > However, there is an important difference between KPTI and X86_4G: > The former unmaps the kernel pages from the user space page tables, > but keeps both the linear mapping and the user pages visible in > kernel mode, while the latter must have also unmapped user space > pages from kernel mode, requiring a more expensive get_user/put_user > implementation. >=20 > Kees mentioned an idea to also unmap user pages from kernel > mode as an additional safeguard on top of KPTI, which would get > it even closer to the X86_4G implementation: > https://outflux.net/blog/archives/2018/01/04/smep-emulation-in-pti/ Well, I guess at this point I'm looking for a good place to start from... > Could you be more specific which 32-bit x86 chips you have that are > affected by Meltdown? Do you mean pre-2004 Pentiums or Core-Duo > laptops? I would guess that Cyrix/Natsemi/AMD 6x86/MediaGX/Geode > and AMD NexGen K6/K7 also affected by Spectre but probably not > Meltdown, and most other 32-bit microarchitectures seem to be purely > in-order. I do have Core Solo here'd like to keep working (and useful for web browsing). Then there's Pentium M. Occasionaly I run 32-bit kernels on modern machines for testing. Thanks, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlpYyZQACgkQMOfwapXb+vJOWQCgqRx+KHbw+MmMQQDyI/tpFI00 jbwAnjMC9KwevPqaa5c9N4yG2JcBlBgg =gTDM -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC--