From: Eric Blake <eblake@redhat.com>
To: Ning Bo <ning.bo9@zte.com.cn>, qemu-devel@nongnu.org, armbru@redhat.com
Cc: mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] vhost-vsock: report QMP event when set running
Date: Thu, 1 Aug 2019 06:17:59 -0500 [thread overview]
Message-ID: <37a4faaf-c589-2da5-a8b8-faa85c69e774@redhat.com> (raw)
In-Reply-To: <1564644533-28850-1-git-send-email-ning.bo9@zte.com.cn>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
On 8/1/19 2:28 AM, Ning Bo wrote:
> Report vsock running event so that the upper application can
> control boot sequence.
> see https://github.com/kata-containers/runtime/pull/1918
>
> Signed-off-by: Ning Bo <ning.bo9@zte.com.cn>
> ---
Since this is an update to an earlier version you posted, it is helpful
to include 'v2' in the subject line ('git format-patch -v2' or 'git
send-email -v2' can do that on your behalf), as well as to document here
after the --- separator how it differs from v1.
More patch submission hints at https://wiki.qemu.org/Contribute/SubmitAPatch
> +++ b/qapi/char.json
> @@ -570,3 +570,25 @@
> { 'event': 'VSERPORT_CHANGE',
> 'data': { 'id': 'str',
> 'open': 'bool' } }
> +
> +##
> +# @VSOCK_RUNNING:
> +#
> +# Emitted when the guest changes the vsock status.
> +#
> +# @cid: guest context ID
> +#
> +# @running: true if the vsock is running
> +#
> +# Since: v4.2
Still not consistent with other uses. s/v4.2/4.2/
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-08-01 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 7:28 [Qemu-devel] [PATCH] vhost-vsock: report QMP event when set running Ning Bo
2019-08-01 11:17 ` Eric Blake [this message]
2019-08-01 15:25 ` Markus Armbruster
2019-08-01 19:15 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2019-07-30 12:24 N. B.
2019-07-30 13:19 ` Eric Blake
2019-07-30 20:29 ` Michael S. Tsirkin
2019-08-15 13:20 ` Stefan Hajnoczi
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=37a4faaf-c589-2da5-a8b8-faa85c69e774@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=mst@redhat.com \
--cc=ning.bo9@zte.com.cn \
--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).