From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-f197.google.com (mail-pg1-f197.google.com [209.85.215.197]) by kanga.kvack.org (Postfix) with ESMTP id 6C8496B7577 for ; Wed, 5 Dec 2018 12:24:05 -0500 (EST) Received: by mail-pg1-f197.google.com with SMTP id 143so11567592pgc.3 for ; Wed, 05 Dec 2018 09:24:05 -0800 (PST) Received: from mga03.intel.com (mga03.intel.com. [134.134.136.65]) by mx.google.com with ESMTPS id u5si17935943pgr.316.2018.12.05.09.24.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Dec 2018 09:24:04 -0800 (PST) Date: Wed, 5 Dec 2018 09:26:37 -0800 From: Alison Schofield Subject: Re: [RFC v2 11/13] keys/mktme: Program memory encryption keys on a system wide basis Message-ID: <20181205172637.GA443@alison-desk.jf.intel.com> References: <72dd5f38c1fdbc4c532f8caf2d2010f1ddfa8439.1543903910.git.alison.schofield@intel.com> <20181204092145.GR11614@hirez.programming.kicks-ass.net> <20181205054353.GE18596@alison-desk.jf.intel.com> <20181205091029.GB4234@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181205091029.GB4234@hirez.programming.kicks-ass.net> Sender: owner-linux-mm@kvack.org List-ID: To: Peter Zijlstra Cc: dhowells@redhat.com, tglx@linutronix.de, jmorris@namei.org, mingo@redhat.com, hpa@zytor.com, bp@alien8.de, luto@kernel.org, kirill.shutemov@linux.intel.com, dave.hansen@intel.com, kai.huang@intel.com, jun.nakajima@intel.com, dan.j.williams@intel.com, jarkko.sakkinen@intel.com, keyrings@vger.kernel.org, linux-security-module@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org On Wed, Dec 05, 2018 at 10:10:29AM +0100, Peter Zijlstra wrote: > On Tue, Dec 04, 2018 at 09:43:53PM -0800, Alison Schofield wrote: > > On Tue, Dec 04, 2018 at 10:21:45AM +0100, Peter Zijlstra wrote: > > > On Mon, Dec 03, 2018 at 11:39:58PM -0800, Alison Schofield wrote: > > > > > How is that serialized and kept relevant in the face of hotplug? > > mktme_leadcpus is updated on hotplug startup and teardowns. > > Not in this patch it is not. That is added in a subsequent patch, which > means that during bisection hotplug is utterly wrecked if you happen to > land between these patches, that is bad. > The Key Service support is split between 4 main patches (10-13), but the dependencies go further back in the patchset. If the bisect need outweighs any benefit from reviewing in pieces, then these patches can be squashed to a single patch: keys/mktme: Add the MKTME Key Service type for memory encryption keys/mktme: Program memory encryption keys on a system wide basis keys/mktme: Save MKTME data if kernel cmdline parameter allows keys/mktme: Support CPU Hotplug for MKTME keys Am I interpreting your point correctly? Thanks, Alison