Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp4862386iog; Wed, 22 Jun 2022 07:15:33 -0700 (PDT) X-Google-Smtp-Source: AGRyM1taqvvd90M4F9i/zKjAVMEazrVRJ/lNhkPsV2D+kE9O0ovaHlhFApo6WL+YrTmi130/Yl+M X-Received: by 2002:a17:907:c26:b0:711:ca03:ab3c with SMTP id ga38-20020a1709070c2600b00711ca03ab3cmr3463716ejc.654.1655907333294; Wed, 22 Jun 2022 07:15:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655907333; cv=none; d=google.com; s=arc-20160816; b=i74HcLa8BWBPRULZ3JvbWz+prOp3w6yRMt8gS6MHONSY0UaFf1p3SKxP9btl5OFmoR p2dGC+4mmdS7lMqRiHEI7NJff01T3OIREfaCeNS/mn0gvDmzy3Km80ESVfbbabmrzUbO +icZsp5YIxNaSPjqTPUClqfaKSCwrjQE6V3cm2ZfDemtmYifUZBhTL4r+93V7GNMguBs k9+qZcTj/Bf0mxhJ90+e50j6gRZ3Ml+cy1O3XP1v74xhAeHpjShsCW+5knP0DEmN1EOI jfQWvTQQEFC5RdmQThtr8fEvh1hX35xWoUovpvGpiJRdLEgFQ8NWxm7OkunyhR4gDJZw buPQ== 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=+EXRl6WV5FG4M9RIL6Oi04vvsi30kRgWRes9pKk2Hh0=; b=Sl6P4XDRknmmFZXirCtnLP38U/dpxwLI0rgCJufemkB0eF/1x6qZ/Z3+itBk3sUMll +kSbjqEVraQBIwRgEocc6kA/ZDc9lHKtxPPWjnIEvDqBULxuIPsmM+tuziiW7UBw2nsW iOLQFkYU8A1IpzzQX4K27boshvYcW67H/b7D8igNVj441tiOt70o2vYdqHRenNEnBaBw rHgcgz0bkCoQDoekHWzCumPoz/ryu9xMMRXTtqVn3q+5XfDuuOXuPkY8ZBX51pnlYbbk +vMDhcXzXvUu8vU5jiHmvcypZk7G+jIqUj3RKTRUrsZ7Ka2Imce0rkjSFc1gcko1mXj6 kuuA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=BUBICXeC; 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 sg6-20020a170907a40600b006f460b50245si16979306ejc.682.2022.06.22.07.14.44; Wed, 22 Jun 2022 07:15:33 -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=BUBICXeC; 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 S1358179AbiFVOOF (ORCPT + 99 others); Wed, 22 Jun 2022 10:14:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35782 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358280AbiFVONr (ORCPT ); Wed, 22 Jun 2022 10:13:47 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EF613B24; Wed, 22 Jun 2022 07:13:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1655907227; x=1687443227; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=+EXRl6WV5FG4M9RIL6Oi04vvsi30kRgWRes9pKk2Hh0=; b=BUBICXeCf8fiP0iAkOVo1MW7VoM2/Dk9XRN3hgLAvp/BxctZeIeJEM3d emQl7hrjYWSS1pi4rsa2pfG9g8ICi0npmVP24Ki+MNYVzUNApyzrtj+MW tuBPRei2/zYaRdR/e+Z7zrsSngChpp8GyedhYFbpVu3l4+yxyHmx3Xq7D azsm00LX3zsLI5a7/4iR1l0OShfeE2buPOu7NBVAYGaVjOQMIWmTLXcge oa0UzeQWPYzhhSk2nuT5YuC7yfdDwvGN0S3A9nPS0AVO432LO5sf1HiAi HLqJbybv1sDLHkFlfAaoSelJBkl8a+DEUG2vG5IWoKFv6ZGfTnjTwEHyB w==; X-IronPort-AV: E=McAfee;i="6400,9594,10385"; a="344416915" X-IronPort-AV: E=Sophos;i="5.92,212,1650956400"; d="scan'208";a="344416915" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2022 07:13:46 -0700 X-IronPort-AV: E=Sophos;i="5.92,212,1650956400"; d="scan'208";a="677555339" 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:13:44 -0700 Message-ID: Date: Wed, 22 Jun 2022 07:13:26 -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: Ashish Kalra , 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, thomas.lendacky@amd.com, 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, michael.roth@amd.com, 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: <8f63961f00fd170ba0e561f499292175f3155d26.1655761627.git.ashish.kalra@amd.com> 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/20/22 16:02, Ashish Kalra wrote: > +/* > + * The RMP entry format is not architectural. The format is defined in PPR > + * Family 19h Model 01h, Rev B1 processor. > + */ Let's say that Family 20h comes out and has a new RMP entry format. What keeps an old kernel from attempting to use this old format on that new CPU?