All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: kvm@vger.kernel.org
Cc: Nicholas Piggin <npiggin@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Huth <thuth@redhat.com>, Nico Boehr <nrb@linux.ibm.com>
Subject: [kvm-unit-tests PATCH 0/3] migration: fixes and multiple migration
Date: Tue, 25 Jul 2023 13:39:34 +1000	[thread overview]
Message-ID: <20230725033937.277156-1-npiggin@gmail.com> (raw)

Spent too long looking at bash code after posting previous RFC, but
got it into shape.

The first 2 seem to be real bugs you can trigger by making a test
case fail. Third IMO is pretty solid now but no users yet so I can
keep it around and resubmit with a user some time later.

Thanks,
Nick

Nicholas Piggin (3):
  migration: Fix test harness hang on fifo
  migration: Fix test harness hang if source does not reach migration
    point
  arch-run: Support multiple migrations

 lib/migrate.c         |  8 +++---
 lib/migrate.h         |  1 +
 scripts/arch-run.bash | 65 ++++++++++++++++++++++++++++++++++++-------
 3 files changed, 60 insertions(+), 14 deletions(-)

-- 
2.40.1


             reply	other threads:[~2023-07-25  3:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  3:39 Nicholas Piggin [this message]
2023-07-25  3:39 ` [kvm-unit-tests PATCH 1/3] migration: Fix test harness hang on fifo Nicholas Piggin
2023-07-28  7:20   ` Nico Boehr
2023-07-25  3:39 ` [kvm-unit-tests PATCH 2/3] migration: Fix test harness hang if source does not reach migration point Nicholas Piggin
2023-07-28  7:34   ` Nico Boehr
2023-07-30 10:03     ` Nicholas Piggin
2023-09-25 11:14       ` Nico Boehr
2023-10-16 18:32         ` Thomas Huth
2023-10-19  7:55           ` Nico Boehr
2023-10-19  8:10             ` Thomas Huth
2023-07-25  3:39 ` [kvm-unit-tests PATCH 3/3] arch-run: Support multiple migrations Nicholas Piggin
2023-07-28  8:44 ` [kvm-unit-tests PATCH 0/3] migration: fixes and multiple migration Shaoqin Huang
2023-07-30 10:06   ` Nicholas Piggin

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=20230725033937.277156-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.