Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp1275843pxb; Wed, 2 Feb 2022 00:45:39 -0800 (PST) X-Google-Smtp-Source: ABdhPJzl0hJA2SUArveUzH3YqInGc9ryqYsudhybb3U9cG90eCK+i8LF/HZlMTlZM1Fr7hGE9MuO X-Received: by 2002:a17:902:da89:: with SMTP id j9mr28403324plx.66.1643791538897; Wed, 02 Feb 2022 00:45:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643791538; cv=none; d=google.com; s=arc-20160816; b=q4a1RYTTU6UcwjN8edlAuB/G3CmAw7RQYr9QyQdwJTG1uJIjsEUPYIZA35w6d0/f3v EXc+ooaO3GFzq2nsaYJqRwycLmLJQM6I9eCCmuPA8+u8CcJrSdMY6oHbzE5EpMjAkEyH SGfDoE+zM/Jq7vYXK3ZdMbTdjr8r5xTCLQdzw13vCTGt3ycNepiBzCBCGLI1h0y2ET0R sHGBUS0YtYGsCwApsE/t1EoPqVVD9JVKUtBUcTm9hYPgNHgnxjMQKrhv0Uxi5Qz+0E24 NMwUj68ZWG67GXwIOKer4+LE15TJAxXksDt5ma+38QEHS2vb9vTrlqhyz4RT3q6WdTjZ dFtA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:subject :from:references:cc:to:content-language:user-agent:mime-version:date :message-id:dkim-signature; bh=Ftdhv8E6EuuVTnxOZUq9Q2to/d9M90KXH1Y6FvWPtw4=; b=XY1Px0+I+u57hvuvsOkx3vKvZB6ACPfMZ8dFxZakZELbKE9+BAlZSLdD1BOTiiLhc1 AV1VIMJMibzIm4MGLMojw2Powhtx+UOlQ3gzpuAuydW/NXp6nxUQK5TJ39PFf0oZqAVz gCZ76HQ+Z0+gaAj04s2g+gMBo/gonhdesAQd1Qm1cw2kt2IBPLMisy+sa0Ev8+7Nm4my mdqQa77fQc6SgkJbbiLaLo4We8mpU90XTXySK1GZEDXGTxd3KVFOQGeFi16l2J/cIUuz NHaWNi54zr8j/oB75V9ABrGjmNGS6DVOlaBBOGI1alP/dcoMcdnE2Jc1C00hTXpVlmZu h8CA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FYOYsMN7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b2si17397790plx.189.2022.02.02.00.45.27; Wed, 02 Feb 2022 00:45:38 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FYOYsMN7; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240188AbiBAPXC (ORCPT + 99 others); Tue, 1 Feb 2022 10:23:02 -0500 Received: from mga11.intel.com ([192.55.52.93]:49744 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231308AbiBAPXB (ORCPT ); Tue, 1 Feb 2022 10:23:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1643728981; x=1675264981; h=message-id:date:mime-version:to:cc:references:from: subject:in-reply-to:content-transfer-encoding; bh=nnvMf1Uwhyx5N3Z7IQ73CHGKH93ytUmyyUjp9Bh+6So=; b=FYOYsMN7NcTW4hchK5YEvdK7mwQdesyU9WcvCtVZeMQ5xXO+VpN2c9SI OYJ8OSPihAX+QtQ7qBKfEmSUX1TVPIH/FajZqVWvTODze6MDIQ663689k j5alkJlv3ZWKJNNxvM80hcwg0J1kzUAIS5D/l4IM5VJ5rTv9aNDrSQoL2 Ta64X9g1qrlq92iD9Sq+dCt+IiDRq3AkzEIhEP3k0/K7sa/L4Ay95oHSl byyqUFmOEkQjqcTgOszXdBtEJEKJbacRMhaf72xykEhVYzj6QIdIDkTNc WcTrAC66m9OCLK+qIV39vWqpBJ6O6GaCj1Iy+solLN3fSyz4Hux2IsPmO A==; X-IronPort-AV: E=McAfee;i="6200,9189,10244"; a="245306612" X-IronPort-AV: E=Sophos;i="5.88,334,1635231600"; d="scan'208";a="245306612" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2022 07:23:01 -0800 X-IronPort-AV: E=Sophos;i="5.88,334,1635231600"; d="scan'208";a="497377097" Received: from kssimha-mobl1.amr.corp.intel.com (HELO [10.212.228.15]) ([10.212.228.15]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2022 07:23:00 -0800 Message-ID: <4d19936f-fc8a-8e86-95b2-67a4ab2e2b7f@intel.com> Date: Tue, 1 Feb 2022 07:22:58 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: Nayna Jain , linuxppc-dev@lists.ozlabs.org Cc: linux-kernel@vger.kernel.org, Douglas Miller , Greg KH , George Wilson , gjoyce@ibm.com, Daniel Axtens , "Weiny, Ira" , Ram Pai References: <20220122005637.28199-1-nayna@linux.ibm.com> From: Dave Hansen Subject: Re: [RFC PATCH 0/2] powerpc/pseries: add support for local secure storage called Platform Keystore(PKS) In-Reply-To: <20220122005637.28199-1-nayna@linux.ibm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/21/22 16:56, Nayna Jain wrote: > Nayna Jain (2): > pseries: define driver for Platform Keystore > pseries: define sysfs interface to expose PKS variables Hi Folks, There another feature that we might want to consider in the naming here: > https://lore.kernel.org/all/20220127175505.851391-1-ira.weiny@intel.com/ Protection Keys for Supervisor pages is also called PKS. It's also not entirely impossible that powerpc might want to start using this code at some point, just like what happened with the userspace protection keys[1]. I don't think it's the end of the world either way, but it might save a hapless user or kernel developer some confusion if we can avoid including two "PKS" features in the kernel. I just wanted to make sure we were aware of the other's existence. :) 1. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/powerpc/include/asm/pkeys.h