From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mga07.intel.com ([134.134.136.100]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fBOtY-0006Ga-3P for speck@linutronix.de; Wed, 25 Apr 2018 20:11:56 +0200 Date: Wed, 25 Apr 2018 11:11:52 -0700 From: Andi Kleen Subject: [MODERATED] Re: [PATCH 1/6] Patch 1 Message-ID: <20180425181152.GK14273@tassilo.jf.intel.com> References: <20180425032932.31562-1-andi@firstfloor.org> <20180425160654.GH14273@tassilo.jf.intel.com> <20180425173619.GJ14273@tassilo.jf.intel.com> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Wed, Apr 25, 2018 at 11:00:57AM -0700, speck for Linus Torvalds wrote: > > > On Wed, 25 Apr 2018, speck for Andi Kleen wrote: > > > > If the MAX_PA-1 bit is inverted the address is not pointing to MMIO space anymore, > > but likely to some real cached memory. > > What the hell are you blathering about? > > This is all only about the SWAP ENTRY. Ok. My patchkit handles both mprotect and swap entries. You're right we don't need it for swap entries and could use the inversion there. I was talking about mprotect though. We need to handle mprotect (and potentially also non lazy fault mmap PROT_NONE) because if we're in a guest setting something to PROT_NONE allows to bypass EPT temporarily, so you could suddenly see the values of some other guest pages. What's your opinion on that case? -Andi