[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v5 17/26] qmp: add new event "request-dropped"
From: |
Peter Xu |
Subject: |
Re: [Qemu-devel] [RFC v5 17/26] qmp: add new event "request-dropped" |
Date: |
Sat, 16 Dec 2017 14:59:44 +0800 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
On Thu, Dec 14, 2017 at 11:16:02AM +0000, Stefan Hajnoczi wrote:
> On Tue, Dec 05, 2017 at 01:51:51PM +0800, Peter Xu wrote:
> > +##
> > +# @RequestDropReason:
> > +#
> > +# Reasons that caused one command to be dropped.
> > +#
> > +# @queue-full: the queue of request is full.
> > +#
> > +# Since: 2.12
> > +##
> > +{ 'enum': 'RequestDropReason',
>
> qapi-schema.json calls them "commands", not "requests". Please rename
> it CommandDropReason for consistency and update the documentation.
>
> > + 'data': [ 'queue-full' ] }
> > +
> > +##
> > +# @REQUEST_DROPPED:
> > +#
> > +# Emitted when one QMP request is dropped due to some reason.
> > +# REQUEST_DROPPED is only emitted when the oob capability is enabled.
>
> Please make it clear that requests can only be dropped when the oob
> capability is enabled.
>
> Emitted when a command is dropped due to some reason. Commands can
> only be dropped when the oob capability is enabled.
Will address all comments, including the other reply.
Meanwhile I'll rename REQUEST_DROPPED to COMMAND_DROPPED so no
"request" but all "command" then. Thanks,
--
Peter Xu
- Re: [Qemu-devel] [RFC v5 15/26] monitor: let suspend_cnt be thread safe, (continued)
[Qemu-devel] [RFC v5 16/26] monitor: separate QMP parser and dispatcher, Peter Xu, 2017/12/05
[Qemu-devel] [RFC v5 17/26] qmp: add new event "request-dropped", Peter Xu, 2017/12/05
[Qemu-devel] [RFC v5 18/26] monitor: send event when request queue full, Peter Xu, 2017/12/05
[Qemu-devel] [RFC v5 19/26] qapi: introduce new cmd option "allow-oob", Peter Xu, 2017/12/05