From: Yan Zhao <yan.y.zhao@intel.com>
To: Peter Xu <zhexu@redhat.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"crosthwaite.peter@gmail.com" <crosthwaite.peter@gmail.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"dgilbert@redhat.com" <dgilbert@redhat.com>,
"quintela@redhat.com" <quintela@redhat.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] migration: notify runstate immediately before vcpu stops
Date: Tue, 16 Jul 2019 22:00:46 -0400 [thread overview]
Message-ID: <20190717020046.GC8912@joy-OptiPlex-7040> (raw)
In-Reply-To: <20190716103341.GC30980@xz-x1>
On Tue, Jul 16, 2019 at 06:33:41PM +0800, Peter Xu wrote:
> On Tue, Jul 16, 2019 at 03:57:49AM -0400, Yan Zhao wrote:
> > On Tue, Jul 16, 2019 at 03:50:25PM +0800, Peter Xu wrote:
> > > On Tue, Jul 16, 2019 at 03:29:19AM -0400, Yan Zhao wrote:
> > > > On Tue, Jul 16, 2019 at 03:23:16PM +0800, Peter Xu wrote:
> > > > > On Tue, Jul 16, 2019 at 03:10:42PM +0800, Yan Zhao wrote:
> > > > > > for some devices to do live migration, it is needed to do something
> > > > > > immediately before vcpu stops. add a notification here.
> > > > >
> > > > > Hi, Yan,
> > > > >
> > > > > Could I ask for a more detailed commit message here? E.g., what is
> > > > > "some devices"? And, what's the problem behind?
> > > > >
> > > > hi Peter,
> > > >
> > > > Some devices refer to assigned devices, like NICs.
> > > > For assigned devices to do live migration, it is sometimes required that
> > > > source device is stopped before stopping source vcpus. vcpus can do some
> > > > final cleanups (like handling interrupt) in that case.
> > >
> > > I see, so this is a prerequisite of another work?
> >
> > Yes.
> > >
> > > IMHO it would make more sense to have this patch to be with that
> > > patchset, then it'll justify itself with reasoning. Unless I
> > > misunderstood - this single patch seems to help nothing if as a
> > > standalone one.
> >
> > It would be better. but this patch alone is also somewhat general,
> > as it only adds an extra notification and wouldn't impact others.
> >
> > Only after this patch is upstreamed, can VFIO live migration have a
> > second choice for those devices of special requirements.
> >
> > Hope it can get understanding from you:)
>
> No you don't need my understanding, as long as the maintainer likes it
> it's good enough, so you probably only need to persuade the
> maintainers. :)
>
> But again for me I would prefer patch like this to simply be the first
> patch of your live migration series. There can be some exceptions
> like that when the prerequisite is too big so we'd better split them
> out to do things step by step, but this patch (which is a oneliner)
> should not be the case.
>
> Thanks,
>
ok. Thank you, Peter :)
> >
> > Or do you think I need to change the commit message a little to unbind
> > from migration?
> >
> > Thanks
> > Yan
> >
>
> --
> Peter Xu
next prev parent reply other threads:[~2019-07-17 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 7:10 [Qemu-devel] [PATCH] migration: notify runstate immediately before vcpu stops Yan Zhao
2019-07-16 7:23 ` Peter Xu
2019-07-16 7:29 ` Yan Zhao
2019-07-16 7:50 ` Peter Xu
2019-07-16 7:57 ` Yan Zhao
2019-07-16 10:33 ` Peter Xu
2019-07-17 2:00 ` Yan Zhao [this message]
2019-07-17 5:36 ` no-reply
2019-07-25 10:39 ` Dr. David Alan Gilbert
2019-07-26 0:12 ` Yan Zhao
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=20190717020046.GC8912@joy-OptiPlex-7040 \
--to=yan.y.zhao@intel.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=crosthwaite.peter@gmail.com \
--cc=dgilbert@redhat.com \
--cc=kevin.tian@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rth@twiddle.net \
--cc=zhexu@redhat.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).