From: Nico Boehr <nrb@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com,
pbonzini@redhat.com, andrew.jones@linux.dev, lvivier@redhat.com
Subject: [kvm-unit-tests PATCH v2 0/4] lib: add function to request migration
Date: Fri, 9 Dec 2022 14:48:05 +0100 [thread overview]
Message-ID: <20221209134809.34532-1-nrb@linux.ibm.com> (raw)
v1->v2:
---
* arm: commit message gib->gic (thanks Andrew)
* arm: remove unneeded {} (thanks Andrew)
* s390x: make patch less intrusive (thanks Claudio)
With this series, I pick up a suggestion Claudio has brought up in my
CMM-migration series[1].
Migration tests can ask migrate_cmd to migrate them to a new QEMU
process. Requesting migration and waiting for completion is hence a
common pattern which is repeated all over the code base. Add a function
which does all of that to avoid repetition.
Since migrate_cmd currently can only migrate exactly once, this function
is called migrate_once() and is a no-op when it has been called before.
This can simplify the control flow, especially when tests are skipped.
[1] https://lore.kernel.org/kvm/20221125154646.5974cb52@p-imbrenda/
Nico Boehr (4):
lib: add function to request migration
powerpc: use migrate_once() in migration tests
s390x: use migrate_once() in migration tests
arm: use migrate_once() in migration tests
arm/Makefile.common | 1 +
powerpc/Makefile.common | 1 +
s390x/Makefile | 1 +
lib/migrate.h | 9 ++++++++
lib/migrate.c | 34 ++++++++++++++++++++++++++++
arm/debug.c | 17 +++++---------
arm/gic.c | 49 ++++++++++++-----------------------------
powerpc/sprs.c | 4 ++--
s390x/migration-cmm.c | 25 +++++++--------------
s390x/migration-sck.c | 4 ++--
s390x/migration-skey.c | 15 +++++--------
s390x/migration.c | 7 ++----
12 files changed, 84 insertions(+), 83 deletions(-)
create mode 100644 lib/migrate.h
create mode 100644 lib/migrate.c
--
2.36.1
next reply other threads:[~2022-12-09 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 13:48 Nico Boehr [this message]
2022-12-09 13:48 ` [kvm-unit-tests PATCH v2 1/4] lib: add function to request migration Nico Boehr
2022-12-09 15:41 ` Claudio Imbrenda
2022-12-09 13:48 ` [kvm-unit-tests PATCH v2 2/4] powerpc: use migrate_once() in migration tests Nico Boehr
2022-12-09 13:48 ` [kvm-unit-tests PATCH v2 3/4] s390x: " Nico Boehr
2022-12-09 15:43 ` Claudio Imbrenda
2022-12-09 13:48 ` [kvm-unit-tests PATCH v2 4/4] arm: " Nico Boehr
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=20221209134809.34532-1-nrb@linux.ibm.com \
--to=nrb@linux.ibm.com \
--cc=andrew.jones@linux.dev \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=lvivier@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox