Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp4878858iog; Wed, 22 Jun 2022 07:32:42 -0700 (PDT) X-Google-Smtp-Source: AGRyM1veBvYzk99ovnA6jQo7aCk9VzPc3XAtYo+RrBshpxPMFKVPhuN+k03Fdni71EvYZoBZ5joC X-Received: by 2002:a17:906:29d:b0:6f0:18d8:7be0 with SMTP id 29-20020a170906029d00b006f018d87be0mr3421574ejf.561.1655908361822; Wed, 22 Jun 2022 07:32:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655908361; cv=none; d=google.com; s=arc-20160816; b=rnZaWbnVoI1RgvfoRjEpl5naOv2aF5lTiGqLkofaiT34KIs+9y14Cb/rKU7cYBEvjf HWXJ1gkr4c51esUgFj9xn48GvDwFneY4dYYnuqmL/v5LYnUduYa8VUmsryIf3uhxhnvV o4BlMfsxKcMRMWWA5Tl1iQKNKWxB/9yjPs0iR9rDA6wUyqYo+ZuaMz9I2AiO/YbUs6mL h3DAESqVXRwzpFNAM1JnyRHISHosNITk2AGqrwXfikC2osrun+6dx8eaKtjvZ+9kmUht I8f85+2/43wGNRAZrDw2OUDxZ6YgWSc023m1joUSoGt8lkJnevE2QWpuJYGwRdCxxq5q QUjA== 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=+F4nwBBEni9ppgS1R/ULIpMtG/XoST/SDPwPq9KYEIM=; b=doiRiZBqkV6vF2HSiMIT5xtf7kNldB0vhLfblQ4nBf80IXuZl9tSuHQNUwHNoJokdf Cxr6ayEluSdpJFRRE4JJrnziAAfTmpvlEL7RaIttEy/P6WUonSYV/Osxwj+ZulhpqT5K tTfgaqjLhNxBEUCwlWNvTY/fxD9ffgxgcnDvuOhwXiyQ/VMKjFZk4hs0RrSf6IqmUTTa frw4LOFlhECx2fmf6pEfGKNDybDEe81zv6G/b8NkAN//eT/605T206loQFA6vjRjwZe8 y4MZI92n9uoEHz8jrwAVKZ1sOx6CxUWsSa84ucuZfUL1nCuymJPCZTVJCMArXqAg9wpx EZ6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=cYTpoAib; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 d5-20020aa7d5c5000000b00435804569fesi8808540eds.442.2022.06.22.07.32.16; Wed, 22 Jun 2022 07:32:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-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=cYTpoAib; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 S1358524AbiFVOau (ORCPT + 99 others); Wed, 22 Jun 2022 10:30:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56224 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358469AbiFVOa3 (ORCPT ); Wed, 22 Jun 2022 10:30:29 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 54A1F3CFFA; Wed, 22 Jun 2022 07:29:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1655908194; x=1687444194; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=PtAWVcHQ/OeCLHQhF7OJWPRZK21owRko6PYyYGt05D0=; b=cYTpoAibFQ2jX6j3PsmcxQkuRqTGuO1ZhzvQ8psHCkryLTqxGuoct+10 Po08TgQxAJXJasWuc1PkOMt793izvjuusJNkA2Jp1wBvcbHDVDh+H11A5 9Rkn6JL0HtjBmnJkpeCiyFfURLZ2rIT+Woi/iOtQ02/QPfLmxR9+wWSx7 ByqQDA6QdL46cHBmKai+ZUEG8ts4GMlyisxLUMq7pA8tXWOA9StYK09Xy Hy6gIyfvgGIkB3anodSu0WXXPcXWjpoJqeDOOp0GECKZ9IhKFDo1Qxaho 080nZ6pizcsb7/58E7bxqg92cPmvSs0hedKn5yrKUdjCZdgXPJrh1K+B0 g==; X-IronPort-AV: E=McAfee;i="6400,9594,10385"; a="260860668" X-IronPort-AV: E=Sophos;i="5.92,212,1650956400"; d="scan'208";a="260860668" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2022 07:29:51 -0700 X-IronPort-AV: E=Sophos;i="5.92,212,1650956400"; d="scan'208";a="677571663" Received: from bshakya-mobl.amr.corp.intel.com (HELO [10.212.188.76]) ([10.212.188.76]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2022 07:29:49 -0700 Message-ID: <25be3068-be13-a451-86d4-ff4cc12ddb23@intel.com> Date: Wed, 22 Jun 2022 07:29:31 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1 Subject: Re: [PATCH Part2 v6 05/49] x86/sev: Add RMP entry lookup helpers Content-Language: en-US To: "Kalra, Ashish" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "kvm@vger.kernel.org" , "linux-coco@lists.linux.dev" , "linux-mm@kvack.org" , "linux-crypto@vger.kernel.org" Cc: "tglx@linutronix.de" , "mingo@redhat.com" , "jroedel@suse.de" , "Lendacky, Thomas" , "hpa@zytor.com" , "ardb@kernel.org" , "pbonzini@redhat.com" , "seanjc@google.com" , "vkuznets@redhat.com" , "jmattson@google.com" , "luto@kernel.org" , "dave.hansen@linux.intel.com" , "slp@redhat.com" , "pgonda@google.com" , "peterz@infradead.org" , "srinivas.pandruvada@linux.intel.com" , "rientjes@google.com" , "dovmurik@linux.ibm.com" , "tobin@ibm.com" , "bp@alien8.de" , "Roth, Michael" , "vbabka@suse.cz" , "kirill@shutemov.name" , "ak@linux.intel.com" , "tony.luck@intel.com" , "marcorr@google.com" , "sathyanarayanan.kuppuswamy@linux.intel.com" , "alpergun@google.com" , "dgilbert@redhat.com" , "jarkko@kernel.org" References: <8f63961f00fd170ba0e561f499292175f3155d26.1655761627.git.ashish.kalra@amd.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On 6/22/22 07:22, Kalra, Ashish wrote: > As I replied previously on the same subject: Architectural implies > that it is defined in the APM and shouldn't change in such a way as > to not be backward compatible. I probably think the wording here > should be architecture independent or more precisely platform > independent. Yeah, arch-independent and non-architectural are quite different concepts. At Intel, at least, when someone says "not architectural" mean that the behavior is implementation-specific. That, combined with the model/family/stepping gave me the wrong impression about what was going on. Some more clarity would be greatly appreciated.