From: Alistair Francis <alistair23@gmail.com>
To: qemu-devel@nongnu.org, hchkuo@avery-design.com.tw,
cbrowy@avery-design.com
Cc: mst@redhat.com, marcel.apfelbaum@gmail.com, alistair23@gmail.com,
Alistair Francis <alistair.francis@wdc.com>
Subject: [RFC v1 0/3] Initial support for SPDM
Date: Tue, 8 Aug 2023 11:51:21 -0400 [thread overview]
Message-ID: <cover.1691509717.git.alistair.francis@wdc.com> (raw)
The Security Protocol and Data Model (SPDM) Specification defines
messages, data objects, and sequences for performing message exchanges
over a variety of transport and physical media.
- https://www.dmtf.org/sites/default/files/standards/documents/DSP0274_1.3.0.pdf
This series is a very initial start on adding SPDM support to QEMU.
This series uses libspdm [1] which is a reference implementation of
SPDM.
The series starts by adding support for building and linking with
libspdm. It then progresses to handling SPDM requests in the NVMe device
over the PCIe DOE protocol.
This is a very early attempt. The code quality is not super high, the C
code hasn't been tested at all. This is really just an RFC to see if
QEMU will accept linking with libspdm.
So, the main question is, how do people feel about linking with libspdm
to support SPDM?
1: https://github.com/DMTF/libspdm
Alistair Francis (3):
subprojects: libspdm: Initial support
hw: nvme: ctrl: Initial support for DOE
hw: nvme: ctrl: Process SPDM requests
meson.build | 78 +++++++++++++++++++++++++++++++++++
hw/nvme/nvme.h | 4 ++
include/hw/pci/pcie_doe.h | 1 +
hw/nvme/ctrl.c | 35 ++++++++++++++++
.gitmodules | 3 ++
meson_options.txt | 3 ++
scripts/meson-buildoptions.sh | 3 ++
subprojects/.gitignore | 1 +
subprojects/libspdm.wrap | 5 +++
9 files changed, 133 insertions(+)
create mode 100644 subprojects/libspdm.wrap
--
2.41.0
next reply other threads:[~2023-08-08 15:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 15:51 Alistair Francis [this message]
2023-08-08 15:51 ` [RFC v1 1/3] subprojects: libspdm: Initial support Alistair Francis
2023-08-08 15:51 ` [RFC v1 2/3] hw: nvme: ctrl: Initial support for DOE Alistair Francis
2023-08-08 15:51 ` [RFC v1 3/3] hw: nvme: ctrl: Process SPDM requests Alistair Francis
2023-08-09 12:11 ` [RFC v1 0/3] Initial support for SPDM Jonathan Cameron via
2023-08-09 16:45 ` Alistair Francis
2023-08-10 10:18 ` Jonathan Cameron via
2023-08-11 16:09 ` Alistair Francis
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=cover.1691509717.git.alistair.francis@wdc.com \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=cbrowy@avery-design.com \
--cc=hchkuo@avery-design.com.tw \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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).