From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1C0CCC636D4 for ; Fri, 10 Feb 2023 19:58:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233514AbjBJT6l (ORCPT ); Fri, 10 Feb 2023 14:58:41 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39498 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233293AbjBJT6j (ORCPT ); Fri, 10 Feb 2023 14:58:39 -0500 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8CD007D3F3; Fri, 10 Feb 2023 11:58:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1676059115; x=1707595115; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=RaSai31/ZxzznTIHdzlNKBGywMqWTjXsH8thm9cfa1I=; b=Koy6RfJ65u+Z4TQbhH6OSf36O7vjbV+f7dJvOerV8yIcVF1seNxB90iB b3k0YlV+P0Ku2zaxPIs+2LY3sUjpxB02jDD3E8pvDw4katoOIAtrgGJmL B/zobczEq+FyUbiaZxwtOVLW+g+JMNLOJ8DE4gNBePE+ZSGcn76UbmS6F g8v5+xmm2BYzdnUIUFHKyAkOCxeYUiMVhwjiZ1H44JVCMekHFec4M62RE wA2gEUz3ZqKBOtcfieQ9OMvwxUYRzjIUwkLpCFuWdA/4ZGQbF/mWCzAv/ FJ2p3IBGcCoAdWIURKLoRXNeyxpXkQtD+UtA+voBp5HQuSX8MSZ/xOD2L w==; X-IronPort-AV: E=McAfee;i="6500,9779,10617"; a="318532371" X-IronPort-AV: E=Sophos;i="5.97,287,1669104000"; d="scan'208";a="318532371" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2023 11:58:34 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10617"; a="913659098" X-IronPort-AV: E=Sophos;i="5.97,287,1669104000"; d="scan'208";a="913659098" Received: from hyekyung-mobl1.amr.corp.intel.com (HELO [10.209.82.221]) ([10.209.82.221]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2023 11:58:32 -0800 Message-ID: Date: Fri, 10 Feb 2023 11:58:32 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v5 06/14] x86/ioremap: Support hypervisor specified range to map as encrypted Content-Language: en-US To: Borislav Petkov , "Michael Kelley (LINUX)" Cc: Sean Christopherson , "hpa@zytor.com" , KY Srinivasan , Haiyang Zhang , "wei.liu@kernel.org" , Dexuan Cui , "luto@kernel.org" , "peterz@infradead.org" , "davem@davemloft.net" , "edumazet@google.com" , "kuba@kernel.org" , "pabeni@redhat.com" , "lpieralisi@kernel.org" , "robh@kernel.org" , "kw@linux.com" , "bhelgaas@google.com" , "arnd@arndb.de" , "hch@lst.de" , "m.szyprowski@samsung.com" , "robin.murphy@arm.com" , "thomas.lendacky@amd.com" , "brijesh.singh@amd.com" , "tglx@linutronix.de" , "mingo@redhat.com" , "dave.hansen@linux.intel.com" , Tianyu Lan , "kirill.shutemov@linux.intel.com" , "sathyanarayanan.kuppuswamy@linux.intel.com" , "ak@linux.intel.com" , "isaku.yamahata@intel.com" , "dan.j.williams@intel.com" , "jane.chu@oracle.com" , "tony.luck@intel.com" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "linux-hyperv@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-pci@vger.kernel.org" , "linux-arch@vger.kernel.org" , "iommu@lists.linux.dev" References: <4216dea6-d899-aecb-2207-caa2ae7db0e3@intel.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org On 2/10/23 11:36, Borislav Petkov wrote: >> One approach is to go with the individual device attributes for now.>> If the list does grow significantly, there will probably be patterns >> or groupings that we can't discern now. We could restructure into >> larger buckets at that point based on those patterns/groupings. > There's a reason the word "platform" is in cc_platform_has(). Initially > we wanted to distinguish attributes of the different platforms. So even > if y'all don't like CC_ATTR_PARAVISOR, that is what distinguishes this > platform and it *is* one platform. > > So call it CC_ATTR_SEV_VTOM as it uses that technology or whatever. But > call it like the platform, not to mean "I need this functionality". I can live with that. There's already a CC_ATTR_GUEST_SEV_SNP, so it would at least not be too much of a break from what we already have.