From: Lukas Wunner <lukas@wunner.de>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Ira Weiny <ira.weiny@intel.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
linux-pci@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
Adam Manzanares <a.manzanares@samsung.com>,
"ben@bwidawsk.net" <ben@bwidawsk.net>,
linuxarm@huawei.com, lorenzo.pieralisi@arm.com, "Box,
David E" <david.e.box@intel.com>,
Chuck Lever <chuck.lever@oracle.com>,
Krzysztof Wilczy??ski <kw@linux.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: (SPDM) Device attestation, secure channels from host to device etc: Discuss at Plumbers?
Date: Mon, 20 Jun 2022 18:52:17 +0200 [thread overview]
Message-ID: <20220620165217.GA18451@wunner.de> (raw)
In-Reply-To: <20220617112124.00002296@Huawei.com>
On Fri, Jun 17, 2022 at 11:21:24AM +0100, Jonathan Cameron wrote:
> On Thu, 9 Jun 2022 07:22:01 -0700 Ira Weiny <ira.weiny@intel.com> wrote:
> > On Thu, Jun 09, 2022 at 12:47:02PM +0100, Jonathan Cameron wrote:
> > > I'll start by saying I haven't moved forward much with the
> > > SPDM/CMA over Data Object Exchange proposal from the PoC that led to
> > > presenting it last year as part of the PCI etc uconf last year.
> > > https://lpc.events/event/11/contributions/1089/
> > > https://lore.kernel.org/all/20220303135905.10420-1-Jonathan.Cameron@huawei.com/
> > > I'm continuing to carry the QEMU emulation but not posted for a while
> > > as we are slowly working through a backlog of CXL stuff to merge.
So the SDPM series you posted in March is the latest version?
If you lack bandwidth to carry on with it, I would pick up the baton
and rework that version based on the review feedback I've posted.
(Unless someone else is eager to do that.)
> > Yes, while this could work as part of the CXL uconf it is probably a more
> > general topic.
>
> Maybe steal time from PCI given CXL uconf is going to be busy!
> (lets see if any of the PCI folk are reading this thread.. :)
>
> At the moment I'm not seeing enough interest to put in a proposal for
> anything 'officially scheduled', but there is a bit more time until
> the deadline so let's see if we get any other interest in that time.
How about a BoF session to discuss the status quo and any open issues?
(I'm not involved with CXL, hence probably belong to "PCI folk".)
> > I [...] was hoping to go in person but I'm unsure of travel budgets.
> > I will likely be virtual if I can't attend in person.
Same.
Thanks,
Lukas
next prev parent reply other threads:[~2022-06-20 16:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 11:47 (SPDM) Device attestation, secure channels from host to device etc: Discuss at Plumbers? Jonathan Cameron
2022-06-09 14:22 ` Ira Weiny
2022-06-17 10:21 ` Jonathan Cameron
2022-06-20 16:52 ` Lukas Wunner [this message]
2022-06-22 11:46 ` Jonathan Cameron
2022-06-24 11:08 ` Jonathan Cameron
2022-06-24 14:15 ` Lukas Wunner
2022-06-24 14:32 ` Jonathan Cameron
2022-06-29 16:01 ` Adam Manzanares
2022-09-06 11:59 ` Jonathan Cameron
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=20220620165217.GA18451@wunner.de \
--to=lukas@wunner.de \
--cc=Jonathan.Cameron@Huawei.com \
--cc=a.manzanares@samsung.com \
--cc=ben@bwidawsk.net \
--cc=bhelgaas@google.com \
--cc=chuck.lever@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=david.e.box@intel.com \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=kw@linux.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
/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).