qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: pbonzini@redhat.com, Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
	armbru@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V8 00/13] monitor: support sub command group in auto completion and help
Date: Tue, 20 Aug 2013 10:04:42 -0400	[thread overview]
Message-ID: <20130820100442.1abc070d@redhat.com> (raw)
In-Reply-To: <20130730120311.7f1e44a7@redhat.com>

On Tue, 30 Jul 2013 12:03:11 -0400
Luiz Capitulino <lcapitulino@redhat.com> wrote:

> On Fri, 26 Jul 2013 11:20:29 +0800
> Wenchao Xia <xiawenc@linux.vnet.ibm.com> wrote:
> 
> > This series make auto completion and help functions works normal for sub
> > command, by using reentrant functions. In order to do that, global variables
> > are not directly used in those functions any more. With this series, cmd_table
> > is a member of structure Monitor so it is possible to create a monitor with
> > different command table now, auto completion will work in that monitor. In
> > short, "info" is not treated as a special case now, this series ensure help
> > and auto complete function works normal for any sub command added in the future.
> > 
> > Patch 5 replaced cur_mon with rs->mon, it is safe because:
> > monitor_init() calls readline_init() which initialize mon->rs, result is
> > mon->rs->mon == mon. Then qemu_chr_add_handlers() is called, which make
> > monitor_read() function take *mon as its opaque. Later, when user input,
> > monitor_read() is called, where cur_mon is set to *mon by "cur_mon = opaque".
> > If qemu's monitors run in one thread, then later in readline_handle_byte()
> > and readline_comletion(), cur_mon is actually equal to rs->mon, in another
> > word, it points to the monitor instance, so it is safe to replace *cur_mon
> > in those functions.
> 
> I've applied this to qmp-next with the change I suggested for
> patch 09/13.

Unfortunately this series brakes make check:

GTESTER check-qtest-x86_64
Broken pipe
GTester: last random seed: R02S3492bd34f44dd17460851643383be44d
main-loop: WARNING: I/O thread spun for 1000 iterations
make: *** [check-qtest-x86_64] Error 1

I debugged it (with some help from Laszlo) and the problem is that it
broke the human-monitor-command command. Any usage of this command
triggers the bug like:

{ "execute": "human-monitor-command",
             "arguments": { "command-line": "info registers" } }

It seems simple to fix, I think you just have to initialize
mon->cmd_table in qmp_human_monitor_command(), but I'd recommend two
things:

 1. It's better to split off some/all QMP initialization from
    monitor_init() and call it from qmp_human_monitor_command()

 2. Can you please take the opportunity and test all commands using
    cur_mon? Just grep for it

Sorry for noticing this only now, but I only run make check before
sending a pull request (although this very likely shows you didn't
run it either).

  parent reply	other threads:[~2013-08-20 14:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  3:20 [Qemu-devel] [PATCH V8 00/13] monitor: support sub command group in auto completion and help Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 01/13] monitor: avoid use of global *cur_mon in cmd_completion() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 02/13] monitor: avoid use of global *cur_mon in file_completion() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 03/13] monitor: avoid use of global *cur_mon in block_completion_it() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 04/13] monitor: avoid use of global *cur_mon in monitor_find_completion() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 05/13] monitor: avoid use of global *cur_mon in readline_completion() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 06/13] monitor: avoid direct use of global variable *mon_cmds Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 07/13] monitor: code move for parse_cmdline() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 08/13] monitor: refine parse_cmdline() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 09/13] monitor: support sub command in help Wenchao Xia
2013-07-30 14:51   ` Luiz Capitulino
2013-07-31  2:23     ` Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 10/13] monitor: refine monitor_find_completion() Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 11/13] monitor: support sub command in auto completion Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 12/13] monitor: allow "help" show message for single command in sub group Wenchao Xia
2013-07-26  3:20 ` [Qemu-devel] [PATCH V8 13/13] monitor: improve auto complete of "help" " Wenchao Xia
2013-07-30 16:03 ` [Qemu-devel] [PATCH V8 00/13] monitor: support sub command group in auto completion and help Luiz Capitulino
2013-07-31  2:17   ` Wenchao Xia
2013-08-20 14:04   ` Luiz Capitulino [this message]
2013-08-21  9:17     ` Wenchao Xia
2013-08-22  9:16     ` Wenchao Xia
2013-08-22 13:12       ` Luiz Capitulino
2013-08-28  2:24         ` Wenchao Xia

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=20130820100442.1abc070d@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xiawenc@linux.vnet.ibm.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).