All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] ui/cocoa.m: Add Mount image file menu item
Date: Wed, 9 Sep 2015 16:25:13 -0600	[thread overview]
Message-ID: <55F0B1C9.8070204@redhat.com> (raw)
In-Reply-To: <16D5C709-5630-4919-BE13-6B1DB4B860F8@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]

On 09/09/2015 03:37 PM, Programmingkid wrote:

>>>>>> On 2 September 2015 at 01:56, Programmingkid
>>>>>> <programmingkidx@gmail.com> wrote:

It's okay to trim your reply, to make it easier for others to quickly
skip to the relevant part of your emails.


> 
> Thank you very much for caring. I appreciate all the help I can receive. I so like my idea of
> sending a command to QEMU as if the user typed it himself. It is so easy to maintain. So 
> easy to use. So expandable. But given that two maintainers have told me that I can't do this,
> the idea has to be abandoned. 

Even emulating typing into the QMP interface is a non-starter.  Just
call the same functions that QMP would eventually call.

> 
> The C interface idea sounds good, but trying to figure out how to make any of the handler
> functions work is very difficult. Just trying to make the QDict and QObject variables is just
> too much. It needs to be a lot easier than this.
> 
> That leaves QMP. I am trying to figure it out. This is my attempt so far:
> 
> Error **errp;
> char *commandBuffer;
> commandBuffer = g_strdup_printf("{ \"execute\": \"quit\" }");
> qmp_query_command_line_options(false, commandBuffer, errp);
> printf("Program should quit now\n");
> 

If you type the QMP command:

{ "execute": "query-command-line-options", "arguments": { "option":
"quit" } }

then that will result in calling:

Error *err;
qmp_query_command_line_options(true, "quit", &err);

which will set err (because '-quit' is not a command line option).

But if you are worried about constructing a QDict (which is a subset of
QObject), you are probably trying to call the wrong interface.

In qmp-commands.hx, the command 'query-command-line-options' is tied to
qmp_marshal_query_command_line_options (well, after Markus' latest
patches are applied; in current qemu.git it is still named
qmp_marshal_input_query_command_line_options).  That is the generated
function that takes QDict, and then calls into the much nicer interface
of qmp_query_command_line_options() that has already broken out all the
arguments into straight-forward parameters.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-09-09 22:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  0:56 [Qemu-devel] [PATCH] ui/cocoa.m: Add Mount image file menu item Programmingkid
2015-09-02  9:05 ` Markus Armbruster
2015-09-08 16:17 ` Peter Maydell
2015-09-08 16:39   ` Programmingkid
2015-09-08 16:54     ` Peter Maydell
2015-09-08 18:46     ` Markus Armbruster
2015-09-09  3:02       ` Programmingkid
2015-09-09  7:29         ` Markus Armbruster
2015-09-09 21:37           ` Programmingkid
2015-09-09 22:25             ` Eric Blake [this message]
2015-09-09 22:31               ` Eric Blake
2015-09-09 23:35                 ` Programmingkid
2015-09-09 23:34               ` Programmingkid
2015-09-10  7:17                 ` Markus Armbruster
2015-09-10  3:28           ` Programmingkid
2015-09-10  7:21             ` Markus Armbruster
2015-09-10 16:22               ` Programmingkid
2015-09-10 17:15                 ` Markus Armbruster
2015-09-10 17:40                   ` Programmingkid
2015-09-11  7:09                     ` Markus Armbruster

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=55F0B1C9.8070204@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=programmingkidx@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.