From: Alex Williamson <alex.williamson@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Yishai Hadas <yishaih@nvidia.com>,
saeedm@nvidia.com, kvm@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, leonro@nvidia.com, maorg@nvidia.com,
cohuck@redhat.com
Subject: Re: [PATCH mlx5-next 0/5] Improve mlx5 live migration driver
Date: Wed, 4 May 2022 16:48:17 -0600 [thread overview]
Message-ID: <20220504164817.348f5fd3.alex.williamson@redhat.com> (raw)
In-Reply-To: <20220504213309.GM49344@nvidia.com>
On Wed, 4 May 2022 18:33:09 -0300
Jason Gunthorpe <jgg@nvidia.com> wrote:
> On Wed, May 04, 2022 at 02:19:19PM -0600, Alex Williamson wrote:
>
> > > This may go apparently via your tree as a PR from mlx5-next once you'll
> > > be fine with.
> >
> > As Jason noted, the net/mlx5 changes seem confined to the 2nd patch,
> > which has no other dependencies in this series. Is there something
> > else blocking committing that via the mlx tree and providing a branch
> > for the remainder to go in through the vfio tree? Thanks,
>
> Our process is to not add dead code to our non-rebasing branches until
> we have an ack on the consumer patches.
>
> So you can get a PR from Leon with everything sorted out including the
> VFIO bits, or you can get a PR from Leon with just the shared branch,
> after you say OK.
As long as Leon wants to wait for some acks in the former case, I'm fine
with either, but I don't expect to be able to shoot down the premise of
the series. You folks are the experts how your device works and there
are no API changes on the vfio side for me to critique here. Thanks,
Alex
next prev parent reply other threads:[~2022-05-04 22:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 9:31 [PATCH mlx5-next 0/5] Improve mlx5 live migration driver Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 1/5] vfio/mlx5: Reorganize the VF is migratable code Yishai Hadas
2022-05-04 20:13 ` Alex Williamson
2022-05-08 12:56 ` Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 2/5] net/mlx5: Expose mlx5_sriov_blocking_notifier_register / unregister APIs Yishai Hadas
2022-05-04 13:55 ` Jason Gunthorpe
2022-04-27 9:31 ` [PATCH mlx5-next 3/5] vfio/mlx5: Manage the VF attach/detach callback from the PF Yishai Hadas
2022-05-04 20:34 ` Alex Williamson
2022-05-08 13:04 ` Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 4/5] vfio/mlx5: Refactor to enable VFs migration in parallel Yishai Hadas
2022-04-27 9:31 ` [PATCH mlx5-next 5/5] vfio/mlx5: Run the SAVE state command in an async mode Yishai Hadas
2022-05-04 13:29 ` [PATCH mlx5-next 0/5] Improve mlx5 live migration driver Yishai Hadas
2022-05-04 20:19 ` Alex Williamson
2022-05-04 21:33 ` Jason Gunthorpe
2022-05-04 22:48 ` Alex Williamson [this message]
2022-05-05 5:38 ` Leon Romanovsky
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=20220504164817.348f5fd3.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=maorg@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=yishaih@nvidia.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;
as well as URLs for NNTP newsgroup(s).