From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com,
Anton Iacobaeus <anton.iacobaeus@canarybit.eu>
Subject: [pve-devel] applied: [PATCH qemu-server 1/1] Add support for TDX quote-generation-socket object
Date: Mon, 17 Nov 2025 15:04:02 +0100 [thread overview]
Message-ID: <176338779198.189087.15403021478648575715.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251117104817.471815-3-anton.iacobaeus@canarybit.eu>
On Mon, 17 Nov 2025 11:48:00 +0100, Anton Iacobaeus wrote:
> Extend the tdx object with the quote-generation-socket as defined in:
> https://www.qemu.org/docs/master/interop/qemu-storage-daemon-qmp-ref.html#object-QSD-qom.TdxGuestProperties
>
> Only vsock is included here since it is the most commonly used with TDX
> attestation.
Applied, thanks! I made some slight changes, most importantly not
exposing the socket type yet. Can still be added later with a default
for 'vsock' should we ever need it. Also changed the checks for 'cid'
and 'port' to be for definedness rather than boolean. And added
explicit coercion to strings in the object passed for JSON, since it's
like that in the QMP schema.
[1/1] Add support for TDX quote-generation-socket object
commit: bd0347878e824e249b1e919fe2fe2348e58d9316
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-17 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 10:47 [pve-devel] [PATCH manager/qemu-server 0/2] Add support for Intel TDX attestation Anton Iacobaeus
2025-11-17 10:47 ` [pve-devel] [PATCH manager 1/1] Add support for " Anton Iacobaeus
2025-11-17 16:33 ` [pve-devel] applied: " Fiona Ebner
2025-11-17 10:48 ` [pve-devel] [PATCH qemu-server 1/1] Add support for TDX quote-generation-socket object Anton Iacobaeus
2025-11-17 14:04 ` Fiona Ebner [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=176338779198.189087.15403021478648575715.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=anton.iacobaeus@canarybit.eu \
--cc=pve-devel@lists.proxmox.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