Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp4352pxb; Mon, 31 Jan 2022 03:51:52 -0800 (PST) X-Google-Smtp-Source: ABdhPJzKQq62rWQqLeDu/YCg7AU2AE0nzjg7xqLTimahctaNi9P5KrhRNsZxGwpLOj+arvSuh/8k X-Received: by 2002:a17:90b:b10:: with SMTP id bf16mr34090859pjb.74.1643629912497; Mon, 31 Jan 2022 03:51:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643629912; cv=none; d=google.com; s=arc-20160816; b=Cy1cHn59nCJVNECmZlFrN2KOLvKoWMvO9lwjjAl8Jy+Bo9+JapVdizKwwOYbG7y+h/ VPQeJXyhnRMIEu7YWgTcRMJYFNVucMlSzbrmrHe7jO8821JgHSYGusWG3VSckT0dpzu6 B1C1LmV5Z/lYHF6ZOYWwzzbfSspSPapZbUoYuuE8IzSYFKmQ7U+5rGCqFMsCnvoNVky2 uQEwF7RP8fYNbDj05lvdiRMjk34co4LoJ3gk0wT+32rY1SKxJK+relFvNpKu4FbacTWv +yDbmRvf8gTNfLBZzA578na7hpvd7vz7Sg9A2u9Silrg4lz6+zrkNZBMSyXO+EjP6v4n 56Vw== 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:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=6CcHt0QaMbts4lfk3ldnSTMov3Nud/ftCVNzKCG62Ms=; b=sKzLi2zh612OLTEs+3p3VP30zEUG3ZHGeIrp+Y5UY6EvCPValNZVGtGjFOpt6hywEl RkkjycMn0G5LbQmwSn32SRGZ5mAE4XcjRL79dn6vDkH5shtXSiXgHZc8SvIEvf1PI5Is 5k6cRlMaK7GvziK33wkoYl1Lm8TetZW9OUkofAgQBHgkYXjo9IzG0hA7nt+V0ZCQirWD hybvxMVmyd8rLgYZYbXdTHSRUdpafFGIhVBlYPUWHBeJm89ngF51C2hWLG+G9lYH6qcE okr8k7NG8lzMgXHP6wPQ1PDnFCLArdTftm1HleEdQL5AhkR39TaHhLz6ku1laLPXgVdV 9bHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=DJHYcSdN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s14si10173230pfk.283.2022.01.31.03.51.41; Mon, 31 Jan 2022 03:51:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=DJHYcSdN; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1351894AbiA2AGd (ORCPT + 99 others); Fri, 28 Jan 2022 19:06:33 -0500 Received: from mga09.intel.com ([134.134.136.24]:47121 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344821AbiA2AGc (ORCPT ); Fri, 28 Jan 2022 19:06:32 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1643414792; x=1674950792; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=UunOKiMHQy6XK19DztRxwXIwZtwG2fh3eR8kNC4ifYw=; b=DJHYcSdNb1NHaV7QE3cFeYIGOrMfT6pyhqr88OGroxYBVhTIWLf/812m 6Dm9DX3qu7RG/L/DJ8fZqZW9H7LKUX5Z9ZeoehABItE8spHvUCAW69ITq maI07Hne3ReuUnXys/KFEhBuhESLLpzqnoQ4cmVUkKBV4NQbiTJQc3I8m LL8TYyLipQaJRbDb6o2Uny5zsUtYrhxj6eFSKD+s9GmpMCrMMYIIlHs58 ExLsBbfoP+vwon0NnlTQwaMd2LRVuW/udTLNd7dsvc415MMKYFyJcMtIa YLhvq2lDBVNi9l4B1joD/gHNIbSLEkAnBajW4aYeH4aHtK5vxHtk5KhEg Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10241"; a="246991372" X-IronPort-AV: E=Sophos;i="5.88,325,1635231600"; d="scan'208";a="246991372" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jan 2022 16:06:32 -0800 X-IronPort-AV: E=Sophos;i="5.88,325,1635231600"; d="scan'208";a="697258807" Received: from zhenkuny-mobl2.amr.corp.intel.com (HELO [10.209.84.59]) ([10.209.84.59]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jan 2022 16:06:32 -0800 Message-ID: Date: Fri, 28 Jan 2022 16:06:29 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.2 Subject: Re: [PATCH V8 06/44] mm/pkeys: Add Kconfig options for PKS Content-Language: en-US To: ira.weiny@intel.com, Dave Hansen , "H. Peter Anvin" , Dan Williams Cc: Fenghua Yu , Rick Edgecombe , linux-kernel@vger.kernel.org References: <20220127175505.851391-1-ira.weiny@intel.com> <20220127175505.851391-7-ira.weiny@intel.com> From: Dave Hansen In-Reply-To: <20220127175505.851391-7-ira.weiny@intel.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/27/22 09:54, ira.weiny@intel.com wrote: > @@ -1867,6 +1867,7 @@ config X86_INTEL_MEMORY_PROTECTION_KEYS > depends on X86_64 && (CPU_SUP_INTEL || CPU_SUP_AMD) > select ARCH_USES_HIGH_VMA_FLAGS > select ARCH_HAS_PKEYS > + select ARCH_HAS_SUPERVISOR_PKEYS For now, this should be: select ARCH_HAS_SUPERVISOR_PKEYS if CPU_SUP_INTEL unless the AMD folks speak up and say otherwise. :)