From: Dan Williams <dan.j.williams@intel.com>
To: <linux-coco@lists.linux.dev>
Subject: Reminder: Out-of-cycle Kernel SIG call starting in ~30 minutes (8pm PDT)
Date: Thu, 19 Jun 2025 19:38:29 -0700 [thread overview]
Message-ID: <6854c9a527731_1f9e1005b@dwillia2-xfh.jf.intel.com.notmuch> (raw)
A few of us, ARM, AMD, Intel folks are getting together to talk through
next steps on advancing the private device assignment infrastructure for
the tsm.git#staging [1] branch. In particular, next steps on the proposed
interactions with and between DMABUF, VFIO, IOMMUFD, KVM, and TSM
drivers [2] [3].
https://zoom-lfx.platform.linuxfoundation.org/meeting/93219227394?password=80705486-101a-4e19-8f11-0baaf92104be
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/log/?h=staging
[2]: http://lore.kernel.org/20250529053513.1592088-1-yilun.xu@linux.intel.com
[3]: http://lore.kernel.org/20250529133757.462088-3-aneesh.kumar@kernel.org
reply other threads:[~2025-06-20 2:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6854c9a527731_1f9e1005b@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=linux-coco@lists.linux.dev \
/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).