From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752579AbdLDS2b (ORCPT ); Mon, 4 Dec 2017 13:28:31 -0500 Received: from mail-it0-f51.google.com ([209.85.214.51]:37507 "EHLO mail-it0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751380AbdLDS23 (ORCPT ); Mon, 4 Dec 2017 13:28:29 -0500 X-Google-Smtp-Source: AGs4zMYwyxzU2f3jpY4cR2jcGIv2uOV6wUL8ChIhnL+m7XeRDXUNt9QxR038XVWMRLgSeewB+eivjFc0Z4YJFL4LxnY= MIME-Version: 1.0 In-Reply-To: References: <20171204140706.296109558@linutronix.de> From: Linus Torvalds Date: Mon, 4 Dec 2017 10:28:28 -0800 X-Google-Sender-Auth: 2C2wpy2KfuCtZ-hG-52tivW3IrM Message-ID: Subject: Re: [patch 00/60] x86/kpti: Kernel Page Table Isolation (was KAISER) To: Thomas Gleixner Cc: LKML , "the arch/x86 maintainers" , Andy Lutomirsky , Peter Zijlstra , Dave Hansen , Borislav Petkov , Greg KH , Kees Cook , Hugh Dickins , Brian Gerst , Josh Poimboeuf , Denys Vlasenko , Rik van Riel , Boris Ostrovsky , Juergen Gross , David Laight , Eduardo Valentin , "Liguori, Anthony" , Will Deacon , Daniel Gruss Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 4, 2017 at 10:18 AM, Thomas Gleixner wrote: >> >> How much of this is considered worth trying to integrate early? > > Probably the entry changes, but we need to sort out that fixmap issue first > and that affects the entry changes as well. Give me a day or two and I can > tell you. Sure. I've skimmed through the patches, and a number of the early ones seem to be "obviously safe and independently nice cleanups". Even the sysenter stack setup etc that isn't really required without the other work seems sane and fine. In fact, I have to say that the patches themselves look very good. Nothing made me go "Christ, what an ugly hack". Maybe that is because of just the skimming through, but still, it was not an unpleasant read-through. The problem, of course, is how *subtle* all the interactions are, and how one missed "oh, the CPU also needs this" makes for some really nasty breakage. So it may all look nice and clean, and then blow up horribly in some very particular configuration. And yes, paravirtualization is evil. Linus