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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1FF5DC433EF for ; Tue, 19 Jul 2022 19:14:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239010AbiGSTOC (ORCPT ); Tue, 19 Jul 2022 15:14:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234410AbiGSTOB (ORCPT ); Tue, 19 Jul 2022 15:14:01 -0400 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2C31F474F1; Tue, 19 Jul 2022 12:13:59 -0700 (PDT) Received: from zn.tnic (p200300ea97297609329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9729:7609: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 74F971EC0138; Tue, 19 Jul 2022 21:13:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1658258034; 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=YtDNrDoiP/YwCtnXFCAYb4Hl8NXDzFtCiOlz4jSq9Ro=; b=n73dc2tkN7SSfchiNt09DoO+Giut6lvnYRRC54C8OBl/IBIvIFfEmvXNcPAB+ZeDqQkg0x mBmdpV8Dpf28ML3SjyDkGrIK+sG14tR2GB2DHtIaifH68mRCkhPCrDTIpGPq0Ad/fnAEuO VPyM9cE+UpZjUFVK/qLcV7rzun1mF+o= Date: Tue, 19 Jul 2022 21:13:50 +0200 From: Borislav Petkov To: Dionna Amalie Glaze Cc: "Kirill A. Shutemov" , Ard Biesheuvel , Peter Gonda , Andy Lutomirski , Sean Christopherson , Andrew Morton , Joerg Roedel , Andi Kleen , Kuppuswamy Sathyanarayanan , David Rientjes , Vlastimil Babka , Tom Lendacky , Thomas Gleixner , Peter Zijlstra , Paolo Bonzini , Ingo Molnar , Varad Gautam , Dario Faggioli , Dave Hansen , Mike Rapoport , David Hildenbrand , Marcelo Cerri , tim.gardner@canonical.com, Khalid ElMously , philip.cox@canonical.com, the arch/x86 maintainers , Linux Memory Management List , linux-coco@lists.linux.dev, linux-efi , LKML , "Yao, Jiewen" Subject: Re: [PATCHv7 00/14] mm, x86/cc: Implement support for unaccepted memory Message-ID: References: <20220627122230.7eetepoufd5w3lxd@black.fi.intel.com> <20220627223808.ihgy3epdx6ofll43@black.fi.intel.com> <20220718172159.4vwjzrfthelovcty@black.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 19, 2022 at 11:29:32AM -0700, Dionna Amalie Glaze wrote: > How about instead of the limited resource of UTS_VERSION, we add a > SETUP_BOOT_FEATURES enum for setup_data in the boot header? That would > be easier to parse out and more extensible in the future. > https://www.kernel.org/doc/html/latest/x86/boot.html?highlight=boot > > This can contain a bitmap of a number of features that we currently > need manual tagging for, such as SEV guest support, SEV-SNP guest > support, TDX guest support, and (CONFIG_UNACCEPTED_MEMORY, TDX) or > (CONFIG_UNACCEPTED_MEMORY, SEV-SNP). > The VMM, UEFI, or boot loader can read these from the images/kernels > and have the appropriate behavior. I think for stuff like that you want loadflags or xloadflags in the setup header. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette