From: Lukas Straub <lukasstraub2@web.de>
To: Markus Armbruster <armbru@redhat.com>
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>,
qemu-devel <qemu-devel@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Max Reitz" <mreitz@redhat.com>
Subject: Re: [PATCH v10 1/8] Introduce yank feature
Date: Sun, 15 Nov 2020 09:28:55 +0100 [thread overview]
Message-ID: <20201115092855.7bd59f97@luklap> (raw)
In-Reply-To: <87y2jkp8tk.fsf@dusky.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
On Mon, 02 Nov 2020 07:32:55 +0100
Markus Armbruster <armbru@redhat.com> wrote:
> Lukas Straub <lukasstraub2@web.de> writes:
>
> > The yank feature allows to recover from hanging qemu by "yanking"
> > at various parts. Other qemu systems can register themselves and
> > multiple yank functions. Then all yank functions for selected
> > instances can be called by the 'yank' out-of-band qmp command.
> > Available instances can be queried by a 'query-yank' oob command.
> >
> > Signed-off-by: Lukas Straub <lukasstraub2@web.de>
> > Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
> [...]
> > qapi_storage_daemon_modules = [
> > diff --git a/qapi/qapi-schema.json b/qapi/qapi-schema.json
> > index 0b444b76d2..79c1705ed7 100644
> > --- a/qapi/qapi-schema.json
> > +++ b/qapi/qapi-schema.json
> > @@ -91,3 +91,4 @@
> > { 'include': 'audio.json' }
> > { 'include': 'acpi.json' }
> > { 'include': 'pci.json' }
> > +{ 'include': 'yank.json' }
>
> This adds the documentation at the very end of the reference manual. Is
> this where you want it to go? Check generated
> docs/interop/qemu-qmp-ref.html.
I've moved it above misc for the next version.
> > diff --git a/qapi/yank.json b/qapi/yank.json
> > new file mode 100644
> > index 0000000000..1964a2202e
> > --- /dev/null
> > +++ b/qapi/yank.json
> > @@ -0,0 +1,115 @@
> > +# -*- Mode: Python -*-
> > +# vim: filetype=python
> > +#
> > +
>
> Please add a suitable heading here. Headings look like this:
>
> ##
> # Text of heading goes here
> ##
Changed for the next version.
> Without it, the yank stuff gets squashed into the previous section
> (happens to be PCI).
>
> If you want to add an introduction or overview, it goes right below the
> heading. I'm not asking you to do that, I'm only telling you what's
> possible.
>
> [...]
>
> Solid work, pleasant to review, thanks!
>
> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>
Thanks!
--
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-11-15 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1604075469.git.lukasstraub2@web.de>
2020-10-30 16:41 ` [PATCH v10 1/8] Introduce yank feature Lukas Straub
2020-11-02 6:32 ` Markus Armbruster
2020-11-15 8:28 ` Lukas Straub [this message]
2020-10-30 16:41 ` [PATCH v10 2/8] block/nbd.c: Add " Lukas Straub
2020-10-30 16:41 ` [PATCH v10 3/8] chardev/char-socket.c: " Lukas Straub
2020-10-30 16:41 ` [PATCH v10 4/8] migration: " Lukas Straub
2020-10-30 16:41 ` [PATCH v10 5/8] io/channel-tls.c: make qio_channel_tls_shutdown thread-safe Lukas Straub
2020-10-30 16:41 ` [PATCH v10 6/8] io: Document qmp oob suitability of qio_channel_shutdown and io_shutdown Lukas Straub
2020-10-30 16:41 ` [PATCH v10 7/8] MAINTAINERS: Add myself as maintainer for yank feature Lukas Straub
2020-11-02 6:33 ` Markus Armbruster
2020-11-15 8:29 ` Lukas Straub
2020-10-30 16:41 ` [PATCH v10 8/8] tests/test-char.c: Wait for the chardev to connect in char_socket_client_dupid_test Lukas Straub
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=20201115092855.7bd59f97@luklap \
--to=lukasstraub2@web.de \
--cc=armbru@redhat.com \
--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).