From: mike <qiudayu@linux.vnet.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
benoit@irqsave.net, stefanha@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] hmp: Add '\n' in monitor_printf()
Date: Tue, 15 Oct 2013 18:07:16 +0800 [thread overview]
Message-ID: <525D13D4.3000704@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131015085851.GA3039@dhcp-200-207.str.redhat.com>
On 10/15/2013 04:58 PM, Kevin Wolf wrote:
> Am 15.10.2013 um 05:38 hat mike geschrieben:
>> On 10/14/2013 10:36 PM, Markus Armbruster wrote:
>>> Mike Qiu <qiudayu@linux.vnet.ibm.com> writes:
>>>
>>>> Without this, output of 'info block'
>>>>
>>>> scsi0-hd0: /images/f18-ppc64.qcow2 (qcow2)
>>>> [not inserted]
>>>> scsi0-cd2: [not inserted]
>>>> Removable device: not locked, tray closed
>>>>
>>>> floppy0: [not inserted]
>>>> Removable device: not locked, tray closed
>>>>
>>>> sd0: [not inserted]
>>>> Removable device: not locked, tray closed
>>>>
>>>> There will be no additional lines between scsi0-hd0 scsi0-cd2,
>>>> and break the info style.
>>> Just saw a similar one:
>>>
>>> (qemu) info block
>>> disk0: test.img (raw)
>>> [not inserted]
>>> cd: [not inserted]
>>> Removable device: not locked, tray closed
>>>
>>> foo: tmp.img (raw)
>>> Removable device: not locked, tray closed
>>> [not inserted](qemu)
>>>
>>>> This patch is to solve this.
>>>>
>>>> Signed-off-by: Mike Qiu <qiudayu@linux.vnet.ibm.com>
>>>> ---
>>>> hmp.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/hmp.c b/hmp.c
>>>> index 5891507..2d2e5f8 100644
>>>> --- a/hmp.c
>>>> +++ b/hmp.c
>>>> @@ -367,7 +367,7 @@ void hmp_info_block(Monitor *mon, const QDict *qdict)
>>>> info->value->inserted->iops_wr_max,
>>>> info->value->inserted->iops_size);
>>>> } else {
>>>> - monitor_printf(mon, " [not inserted]");
>>>> + monitor_printf(mon, " [not inserted]\n");
>>>> }
>>>> if (verbose) {
>>> monitor_printf(mon, "\nImages:\n");
>>>
>>> What about removing the newline before "Images"?
>> A good idea I think, it no need to add addition lines in one info.
>>
>> But see commit id: fbe2e26c15af35e4d157874dc80f6a19eebaa83b
>> [...]
>> It was changed to add this, so there maybe some reasons I think,
> Like everything else in that commit, I did that change because I found it
> more readable.
>
> The problem seems to be commit 3e9fab69 ('block: Add support for
> throttling burst max in QMP and the command line'), which added a bogus
> "[not inserted]" message. We simply need to drop it altogether instead of
> adding a newline.
>
Yes, I agree with you. but maybe need the author of the commit 3e9fab69
('block: Add support for throttling burst max in QMP and the command line')
to have some comments on this line, I think.
>>> I think we should also drop this newline:
>>>
>>> if (info->value->removable) {
>>> monitor_printf(mon, " Removable device: %slocked, tray %s\n",
>>> info->value->locked ? "" : "not ",
>>> info->value->tray_open ? "open" : "closed");
>>> }
> Why? Look:
>
> (qemu) info block
> scsi0-cd0: /tmp/cdrom.qcow2 (qcow2)
> Removable device: not locked, tray closed
> Backing file: /home/kwolf/images/iso/Fedora-18-x86_64-Live-Desktop.iso (chain depth: 1)
> I/O throttling: bps=1048576 bps_rd=0 bps_wr=0 bps_max=104857 bps_rd_max=0 bps_wr_max=0 iops=0 iops_rd=0 iops_wr=0 iops_max=0 iops_rd_max=0 iops_wr_max=0 iops_size=0
>
> Do you really want to remove the newline?
I'm not, but Markus suggest to do so.
Thanks
Mike
> Kevin
>
>
>
next prev parent reply other threads:[~2013-10-15 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 13:31 [Qemu-devel] [PATCH] hmp: Add '\n' in monitor_printf() Mike Qiu
2013-10-14 14:36 ` Markus Armbruster
2013-10-15 3:38 ` mike
2013-10-15 8:58 ` Kevin Wolf
2013-10-15 9:31 ` Markus Armbruster
2013-10-15 10:12 ` mike
2013-10-15 10:07 ` mike [this message]
2013-10-15 11:14 ` Benoît Canet
2013-10-16 7:29 ` Wenchao Xia
2013-10-16 7:47 ` Markus Armbruster
2013-10-16 7:56 ` Wenchao Xia
2013-10-16 9:03 ` mike
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=525D13D4.3000704@linux.vnet.ibm.com \
--to=qiudayu@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).