public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jarkko Sakkinen" <jarkko@kernel.org>,
	"Stefano Garzarella" <sgarzare@redhat.com>
Cc: "Dionna Amalie Glaze" <dionnaglaze@google.com>,
	"Jarkko Sakkinen" <jarkko.sakkinen@iki.fi>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"James Bottomley" <james.bottomley@hansenpartnership.com>,
	<linux-coco@lists.linux.dev>, "Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"Peter Huewe" <peterhuewe@gmx.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	<linux-integrity@vger.kernel.org>, <x86@kernel.org>,
	"Joerg Roedel" <jroedel@suse.de>, <linux-kernel@vger.kernel.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Claudio Carvalho" <cclaudio@linux.ibm.com>,
	"Dov Murik" <dovmurik@linux.ibm.com>,
	"Tom Lendacky" <thomas.lendacky@amd.com>
Subject: Re: [PATCH 3/3] x86/sev: add a SVSM vTPM platform device
Date: Thu, 23 Jan 2025 13:49:34 +0200	[thread overview]
Message-ID: <D79FHC9OB5WS.CCNDGUTDNG31@kernel.org> (raw)
In-Reply-To: <D79FFA5JMK7J.1GD3PSB11COGC@kernel.org>

On Thu Jan 23, 2025 at 1:46 PM EET, Jarkko Sakkinen wrote:
> On Thu Jan 23, 2025 at 12:09 PM EET, Stefano Garzarella wrote:
> > On Thu, Jan 23, 2025 at 11:50:40AM +0200, Jarkko Sakkinen wrote:
> > >On Wed Jan 22, 2025 at 11:29 PM EET, Dionna Amalie Glaze wrote:
> > >> I can appreciate this viewpoint. It even surfaced Microsoft's fTPM
> > >> paper to me, which solves some interesting problems we need to solve
> > >> in SVSM too. So thanks for that.
> > >>
> > >> Just to clarify, you're not asking for SVSM to implement the TIS-MMIO
> > >> interface instead, but rather to use the fTPM stack, which could make
> > >> SVSM calls a TEE device operation?
> > >
> > >I don't really know what I'm asking because this is barely even a
> > >PoC, and I state it like this knowingly.
> > >
> > >You should make the argument, and the case for the solution. Then
> > >it is my turn to comment on that scheme.
> >
> > I'll check if I can use fTPM, in the meantime I had started to simplify
> > this series, avoiding the double stack and exposing some APIs from SEV
> > to probe the vTPM and to send the commands. The final driver in
> > drivers/char/tpm would be quite simple.
> >
> > But I'll try to see if reusing fTPM is a feasible way, I like the idea.
> >
> > >
> > >That said, I would not give high odds for acceptance of a duplicate
> > >TPM stack succeeding.
> >
> > Got it ;-)
> >
> > Thanks to everyone for the helpful feedbacks!
> >
> > I've been a bit messy these days and I'm in FOSDEM next week, so I hope
> > not to take too long for the v2.
>
> Yeah, OK one thing that I want to say.
>
> Nail the story. What is it about what is the problem what is the
> motivation to solve it etc. If you have all that properly written
> up then it is easier to forgive not that well nailed code and
> give reasonable arguments.
>
> And don't rush, I have all the time in the world ;-)

Here the point is that if I don't fully understand the context
(starting explaining the obvious like what is SVSM) I might 
give some ridiculously wrong advice.

Then people come back to me and start blaming me on saying
opposite arguments. I hope you see where I'm standing here.
I neither don't want you to do useless and unproductive
work.

BR, Jarkko

  reply	other threads:[~2025-01-23 11:49 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 14:34 [PATCH 0/3] Enlightened vTPM support for SVSM on SEV-SNP Stefano Garzarella
2024-12-10 14:34 ` [PATCH 1/3] tpm: add generic platform device Stefano Garzarella
2024-12-12  9:51   ` Stefano Garzarella
2024-12-12 14:35     ` James Bottomley
2024-12-12 15:30       ` Stefano Garzarella
2024-12-12 15:41         ` James Bottomley
2024-12-12 16:12           ` Stefano Garzarella
2024-12-10 14:34 ` [PATCH 2/3] x86/sev: add SVSM call macros for the vTPM protocol Stefano Garzarella
2024-12-10 14:34 ` [PATCH 3/3] x86/sev: add a SVSM vTPM platform device Stefano Garzarella
2024-12-10 14:40   ` Jason Gunthorpe
2024-12-10 14:55     ` James Bottomley
2024-12-10 15:04       ` Jason Gunthorpe
2024-12-11  8:19         ` Stefano Garzarella
2024-12-11 15:00           ` Jason Gunthorpe
2024-12-11 15:38             ` Stefano Garzarella
2024-12-11 15:53               ` Jason Gunthorpe
2024-12-11 16:42                 ` Stefano Garzarella
2024-12-19 15:35             ` Stefano Garzarella
2024-12-19 15:40               ` Jarkko Sakkinen
2024-12-19 16:06                 ` Stefano Garzarella
2025-01-14 10:42                   ` Stefano Garzarella
2025-01-14 13:07                     ` Jason Gunthorpe
2025-01-14 16:51                       ` Stefano Garzarella
2025-01-14 17:33                         ` Jason Gunthorpe
2025-01-14 22:46                     ` Jarkko Sakkinen
2025-01-14 22:48                       ` Jarkko Sakkinen
2025-01-14 23:12                         ` Jarkko Sakkinen
2025-01-22 21:29                           ` Dionna Amalie Glaze
2025-01-23  9:50                             ` Jarkko Sakkinen
2025-01-23 10:09                               ` Stefano Garzarella
2025-01-23 11:46                                 ` Jarkko Sakkinen
2025-01-23 11:49                                   ` Jarkko Sakkinen [this message]
2025-01-23 12:29                                     ` Stefano Garzarella
2024-12-11 16:30   ` Tom Lendacky
2024-12-11 16:55     ` Stefano Garzarella
2024-12-11 17:02     ` James Bottomley
2024-12-13 11:48       ` Stefano Garzarella

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=D79FHC9OB5WS.CCNDGUTDNG31@kernel.org \
    --to=jarkko@kernel.org \
    --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=james.bottomley@hansenpartnership.com \
    --cc=jarkko.sakkinen@iki.fi \
    --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