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 6CAC4C4707B for ; Tue, 9 Jan 2024 22:08:41 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E87AC6B00B3; Tue, 9 Jan 2024 17:08:40 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id E11256B00B4; Tue, 9 Jan 2024 17:08:40 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id C89D56B00B5; Tue, 9 Jan 2024 17:08:40 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id B091B6B00B3 for ; Tue, 9 Jan 2024 17:08:40 -0500 (EST) Received: from smtpin28.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id 8C280409B0 for ; Tue, 9 Jan 2024 22:08:40 +0000 (UTC) X-FDA: 81661162800.28.242BC8C Received: from mail.alien8.de (mail.alien8.de [65.109.113.108]) by imf28.hostedemail.com (Postfix) with ESMTP id 2DF5CC001B for ; Tue, 9 Jan 2024 22:08:37 +0000 (UTC) Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=alien8.de header.s=alien8 header.b=NCRmx0F1; spf=pass (imf28.hostedemail.com: domain of bp@alien8.de designates 65.109.113.108 as permitted sender) smtp.mailfrom=bp@alien8.de; dmarc=pass (policy=none) header.from=alien8.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1704838118; 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=worxUdT9KOJEranFxZps6GXVgd62mc3IxDyhlGzs0cY=; b=eF+QtOrvU0/mAWdQYPRyyowzvrlTUieYAguZgiXl+BeL4mlVtcHwhykq4rnircxFX2p/xI 9dskF/8du5ZjmJGxJ4AAMNeUSQ+0H3UZW7ljgEw7cKWwUoIgb0yXJFzb9wUUw9tsUnKWgq ZHUosXiRBrpdLPwcAHLJSYwn6ipyVX0= ARC-Authentication-Results: i=1; imf28.hostedemail.com; dkim=pass header.d=alien8.de header.s=alien8 header.b=NCRmx0F1; spf=pass (imf28.hostedemail.com: domain of bp@alien8.de designates 65.109.113.108 as permitted sender) smtp.mailfrom=bp@alien8.de; dmarc=pass (policy=none) header.from=alien8.de ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1704838118; a=rsa-sha256; cv=none; b=W4sRy9soaDe5T0I18ouxpeSOgzjcj5mDRHTgm/mBkuG5+/hCIMKurgG1ynAmOcgulGNb3p Bhu73n3xezbYritZ3HoLjDhxUeCLDYAsgvzEDb/+CsRGLUVKjoGgzz021lKW0FKa9MkLUY 8bfzWy4Weq2cEdFItFsJu+s1WuaWFEY= Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.alien8.de (SuperMail on ZX Spectrum 128k) with ESMTP id 2EB3A40E01B2; Tue, 9 Jan 2024 22:08:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.alien8.de Received: from mail.alien8.de ([127.0.0.1]) by localhost (mail.alien8.de [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id KiOhwCe-g0qp; Tue, 9 Jan 2024 22:08:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=alien8; t=1704838112; bh=worxUdT9KOJEranFxZps6GXVgd62mc3IxDyhlGzs0cY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NCRmx0F1AvON411bFZmisI9EYkIitCHfOHXNYd/eCzvNPdZfDISwu7fxP5jInn05r Y7lHFxA3DeKeTHPE930sls+OiWOCmJluo7488AyOZIeKFkRBkXl2iUXCM8GGAreu2s nFVP+KSf04QKZX8XUej+18buuwurHIpE5XqekAMmpz6b5D4hIg7C9Vq8JnfDSvK7Sy qU7lJntAy1iA9V0KB54lFK7akmoJKnPsdVXl5AolCQBWq9w9WIZwHY6WUxvlUroeg0 diJ9wGF38YnE3SZilIAzaW5qNKm2F9v1diPgYGTnNwzJXVyHBtrRIfSRqsapjUEATl CgmEb2dNA4CxcF/AJXsFTCxWsREDxUH2GiD+OhVGLIRJyKhH66wOWD01MkSsnjfjM5 AkSZF01kqKAu+GP9zgYSV8pKHeGnbktYaoFbibduOXOGpbiutLCXU2O9aHjtJ//yYM qfekQTSH0ZeRz8qcU6k66AkfK9KgngakBU6iZQwadHQM9UkvyqXiu7tX4RYyPA641c T+xwcwaFrEkuXAle/ZJdyJlEWyG42lZfjFyclRehF8GfV6jAqmGNWv26aQm0zdHwn4 Cc+99gALtyJcjitB/MLC0x+ZYPEpwh4qBL7mc4fL8Kfm7T4aQubP2IeUc2hPA7eLVs D5BX6VxTFc2YtIkwtP3VCTyY= Received: from zn.tnic (pd9530f8c.dip0.t-ipconnect.de [217.83.15.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail.alien8.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 7C72340E016C; Tue, 9 Jan 2024 22:07:52 +0000 (UTC) Date: Tue, 9 Jan 2024 23:07:46 +0100 From: Borislav Petkov To: Michael Roth Cc: kvm@vger.kernel.org, linux-coco@lists.linux.dev, linux-mm@kvack.org, linux-crypto@vger.kernel.org, x86@kernel.org, linux-kernel@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, vbabka@suse.cz, kirill@shutemov.name, ak@linux.intel.com, tony.luck@intel.com, sathyanarayanan.kuppuswamy@linux.intel.com, alpergun@google.com, jarkko@kernel.org, ashish.kalra@amd.com, nikunj.dadhania@amd.com, pankaj.gupta@amd.com, liam.merwick@oracle.com, zhi.a.wang@intel.com, Brijesh Singh Subject: Re: [PATCH v10 07/50] x86/sev: Add RMP entry lookup helpers Message-ID: <20240109220746.GAZZ3DsouxpiUPeBVN@fat_crate.local> References: <20231016132819.1002933-1-michael.roth@amd.com> <20231016132819.1002933-8-michael.roth@amd.com> <20231114142442.GCZVODKh03BoMFdlmj@fat_crate.local> <20231219033150.m4x6yh6udupkdqaa@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20231219033150.m4x6yh6udupkdqaa@amd.com> X-Rspamd-Queue-Id: 2DF5CC001B X-Rspam-User: X-Stat-Signature: xqk1s7wwwp976cxi9b3ck38ryhqxbay1 X-Rspamd-Server: rspam01 X-HE-Tag: 1704838117-12678 X-HE-Meta: U2FsdGVkX1/rqF0kYJUJ4j52A2LlhvZ8NK81aO4f/pMXNkarbNZzdhQ4Oij5ABVvxk8Yqbn0U1HqKKYk4OWONwK17RJKgvaCiKYzPsISmKzARRZtjGUjur7pWUtULJxk3zVbyTwC9KhpGoeUEopC21iYUV1PDP07Vu/n0SwEDhPx2Uztykvx6uz74D2Wd5kyEZXOsLF4z+5llwEHzwgxm2CbFSWirTqvLwMQkRjkuU0FVenw6OlrRJwx7HObqrDmphrfhyBUPbVrrqRRQeAYi3T3zK6GIsGMjcuP4S+cuz6jqoYIzVJO8EopyAl3KT5TJf/RtYXAjz5V4Q7JWkNGHirVrbloLATGKeN3FNAgCqEHeIKqqLvNXjaqmIs05bTNMBrNtk7Pa9zJM2MLPNQEkO2alKT6W81RTAF9AWYkA/8cxCtcv9WKYxB7qXwaEXbDA7PutIImMX5CAZw33VKu0mn3G8ptjQNiovm0qIHWMkdbUexmDTOcrrWhqrrIJ3KiOLjoy04BrKj+b3Y1Hg8tB5Kg1OrSLUocAwvaZ3rAKEj9SyrVwUqjRxTwiGKTXgrvXew0cyQmjuPWVQaj6nr4uLvs0wYkUKr7fcd0n1a9FxtRbnxU+zwipNk/twlrMDwYsHrV3wrrCyUzr4SXYZZ339AffZGSWwSdaQKOjfLV3MEeA3IT9WeiVtsa7nGgrqVHuSmgNv8zlYH0zUZesaOkxdlqTiq5DkV/4ih1i9K92wh+4MFLoLtw0UC0nYoyRpHe293M8GTSGtGR6tzvjiDyAoVuGQZhDskQiiHaAiik2dmcgYgI+aDNRh/xbQysZ4ApHLUBI7pILI+CaOQJuN+JUJiH3THo9SOlbN5H2E69+XgPrnK2cQi/HpE0UGWs1ftl07gx2F0xKMZa/4ATfcLaCHRa2EQ4hwzimT4R1bbGuhUMrDYxl0/vcliuYFhNnFOmJ1NEpuQcOe6Ur+UEDKg 5C794AAB hhaTvprxRt70CK/NMwel/9qJHMNuoXRMzt8KwPTvTGUCcQYx3kvl3Fr//1IPh75f6H6GgpzGlzCspfVSVsDIkWKwT76Wm8czX3RR18SonDHyzK+2/x22RQRzW1AvTxBCz7HonZydYnxtCl9du3aMes5OZhUfWOcqHql4Y1P0tEAa4f6ruFzIAmRQyvMBaMObZX4RsAE42JYeqbTQ= 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: List-Subscribe: List-Unsubscribe: On Mon, Dec 18, 2023 at 09:31:50PM -0600, Michael Roth wrote: > I've moved this to sev.h, but it RMP_PG_SIZE_4K is already defined there > and used by a bunch of guest code so it's a bit out-of-place to update > those as part of this patchset. I can send a follow-up series to clean up > some of the naming and get rid of sev-common.h Yap, good idea. > Doesn't seem like it would be an issue, maybe some fallout from any > files that previously only included sev-common.h and now need to pull in > guest struct definitions as well, but those definitions don't have a lot > of external dependencies so don't anticipate any header include > hellishness. I'll send that as a separate follow-up, along with some of > the renames you suggested above since they'll touch guest code and > create unecessary churn for SNP host support. OTOH, people recently have started looking at including only that stuff which is really used so having a single header would cause more preprocessing effort. I'm not too crazy about it as the preprocessing overhead is barely measurable so might as well have a single header and then split it later... Definitely something for the after-burner and not important right now. Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette