qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, dgilbert@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Migration events fix and generate trace
Date: Wed,  8 Jul 2015 14:08:28 +0200	[thread overview]
Message-ID: <1436357310-3879-1-git-send-email-quintela@redhat.com> (raw)

Hi

This should fix the problems on s390, and restores unconditionally the trace point.

Please review/test.

Thanks, Juan.

Juan Quintela (2):
  migration: Only change state after migration has finished
  migration: Trace event and migration event are different things

 migration/migration.c | 50 ++++++++++++++++++++++++++++----------------------
 1 file changed, 28 insertions(+), 22 deletions(-)

-- 
2.4.3

             reply	other threads:[~2015-07-08 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 12:08 Juan Quintela [this message]
2015-07-08 12:08 ` [Qemu-devel] [PATCH 1/2] migration: Only change state after migration has finished Juan Quintela
2015-07-08 12:18   ` Christian Borntraeger
2015-07-08 12:08 ` [Qemu-devel] [PATCH 2/2] migration: Trace event and migration event are different things Juan Quintela
2015-07-08 12:20   ` Dr. David Alan Gilbert

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=1436357310-3879-1-git-send-email-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).