From: Jarkko Sakkinen <jarkko@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Stefano Garzarella <sgarzare@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-coco@lists.linux.dev, linux-integrity@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, Tom Lendacky <thomas.lendacky@amd.com>,
Joerg Roedel <jroedel@suse.de>,
Dionna Glaze <dionnaglaze@google.com>,
Claudio Carvalho <cclaudio@linux.ibm.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-kernel@vger.kernel.org, Dov Murik <dovmurik@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v6 0/4] Enlightened vTPM support for SVSM on SEV-SNP
Date: Mon, 7 Apr 2025 21:14:46 +0300 [thread overview]
Message-ID: <Z_QWFjJbPWIsBP2s@kernel.org> (raw)
In-Reply-To: <20250407134643.GDZ_PXQ0OlzcMjiGgp@fat_crate.local>
On Mon, Apr 07, 2025 at 03:46:43PM +0200, Borislav Petkov wrote:
> On Thu, Apr 03, 2025 at 12:09:38PM +0200, Stefano Garzarella wrote:
> > Stefano Garzarella (4):
> > x86/sev: add SVSM vTPM probe/send_command functions
> > svsm: add header with SVSM_VTPM_CMD helpers
> > tpm: add SNP SVSM vTPM driver
> > x86/sev: register tpm-svsm platform device
> >
> > arch/x86/include/asm/sev.h | 9 +++
> > include/linux/tpm_svsm.h | 149 ++++++++++++++++++++++++++++++++++++
> > arch/x86/coco/sev/core.c | 67 ++++++++++++++++
> > drivers/char/tpm/tpm_svsm.c | 128 +++++++++++++++++++++++++++++++
> > drivers/char/tpm/Kconfig | 10 +++
> > drivers/char/tpm/Makefile | 1 +
> > 6 files changed, 364 insertions(+)
> > create mode 100644 include/linux/tpm_svsm.h
> > create mode 100644 drivers/char/tpm/tpm_svsm.c
>
> Jarrko,
>
> should I take the whole bunch through the tip tree?
>
> No point in splitting between two trees...
It's cleanly separated and does not even touch any shared headers,
so I don't see any issues on doing that. I.e., I'm with it :-)
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
>
BR, Jarkko
prev parent reply other threads:[~2025-04-07 18:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 10:09 [PATCH v6 0/4] Enlightened vTPM support for SVSM on SEV-SNP Stefano Garzarella
2025-04-03 10:09 ` [PATCH v6 1/4] x86/sev: add SVSM vTPM probe/send_command functions Stefano Garzarella
2025-04-03 10:09 ` [PATCH v6 2/4] svsm: add header with SVSM_VTPM_CMD helpers Stefano Garzarella
2025-04-03 10:09 ` [PATCH v6 3/4] tpm: add SNP SVSM vTPM driver Stefano Garzarella
2025-04-03 19:05 ` Jarkko Sakkinen
2025-04-09 9:43 ` Stefano Garzarella
2025-04-09 14:21 ` Jarkko Sakkinen
2025-04-04 17:31 ` Dionna Amalie Glaze
2025-04-04 18:37 ` Stefano Garzarella
2025-04-04 18:58 ` Dionna Amalie Glaze
2025-04-09 9:45 ` Stefano Garzarella
2025-04-03 10:09 ` [PATCH v6 4/4] x86/sev: register tpm-svsm platform device Stefano Garzarella
2025-04-03 19:06 ` Jarkko Sakkinen
2025-04-08 11:00 ` Borislav Petkov
2025-04-08 11:08 ` Stefano Garzarella
2025-04-08 11:28 ` Borislav Petkov
2025-04-08 11:54 ` Stefano Garzarella
2025-04-09 10:21 ` Borislav Petkov
2025-04-09 10:43 ` Stefano Garzarella
2025-04-09 11:31 ` Borislav Petkov
2025-04-09 12:22 ` James Bottomley
2025-04-09 15:09 ` Stefano Garzarella
2025-04-09 18:38 ` Borislav Petkov
2025-04-09 16:07 ` Tom Lendacky
2025-04-09 16:51 ` Stefano Garzarella
2025-04-09 18:45 ` Borislav Petkov
2025-04-09 19:16 ` Tom Lendacky
2025-04-10 8:15 ` Stefano Garzarella
2025-04-07 13:46 ` [PATCH v6 0/4] Enlightened vTPM support for SVSM on SEV-SNP Borislav Petkov
2025-04-07 18:14 ` Jarkko Sakkinen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z_QWFjJbPWIsBP2s@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bp@alien8.de \
--cc=cclaudio@linux.ibm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dionnaglaze@google.com \
--cc=dovmurik@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jgg@ziepe.ca \
--cc=jroedel@suse.de \
--cc=linux-coco@lists.linux.dev \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterhuewe@gmx.de \
--cc=sgarzare@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).