[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d39e428e-9bba-4319-bd72-ece8e39012e1@intel.com>
Date: Tue, 10 Jun 2025 08:02:59 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Nikolay Borisov <nik.borisov@...e.com>, Chao Gao <chao.gao@...el.com>
Cc: linux-coco@...ts.linux.dev, x86@...nel.org, kvm@...r.kernel.org,
seanjc@...gle.com, pbonzini@...hat.com, eddie.dong@...el.com,
kirill.shutemov@...el.com, dan.j.williams@...el.com, kai.huang@...el.com,
isaku.yamahata@...el.com, elena.reshetova@...el.com,
rick.p.edgecombe@...el.com, Farrah Chen <farrah.chen@...el.com>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 03/20] x86/virt/seamldr: Introduce a wrapper for
P-SEAMLDR SEAMCALLs
On 6/9/25 23:52, Nikolay Borisov wrote:
> Then just have TDX select FW_UPLOAD/FW_LOADER and be done with it.
> Still, let's hear other opinions but in this case I'd say size
> considerations aren't major so let's make it simpler for the user.
In general, those of us at hardware companies like to mint lots of
Kconfig options. Folks like Nikolay at the distros have to deal with
fallout from the piles of Kconfig options.
I tend to be pretty deferential to the distro guys on matters like this.
I haven't heard anything even remotely compelling that we need a
user-visible Kconfig option for this.
Powered by blists - more mailing lists