Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp3955554ybi; Mon, 15 Jul 2019 01:30:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqw8HfXhxM6M8Xqu4sZK7MiaN4+xlYRYbU0Ee0f7PcvUuxXpKxS8ZfiLdc4qkC8YbkzfChPN X-Received: by 2002:a17:902:7087:: with SMTP id z7mr26700056plk.184.1563179442075; Mon, 15 Jul 2019 01:30:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563179442; cv=none; d=google.com; s=arc-20160816; b=VW8d6XOxVgojgZZ/mpmyogB4Uq3W9I97wI3SCMMM/uX8G2+L1xIxLdzCV2jiqzqOaf lAFYvrt14+cKzKAK8XLrHzH2KKHz0tppg6ZYR/l6VZ3SAKZlMAVeBI+PwhZb5iwBOx6F lZRrk4w+noG2IMtkygV6RVBMuy9CqdRCrgftT2mWBSrRak4DtZrgUJYp12vrTtPA07ML ZZdmODQeocV0Ykf20f1cPBxY7JkI4VC+w3o1fFA3saJgjWWyjSbrT7Z8tDafOBmkFyLQ IF0HxsWK59C0K+rtWFCYlSWAXDqUhE5QDk42H5tZ1ejInB3gWfwbJVN2mvxTGcwJ2ZOP M99w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=ZI59Obl45UF1mQBOMQqzF1+nbTJngjjz72dAyoLdS2I=; b=RnZ4UjAMynxTYOyBzvPNqYH28sjpygVPlOPYe118qoUF4AZq2LoR2Il2oKKpA1cjPE NjVPFhUz6W6EiMNVB7y8aeRkcP10D9Jz3A8a5ecewl2m5YVE6h6zJnfN57F0BPOek/4H cPfQCkBIXxbfQL7+wdv0D/iD4stoAYQLVbhBwo+DT3q/qmO8viigKZ0YtUUrVAN7gP3W asIogEuPTQOHip0j8eHrdQW8XT/pC04cmhojwaL2iLHmarJ3lyiMCflBJdMfaxenj+jh 7cAkhbT1d1eKSQK3W98o5j6XN2CnOIvZgtKFwG7PPp+xQr6J4LyaAM43xXN6YEEc9KcH f+kQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y5si16578852pfq.181.2019.07.15.01.30.22; Mon, 15 Jul 2019 01:30:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729479AbfGOI2a (ORCPT + 99 others); Mon, 15 Jul 2019 04:28:30 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:46682 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729302AbfGOI2a (ORCPT ); Mon, 15 Jul 2019 04:28:30 -0400 Received: from pd9ef1cb8.dip0.t-ipconnect.de ([217.239.28.184] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hmwLE-0005Ij-RB; Mon, 15 Jul 2019 10:28:12 +0200 Date: Mon, 15 Jul 2019 10:28:11 +0200 (CEST) From: Thomas Gleixner To: Alexandre Chartre cc: Peter Zijlstra , Dave Hansen , pbonzini@redhat.com, rkrcmar@redhat.com, mingo@redhat.com, bp@alien8.de, hpa@zytor.com, dave.hansen@linux.intel.com, luto@kernel.org, kvm@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, konrad.wilk@oracle.com, jan.setjeeilers@oracle.com, liran.alon@oracle.com, jwadams@google.com, graf@amazon.de, rppt@linux.vnet.ibm.com, Paul Turner Subject: Re: [RFC v2 00/27] Kernel Address Space Isolation In-Reply-To: Message-ID: References: <1562855138-19507-1-git-send-email-alexandre.chartre@oracle.com> <5cab2a0e-1034-8748-fcbe-a17cf4fa2cd4@intel.com> <61d5851e-a8bf-e25c-e673-b71c8b83042c@oracle.com> <20190712125059.GP3419@hirez.programming.kicks-ass.net> <3ca70237-bf8e-57d9-bed5-bc2329d17177@oracle.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Alexandre, On Mon, 15 Jul 2019, Alexandre Chartre wrote: > On 7/12/19 9:48 PM, Thomas Gleixner wrote: > > As I said before, come up with a list of possible usage scenarios and > > protection scopes first and please take all the ideas other people have > > with this into account. This includes PTI of course. > > > > Once we have that we need to figure out whether these things can actually > > coexist and do not contradict each other at the semantical level and > > whether the outcome justifies the resulting complexity. > > > > After that we can talk about implementation details. > > Right, that makes perfect sense. I think so far we have the following > scenarios: > > - PTI > - KVM (i.e. VMExit handler isolation) > - maybe some syscall isolation? Vs. the latter you want to talk to Paul Turner. He had some ideas there. > I will look at them in more details, in particular what particular > mappings they need and when they need to switch mappings. > > And thanks for putting me back on the right track. That's what maintainers are for :) Thanks, tglx