From: Paolo Bonzini <pbonzini@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: aliguori@us.ibm.com, stefanha@linux.vnet.ibm.com, mst@redhat.com,
rusty@rustcorp.com.au, qemu-devel@nongnu.org,
Orit Wasserman <owasserm@redhat.com>,
quintela@redhat.com
Subject: Re: [Qemu-devel] [V6 PATCH 1/4] net: announce self after vm start
Date: Wed, 02 May 2012 10:32:33 +0200 [thread overview]
Message-ID: <4FA0F121.5030903@redhat.com> (raw)
In-Reply-To: <4FA0E976.9050808@redhat.com>
Il 02/05/2012 09:59, Jason Wang ha scritto:
> I don't like this external flag. As this is only related to migration
> I think we can add a new state RUN_STATE_MIG_PRELAUNCH. In vm_start
> call qemu_announce_self only if the state was
> RUN_STATE_MIG_PRELAUNCH. This will we useful if we will need to do
> something else when resuming a migrated guest.
I don't think this global is replacing a runstate. It is simply saying
that some work has been delayed to the next time the CPU runs.
Perhaps we can instead use a runstate-change notifier and keep the
global hidden to vl.c.
Paolo
next prev parent reply other threads:[~2012-05-02 8:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 5:40 [Qemu-devel] [V6 PATCH 0/4] Send gratuitous packets by guest Jason Wang
2012-03-28 5:40 ` [Qemu-devel] [V6 PATCH 1/4] net: announce self after vm start Jason Wang
2012-03-28 7:22 ` Paolo Bonzini
2012-05-02 7:49 ` Orit Wasserman
2012-05-02 7:59 ` Jason Wang
2012-05-02 8:32 ` Paolo Bonzini [this message]
2012-03-28 5:40 ` [Qemu-devel] [V6 PATCH 2/4] net: model specific announcing support Jason Wang
2012-03-28 7:23 ` Paolo Bonzini
2012-03-28 5:40 ` [Qemu-devel] [V6 PATCH 3/4] virtio-net: notify guest to annouce itself Jason Wang
2012-03-28 5:40 ` [Qemu-devel] [V6 PATCH 4/4] virtio-net: compat guest announce support Jason Wang
2012-05-02 3:51 ` [Qemu-devel] [V6 PATCH 0/4] Send gratuitous packets by guest Jason Wang
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=4FA0F121.5030903@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=stefanha@linux.vnet.ibm.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).