From: Jason Gunthorpe <jgg@nvidia.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"Christoph Hellwig" <hch@lst.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"Javier González" <javier@javigon.com>,
"Keith Busch" <kbusch@kernel.org>
Subject: Re: [LSF/MM/BFP ATTEND][LSF/MM/BFP TOPIC] BoF: NVMe VFIO Live Migration
Date: Thu, 9 Feb 2023 15:26:13 -0400 [thread overview]
Message-ID: <Y+VI1b+gztQE3rOD@nvidia.com> (raw)
In-Reply-To: <a0ef2710-43e5-b856-f9ce-e6f1ba99df51@nvidia.com>
On Thu, Feb 02, 2023 at 02:13:38AM +0000, Chaitanya Kulkarni wrote:
>
> Hi,
>
> Since I've conducted NVMe VFIO Live Migration talk at SNIA SDC 2022 [1],
> there has been significant development in this area in the NVMe TWG and
> on the mailing list with RFC kernel implementation posted by Intel [2].
>
> Although RFC implementation is far from the actual implementation since
> there is no support for the standards for NVMe Live Migration
> commands, it did bring up some interesting points about how the
> kernel implementation would look like especially between VFIO and NVMe
> subsystem.
>
> I'd like to propose a BoF session for NVMe Live Migration and
> discuss what are the kernel side implementation issues we need to
> address apart from the discussion we had on [2].
Sounds like a good opportunity to discuss the Linux side of this
implementation.
By LSF/MM we should be quite far along alot of the migration ecosystem
work in kernel/qemu/libvirt/etc
Thanks,
Jason
prev parent reply other threads:[~2023-02-09 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 2:13 [LSF/MM/BFP ATTEND][LSF/MM/BFP TOPIC] BoF: NVMe VFIO Live Migration Chaitanya Kulkarni
2023-02-06 22:49 ` Chaitanya Kulkarni
2023-02-09 19:26 ` Jason Gunthorpe [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=Y+VI1b+gztQE3rOD@nvidia.com \
--to=jgg@nvidia.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=javier@javigon.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.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