All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Amos Jianjun Kong <kongjianjun@gmail.com>,
	Ting Wang <kathy.wangting@huawei.com>
Cc: wu.wubin@huawei.com, famz@redhat.com,
	qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5] hmp: add info iothreads command
Date: Thu, 30 Jul 2015 19:07:35 +0200	[thread overview]
Message-ID: <55BA59D7.2060909@redhat.com> (raw)
In-Reply-To: <CAFeW=pYNRrzPZ34wcqCVFX2+H4tGiDA=oKsiPr4Wsj46LwVXmg@mail.gmail.com>



On 30/07/2015 18:51, Amos Jianjun Kong wrote:
>> > +void hmp_info_iothreads(Monitor *mon, const QDict *qdict)
>> > +{
>> > +    IOThreadInfoList *info_list = qmp_query_iothreads(NULL);
>> > +    IOThreadInfoList *info;
>> > +
>> > +    for (info = info_list; info; info = info->next) {
>> > +        monitor_printf(mon, "%s: thread_id=%" PRId64 "\n",
> How about add a '\' at the beginning of each line? similar as the
> output of 'info network'
> 

For 'info network', the \ represents the peer relationship between e.g.
NIC and backend.  There is no such relationship for iothreads.

Paolo

  reply	other threads:[~2015-07-30 17:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  8:07 [Qemu-devel] [PATCH v5] hmp: add info iothreads command Ting Wang
2015-07-03 12:43 ` Markus Armbruster
2015-07-06  2:24   ` Ting Wang
2015-07-30 16:05 ` Luiz Capitulino
2015-07-31  1:09   ` Ting Wang
2015-07-30 16:51 ` Amos Jianjun Kong
2015-07-30 17:07   ` Paolo Bonzini [this message]
2015-07-30 17:09     ` Amos Jianjun Kong
2015-08-05  9:54 ` 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=55BA59D7.2060909@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=famz@redhat.com \
    --cc=kathy.wangting@huawei.com \
    --cc=kongjianjun@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wu.wubin@huawei.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 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.