From: Lukas Straub <lukasstraub2@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block <qemu-block@nongnu.org>,
"Juan Quintela" <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH v7 0/8] Introduce 'yank' oob qmp command to recover from hanging qemu
Date: Tue, 18 Aug 2020 14:26:31 +0200 [thread overview]
Message-ID: <20200818142631.3e1c1481@luklap> (raw)
In-Reply-To: <cover.1596528468.git.lukasstraub2@web.de>
[-- Attachment #1: Type: text/plain, Size: 3142 bytes --]
On Tue, 4 Aug 2020 10:11:22 +0200
Lukas Straub <lukasstraub2@web.de> wrote:
> Hello Everyone,
> In many cases, if qemu has a network connection (qmp, migration, chardev, etc.)
> to some other server and that server dies or hangs, qemu hangs too.
> These patches introduce the new 'yank' out-of-band qmp command to recover from
> these kinds of hangs. The different subsystems register callbacks which get
> executed with the yank command. For example the callback can shutdown() a
> socket. This is intended for the colo use-case, but it can be used for other
> things too of course.
>
> Regards,
> Lukas Straub
>
> v7:
> -yank_register_instance now returns error via Error **errp instead of aborting
> -dropped "chardev/char.c: Check for duplicate id before creating chardev"
>
> v6:
> -add Reviewed-by and Acked-by tags
> -rebase on master
> -lots of changes in nbd due to rebase
> -only take maintainership of util/yank.c and include/qemu/yank.h (Daniel P. Berrangé)
> -fix a crash discovered by the newly added chardev test
> -fix the test itself
>
> v5:
> -move yank.c to util/
> -move yank.h to include/qemu/
> -add license to yank.h
> -use const char*
> -nbd: use atomic_store_release and atomic_load_aqcuire
> -io-channel: ensure thread-safety and document it
> -add myself as maintainer for yank
>
> v4:
> -fix build errors...
>
> v3:
> -don't touch softmmu/vl.c, use __contructor__ attribute instead (Paolo Bonzini)
> -fix build errors
> -rewrite migration patch so it actually passes all tests
>
> v2:
> -don't touch io/ code anymore
> -always register yank functions
> -'yank' now takes a list of instances to yank
> -'query-yank' returns a list of yankable instances
>
> Lukas Straub (8):
> Introduce yank feature
> block/nbd.c: Add yank feature
> chardev/char-socket.c: Add yank feature
> migration: Add yank feature
> io/channel-tls.c: make qio_channel_tls_shutdown thread-safe
> io: Document thread-safety of qio_channel_shutdown
> MAINTAINERS: Add myself as maintainer for yank feature
> tests/test-char.c: Wait for the chardev to connect in
> char_socket_client_dupid_test
>
> MAINTAINERS | 6 ++
> block/nbd.c | 129 +++++++++++++++---------
> chardev/char-socket.c | 31 ++++++
> include/io/channel.h | 2 +
> include/qemu/yank.h | 80 +++++++++++++++
> io/channel-tls.c | 6 +-
> migration/channel.c | 12 +++
> migration/migration.c | 25 ++++-
> migration/multifd.c | 10 ++
> migration/qemu-file-channel.c | 6 ++
> migration/savevm.c | 6 ++
> qapi/misc.json | 45 +++++++++
> tests/Makefile.include | 2 +-
> tests/test-char.c | 1 +
> util/Makefile.objs | 1 +
> util/yank.c | 184 ++++++++++++++++++++++++++++++++++
> 16 files changed, 493 insertions(+), 53 deletions(-)
> create mode 100644 include/qemu/yank.h
> create mode 100644 util/yank.c
>
> --
> 2.20.1
Ping...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-18 12:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 8:11 [PATCH v7 0/8] Introduce 'yank' oob qmp command to recover from hanging qemu Lukas Straub
2020-08-04 8:11 ` [PATCH v7 1/8] Introduce yank feature Lukas Straub
2020-08-27 10:31 ` Daniel P. Berrangé
2020-08-27 12:37 ` Markus Armbruster
2020-08-27 14:28 ` Daniel P. Berrangé
2020-08-28 14:21 ` Lukas Straub
2020-08-31 7:47 ` Markus Armbruster
2020-09-04 12:33 ` Lukas Straub
2020-09-04 12:47 ` Eric Blake
2020-08-04 8:11 ` [PATCH v7 2/8] block/nbd.c: Add " Lukas Straub
2020-08-27 10:31 ` Daniel P. Berrangé
2020-08-04 8:11 ` [PATCH v7 3/8] chardev/char-socket.c: " Lukas Straub
2020-08-27 10:32 ` Daniel P. Berrangé
2020-08-04 8:11 ` [PATCH v7 4/8] migration: " Lukas Straub
2020-08-27 10:39 ` Daniel P. Berrangé
2020-08-04 8:11 ` [PATCH v7 5/8] io/channel-tls.c: make qio_channel_tls_shutdown thread-safe Lukas Straub
2020-08-04 8:11 ` [PATCH v7 6/8] io: Document thread-safety of qio_channel_shutdown Lukas Straub
2020-08-04 8:11 ` [PATCH v7 7/8] MAINTAINERS: Add myself as maintainer for yank feature Lukas Straub
2020-08-04 8:12 ` [PATCH v7 8/8] tests/test-char.c: Wait for the chardev to connect in char_socket_client_dupid_test Lukas Straub
2020-08-27 10:30 ` Daniel P. Berrangé
2020-08-18 12:26 ` Lukas Straub [this message]
2020-08-27 8:42 ` [PATCH v7 0/8] Introduce 'yank' oob qmp command to recover from hanging qemu Lukas Straub
2020-08-27 10:41 ` Daniel P. Berrangé
2020-08-27 14:18 ` Markus Armbruster
2020-08-27 17:58 ` 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=20200818142631.3e1c1481@luklap \
--to=lukasstraub2@web.de \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).