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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7574AC43334 for ; Fri, 22 Jul 2022 19:38:15 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id CC0636B0072; Fri, 22 Jul 2022 15:38:14 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id C700B6B0073; Fri, 22 Jul 2022 15:38:14 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id AE9D86B0074; Fri, 22 Jul 2022 15:38:14 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id A14EB6B0072 for ; Fri, 22 Jul 2022 15:38:14 -0400 (EDT) Received: from smtpin27.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 548C0A0D45 for ; Fri, 22 Jul 2022 19:38:14 +0000 (UTC) X-FDA: 79715746908.27.40ADC87 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by imf14.hostedemail.com (Postfix) with ESMTP id DED84100088 for ; Fri, 22 Jul 2022 19:38:13 +0000 (UTC) Received: from zn.tnic (p200300ea97297665329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9729:7665:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id A74851EC0666; Fri, 22 Jul 2022 21:38:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1658518688; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=oqMlhQ+9AS8F60PcU1q78Rrrk17ahXV0byauFO5z1UU=; b=pfCUktwvWkG8U+aXBptEc75Naz9avVy8tj8mgVyoRbOzAP4tbeOUfcsyB1cEHRJQiRYHNN OszJAzeSOi6AAD3WDUvaBlLpfBrkiXm9Br3wdsTCPfwl/qdjJMF6lwdg4DjjaBwlGllUqz 9n5XyBv4JtYXEaGzrdzUq78AGYDJkNM= Date: Fri, 22 Jul 2022 21:38:04 +0200 From: Borislav Petkov To: Sean Christopherson Cc: "Kalra, Ashish" , Dave Hansen , "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" , "tglx@linutronix.de" , "mingo@redhat.com" , "jroedel@suse.de" , "Lendacky, Thomas" , "hpa@zytor.com" , "ardb@kernel.org" , "pbonzini@redhat.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" , "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" Subject: Re: [PATCH Part2 v6 05/49] x86/sev: Add RMP entry lookup helpers Message-ID: References: <99d72d58-a9bb-d75c-93af-79d497dfe176@intel.com> <5db37cc2-4fb1-7a73-c39a-3531260414d0@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1658518694; a=rsa-sha256; cv=none; b=oe58X64n1dfL7D/kaTi4zu2eOMo2rAArDJ3n0hG1EtlMHxk3rOajGuY514QrIsHiiT5ChN Es6fiPGPeQhyK2CD2ByxQtbCFLrZ4n0FYp6DiwWKSArc2E8UOyx/YpXJv5ziy6hQluIDFP Xip0w4MTRuuw4D9jb7Pkw5JhAfDlrpE= ARC-Authentication-Results: i=1; imf14.hostedemail.com; dkim=pass header.d=alien8.de header.s=dkim header.b=pfCUktwv; dmarc=pass (policy=none) header.from=alien8.de; spf=pass (imf14.hostedemail.com: domain of bp@alien8.de designates 5.9.137.197 as permitted sender) smtp.mailfrom=bp@alien8.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1658518694; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=oqMlhQ+9AS8F60PcU1q78Rrrk17ahXV0byauFO5z1UU=; b=1fdhnM1Oq4JyhNkicgdeyZuY9fEzdSGHelpWOWjkY8GpNy/aDA3+93Dzd78wyNUdZ7zpan ufogQBIMeaVNlYt/fdwZBtvJKua2mgoCtKM2oGj1wjU6bCNdhUmPuEIdMBESmItRr2+sNx k4+j0mDOfNiFu36kvHlymGaf2BciFco= X-Rspamd-Queue-Id: DED84100088 Authentication-Results: imf14.hostedemail.com; dkim=pass header.d=alien8.de header.s=dkim header.b=pfCUktwv; dmarc=pass (policy=none) header.from=alien8.de; spf=pass (imf14.hostedemail.com: domain of bp@alien8.de designates 5.9.137.197 as permitted sender) smtp.mailfrom=bp@alien8.de X-Rspam-User: X-Rspamd-Server: rspam07 X-Stat-Signature: qhpiyq4ptju6crhejin9ejyupm191xyp X-HE-Tag: 1658518693-391339 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Btw, what could work is to spec only a *version* field somewhere in the HW or FW which says which version the RMP header has. Then, OS would check that field and if it doesn't support that certain version, it'll bail. I'd need to talk to folks first, though, what the whole story is behind not spec-ing the RMP format... -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette