qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: akong@redhat.com, qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 for-2.2] input: move input-send-event into experimental namespace
Date: Tue, 25 Nov 2014 09:15:34 -0500	[thread overview]
Message-ID: <20141125091534.312b3198@redhat.com> (raw)
In-Reply-To: <1416923657-10614-1-git-send-email-armbru@redhat.com>

On Tue, 25 Nov 2014 14:54:17 +0100
Markus Armbruster <armbru@redhat.com> wrote:

> From: Gerd Hoffmann <kraxel@redhat.com>
> 
> Ongoing discussions on how we are going to specify the console,
> so tag the command as experiental so we can refine things in
> the 2.3 development cycle.
> 
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> [Spell out "not a stable API", and x- the QAPI schema, too]
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> 
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> I would've ripped out the command entirely, but Gerd's approach works
> for me, too.  Since time for -rc3 is running out, I'm respinning his
> patch with my and Amos's review comments worked in.  Hope that's okay.
> 
> We should also pick Amos's "[PATCH] qmp: fix typo in input-send-event
> examples".

Is this going to be merged via Gerd's tree or QMP tree? In any case it
would be good to have Eric's review.

> 
>  qapi-schema.json |  6 ++++--
>  qmp-commands.hx  | 16 +++++++++-------
>  ui/input.c       |  4 ++--
>  3 files changed, 15 insertions(+), 11 deletions(-)
> 
> diff --git a/qapi-schema.json b/qapi-schema.json
> index d0926d9..9ffdcf8 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -3245,7 +3245,7 @@
>                'abs'     : 'InputMoveEvent' } }
>  
>  ##
> -# @input-send-event
> +# @x-input-send-event
>  #
>  # Send input event(s) to guest.
>  #
> @@ -3257,8 +3257,10 @@
>  #
>  # Since: 2.2
>  #
> +# Note: this command is experimental, and not a stable API.
> +#
>  ##
> -{ 'command': 'input-send-event',
> +{ 'command': 'x-input-send-event',
>    'data': { '*console':'int', 'events': [ 'InputEvent' ] } }
>  
>  ##
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index 8812401..718dd92 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -3791,13 +3791,13 @@ Example:
>  EQMP
>  
>      {
> -        .name       = "input-send-event",
> +        .name       = "x-input-send-event",
>          .args_type  = "console:i?,events:q",
> -        .mhandler.cmd_new = qmp_marshal_input_input_send_event,
> +        .mhandler.cmd_new = qmp_marshal_input_x_input_send_event,
>      },
>  
>  SQMP
> -@input-send-event
> +@x-input-send-event
>  -----------------
>  
>  Send input event to guest.
> @@ -3811,17 +3811,19 @@ The consoles are visible in the qom tree, under
>  /backend/console[$index]. They have a device link and head property, so
>  it is possible to map which console belongs to which device and display.
>  
> +Note: this command is experimental, and not a stable API.
> +
>  Example (1):
>  
>  Press left mouse button.
>  
> --> { "execute": "input-send-event",
> +-> { "execute": "x-input-send-event",
>      "arguments": { "console": 0,
>                     "events": [ { "type": "btn",
>                      "data" : { "down": true, "button": "Left" } } } }
>  <- { "return": {} }
>  
> --> { "execute": "input-send-event",
> +-> { "execute": "x-input-send-event",
>      "arguments": { "console": 0,
>                     "events": [ { "type": "btn",
>                      "data" : { "down": false, "button": "Left" } } } }
> @@ -3831,7 +3833,7 @@ Example (2):
>  
>  Press ctrl-alt-del.
>  
> --> { "execute": "input-send-event",
> +-> { "execute": "x-input-send-event",
>       "arguments": { "console": 0, "events": [
>          { "type": "key", "data" : { "down": true,
>            "key": {"type": "qcode", "data": "ctrl" } } },
> @@ -3845,7 +3847,7 @@ Example (3):
>  
>  Move mouse pointer to absolute coordinates (20000, 400).
>  
> --> { "execute": "input-send-event" ,
> +-> { "execute": "x-input-send-event" ,
>    "arguments": { "console": 0, "events": [
>                 { "type": "abs", "data" : { "axis": "X", "value" : 20000 } },
>                 { "type": "abs", "data" : { "axis": "Y", "value" : 400 } } ] } }
> diff --git a/ui/input.c b/ui/input.c
> index 37ff46f..7ba99e5 100644
> --- a/ui/input.c
> +++ b/ui/input.c
> @@ -122,8 +122,8 @@ qemu_input_find_handler(uint32_t mask, QemuConsole *con)
>      return NULL;
>  }
>  
> -void qmp_input_send_event(bool has_console, int64_t console,
> -                          InputEventList *events, Error **errp)
> +void qmp_x_input_send_event(bool has_console, int64_t console,
> +                            InputEventList *events, Error **errp)
>  {
>      InputEventList *e;
>      QemuConsole *con;

  reply	other threads:[~2014-11-25 14:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 13:54 [Qemu-devel] [PATCH v2 for-2.2] input: move input-send-event into experimental namespace Markus Armbruster
2014-11-25 14:15 ` Luiz Capitulino [this message]
2014-11-25 14:24   ` Peter Maydell
2014-11-25 15:28 ` Amos Kong
2014-11-25 16:58 ` Eric Blake
2014-11-25 18:22   ` Peter Maydell

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=20141125091534.312b3198@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=akong@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --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).