public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <djbw@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
	 "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	 "michael.roth@amd.com" <michael.roth@amd.com>,
	 "Xu, Yilun" <yilun.xu@intel.com>,
	 "djbw@kernel.org" <djbw@kernel.org>,
	 "Weiny, Ira" <ira.weiny@intel.com>
Subject: Re: PUCK follow up: Trusted IO call details
Date: Thu, 16 Apr 2026 19:37:43 -0700	[thread overview]
Message-ID: <69e19cf75b5e9_147c8010018@djbw-dev.notmuch> (raw)
In-Reply-To: <CABgObfasYTWmuqkz4TaTprcivwkzKGxAjdYZJVgO66HB1wK-5w@mail.gmail.com>

Paolo Bonzini wrote:
> On Wed, Apr 15, 2026 at 8:59 PM Edgecombe, Rick P
> <rick.p.edgecombe@intel.com> wrote:
> >
> > The call I mentioned is officially called: "TAC Subcommittee: Linux Kernel Special Interest Group (Linux
> > Kernel-SIG)". This seems to be the info:
> > https://confidentialcomputing.io/about/committees/#Linux-Kernel-SIG
> >
> > Paolo, unfortunately I did remember correctly that it is not an EU friendly time.
> 
> This one is friendly (9AM PST = 6PM CEST). The unfriendly one is the
> IOMMUFD one (5AM :)).

There are couple topics at present that would be suitable to raise at
the EU-US friendly time. Specifically whether all of the per-arch
implementations of "transport large attestation evidence blobs over
shared memory from host-to-guest" would be better served with a shared
generic transport (simple virtio-pipe / something equivalent for vmbus
to publish).

Then there are the next steps with the uapi to convey PCI device
attestation that was proposed here [1], and also discussed as part of
the Rust SPDM proposal [2].

[1]: http://lore.kernel.org/20260303000207.1836586-9-dan.j.williams@intel.com
[2]: http://lore.kernel.org/69976d7d39c60_2f4a1009@dwillia2-mobl4.notmuch

  parent reply	other threads:[~2026-04-17  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15 18:59 PUCK follow up: Trusted IO call details Edgecombe, Rick P
2026-04-16  8:54 ` Xu Yilun
2026-04-16 12:59 ` Paolo Bonzini
2026-04-16 17:31   ` Edgecombe, Rick P
2026-04-17  2:37   ` Dan Williams [this message]
2026-04-17 19:51     ` James Bottomley

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=69e19cf75b5e9_147c8010018@djbw-dev.notmuch \
    --to=djbw@kernel.org \
    --cc=ira.weiny@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=yilun.xu@intel.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