From: Robert Hu <robert.hu@vmm.sh.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Robert Ho <robert.hu@intel.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Reveal 'to' parameter of 'vnc' option to user
Date: Sun, 05 Jun 2016 21:08:31 +0800 [thread overview]
Message-ID: <1465132111.14690.15.camel@vmm.sh.intel.com> (raw)
In-Reply-To: <8cbea5f1-bd87-4321-77e1-620a6c0234ac@redhat.com>
On Tue, 2016-05-31 at 14:59 +0200, Paolo Bonzini wrote:
>
> On 31/05/2016 09:03, Robert Ho wrote:
> > I find that '-vnc' option actually has a parameter 'to', implicitly;
> > while actually is there and can be used but not be public.
> > Don't know why but this may probably confuse user, especially when used in
> > some default situation implicitly.
> >
> > So shall I?
> > 1. Add its description in QEMU manual info
> > 2. Expilicitly print out when it's used with non-default value
>
> I think patch 1 is okay.
Thanks Paolo. Sorry for late reply, since I just part-time work on this.
>
> For patch 2, I am not sure I see the point of printing the VNC options;
> the VNC port is printed immediately after.
I agree it is not significantly meaningful to print out the options. I
just disliked the implicitly be-on-behalf-chose a value without
notification; especially we don't know there is a 'to' option. So when I
did the density test of huge quantity of guests, always failed on 99th,
made me quizzical. :(
In most ordinary cases, the final 'VNC server running on ...' printf is
sufficient.
Now my that emotion gradually die out, I agree abandon patch 2. :)
>
> However, I think it is useful to print the VNC port whenever the user
> specifies "-vnc to=XX". Perhaps you could move show_vnc_port (the
> variable, the assignments and the "if (show_vnc_port)") from vl.c to
> vnc_display_open?
And 2nd reason I abandon patch 2: I grepped in vnc.c, no bare 'printf'.
Any nice wrapper for such info purpose? I don't want to be first 'bad
guy' to break the elegant code. ;)
So do I need to send out v2 patch? which simply contains single patch 1.
>
> Thanks,
>
> Paolo
next prev parent reply other threads:[~2016-06-05 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 7:03 [Qemu-devel] [PATCH 0/2] Reveal 'to' parameter of 'vnc' option to user Robert Ho
2016-05-31 7:03 ` [Qemu-devel] [PATCH 1/2] Reveal 'to' param of '-vnc' option in qemu man page Robert Ho
2016-05-31 7:03 ` [Qemu-devel] [PATCH 2/2] Explicitly print out default vnc option in use Robert Ho
2016-05-31 12:59 ` [Qemu-devel] [PATCH 0/2] Reveal 'to' parameter of 'vnc' option to user Paolo Bonzini
2016-06-05 13:08 ` Robert Hu [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-31 6:42 Robert Ho
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=1465132111.14690.15.camel@vmm.sh.intel.com \
--to=robert.hu@vmm.sh.intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.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).