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 5306CC43217 for ; Tue, 15 Nov 2022 16:27:27 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 8373C6B0072; Tue, 15 Nov 2022 11:27:26 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 7E77C6B0073; Tue, 15 Nov 2022 11:27:26 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6AEC78E0002; Tue, 15 Nov 2022 11:27:26 -0500 (EST) 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 5B7B06B0072 for ; Tue, 15 Nov 2022 11:27:26 -0500 (EST) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id F2093140961 for ; Tue, 15 Nov 2022 16:27:25 +0000 (UTC) X-FDA: 80136206850.20.796E4DA Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by imf24.hostedemail.com (Postfix) with ESMTP id F10A6180017 for ; Tue, 15 Nov 2022 16:27:18 +0000 (UTC) Received: from zn.tnic (p200300ea9733e7da329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9733:e7da: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 F0DB91EC02AD; Tue, 15 Nov 2022 17:27:15 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1668529636; 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=rqKIUpJn3nuSltSmzhMF2AZfwfkeGnGGGviR3ix9tLg=; b=mejjCFr9kN4KR9WGJSUq/Be8o4tEwH/lc5S4fwqi2vbY822ufKa0pQR5vK6vWnDWoXFJEg uw11kiWVcBoHglbEPF8K6WOiFUS2d8AorPN5Nys5XjJuAAy0CRlcecCpx++70Jjg96KZQX V2sGDC+J4ua9VYHLBcwPcohp3KOjn/Y= Date: Tue, 15 Nov 2022 17:27:12 +0100 From: Borislav Petkov To: "Kalra, Ashish" Cc: Vlastimil Babka , 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, 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, michael.roth@amd.com, 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, "Kaplan, David" , Naoya Horiguchi , Miaohe Lin , Oscar Salvador Subject: Re: [PATCH Part2 v6 14/49] crypto: ccp: Handle the legacy TMR allocation when SNP is enabled Message-ID: References: <380c9748-1c86-4763-ea18-b884280a3b60@amd.com> <6511c122-d5cc-3f8d-9651-7c2cd67dc5af@amd.com> <7882353e-2b13-d35a-b462-cef35ee56f51@suse.cz> 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=1668529645; a=rsa-sha256; cv=none; b=CvLCmIfvnpe+riZlmFHPYsZ26UqO/MGjSinWdAtl1b4tfS7eSuIJ8Hx+Ff/YYwdQ1kcYZn lomYg9i7vMEGHoYb5JIVwVJvUT9UPPCzpTRoOFd+2daGsImUoUstts4fWW73YUOcf3guOt 5CEVnDilkB9fssAiHBcWVwpYXIeHG+4= ARC-Authentication-Results: i=1; imf24.hostedemail.com; dkim=temperror ("DNS error when getting key") header.d=alien8.de header.s=dkim header.b=mejjCFr9; dmarc=temperror reason="SPF/DKIM temp error" header.from=alien8.de (policy=temperror); spf=temperror (imf24.hostedemail.com: error in processing during lookup of bp@alien8.de: DNS error) smtp.mailfrom=bp@alien8.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1668529645; 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=rqKIUpJn3nuSltSmzhMF2AZfwfkeGnGGGviR3ix9tLg=; b=xWDTxFlesqlbgyUKJxt+/Hbm3/bVqCx+0h3JndycnkYQGuHIIxRHn6pk2OkLqfpj1JJ27k fvm0EhOp1Ow1vPnzBbNsxh+9eYdlSByAnlHKFSWVCd2U3jcAT/JtC5XoxhLRJ0H0c2mtzL 8nMVK6X7fWpkgtrbcjO8grMDraI1efI= X-Rspamd-Queue-Id: F10A6180017 X-Rspam-User: Authentication-Results: imf24.hostedemail.com; dkim=temperror ("DNS error when getting key") header.d=alien8.de header.s=dkim header.b=mejjCFr9; dmarc=temperror reason="SPF/DKIM temp error" header.from=alien8.de (policy=temperror); spf=temperror (imf24.hostedemail.com: error in processing during lookup of bp@alien8.de: DNS error) smtp.mailfrom=bp@alien8.de X-Rspamd-Server: rspam06 X-Stat-Signature: oas7ers5ritqisbb3wkkzopub8sdfnb8 X-HE-Tag: 1668529638-879731 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000001, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: And, as dhansen connected the dots, this should be the exact same protection scenario as UPM: https://lore.kernel.org/all/20221025151344.3784230-1-chao.p.peng@linux.intel.com so you should be able to mark them inaccessible the same way and you won't need any poisoning dance. And Michael has patches so you probably should talk to him... Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette