[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <xfwwxtkphwlkrpemprdyju6zahwh43tijdlbzivtokqtcfvvxw@a4ujdfs744tm>
Date: Thu, 10 Apr 2025 10:15:31 +0200
From: Stefano Garzarella <sgarzare@...hat.com>
To: Tom Lendacky <thomas.lendacky@....com>
Cc: Borislav Petkov <bp@...en8.de>, Jarkko Sakkinen <jarkko@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>, Peter Huewe <peterhuewe@....de>, Jason Gunthorpe <jgg@...pe.ca>,
"H. Peter Anvin" <hpa@...or.com>, linux-coco@...ts.linux.dev, linux-integrity@...r.kernel.org,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org, Joerg Roedel <jroedel@...e.de>,
Dionna Glaze <dionnaglaze@...gle.com>, Claudio Carvalho <cclaudio@...ux.ibm.com>,
James Bottomley <James.Bottomley@...senpartnership.com>, linux-kernel@...r.kernel.org, Dov Murik <dovmurik@...ux.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v6 4/4] x86/sev: register tpm-svsm platform device
On Wed, Apr 09, 2025 at 02:16:40PM -0500, Tom Lendacky wrote:
>On 4/9/25 13:45, Borislav Petkov wrote:
>> On Wed, Apr 09, 2025 at 11:07:49AM -0500, Tom Lendacky wrote:
>>> So the vTPM driver wouldn't change, just snp_init_platform_device():
>>>
>>> if (snp_vmpl && platform_device_register(&tpm_svsm_device))
>>
>> So this basically says that the SVSM is always sporting a vTPM emulation. But
>> you can build the cocont-svsm thing without it AFAICT.
>>
>> So I'm guessing Stefano's suggestion here might make more sense:
>>
>> https://lore.kernel.org/r/o2u7p3wb64lcc4sziunr274hyubkgmspzdjcvihbpzkw6mkvpo@sjq3vi4y2qfl
>>
>> considering it all...
>
>That way works for me, too.
Okay, it looks like we have an agreement! I'll apply that and send v7.
Thanks,
Stefano
Powered by blists - more mailing lists