From: BALATON Zoltan <balaton@eik.bme.hu>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Akihiko Odaki" <akihiko.odaki@daynix.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] vl: Print display options for -display help
Date: Thu, 14 Dec 2023 14:00:03 +0100 (CET) [thread overview]
Message-ID: <8f8d3317-c28b-3985-89d7-0fbd1ce4b56e@eik.bme.hu> (raw)
In-Reply-To: <9443821d-5eff-46e6-be69-707cca9cd0d0@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 3135 bytes --]
On Thu, 14 Dec 2023, Philippe Mathieu-Daudé wrote:
> Hi Akihiko,
>
> On 14/12/23 07:47, Akihiko Odaki wrote:
>> -display lists display backends, but does not tell their options.
>> Use the help messages from qemu-options.def, which include the list of
>> options.
>>
>> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
>> ---
>> include/ui/console.h | 1 -
>> system/vl.c | 11 ++++++-----
>> ui/console.c | 20 --------------------
>> 3 files changed, 6 insertions(+), 26 deletions(-)
>
>
>> diff --git a/ui/console.c b/ui/console.c
>> index 7db921e3b7d6..6aee5e9a7ffb 100644
>> --- a/ui/console.c
>> +++ b/ui/console.c
>> @@ -1691,23 +1691,3 @@ const char *qemu_display_get_vc(DisplayOptions
>> *opts)
>> }
>> return vc;
>> }
>> -
>> -void qemu_display_help(void)
>> -{
>> - int idx;
>> -
>> - printf("Available display backend types:\n");
>> - printf("none\n");
>> - for (idx = DISPLAY_TYPE_NONE; idx < DISPLAY_TYPE__MAX; idx++) {
>> - if (!dpys[idx]) {
>> - Error *local_err = NULL;
>> - int rv = ui_module_load(DisplayType_str(idx), &local_err);
>> - if (rv < 0) {
>> - error_report_err(local_err);
>> - }
>> - }
>> - if (dpys[idx]) {
>> - printf("%s\n", DisplayType_str(dpys[idx]->type));
>
> Is the "qapi/qapi-commands-ui.h" header still necessary?
>
>> - }
>> - }
>> -}
>
> So we go from:
>
> $ ./qemu-system-aarch64 -display help
> Available display backend types:
> none
> gtk
> sdl
> curses
> cocoa
> dbus
>
> to:
>
> $ ./qemu-system-aarch64 -display help
> -display sdl[,gl=on|core|es|off][,grab-mod=<mod>][,show-cursor=on|off]
> [,window-close=on|off]
> -display gtk[,full-screen=on|off][,gl=on|off][,grab-on-hover=on|off]
> [,show-tabs=on|off][,show-cursor=on|off][,window-close=on|off]
> [,show-menubar=on|off]
> -display vnc=<display>[,<optargs>]
> -display curses[,charset=<encoding>]
> -display cocoa[,full-grab=on|off][,swap-opt-cmd=on|off]
> -display dbus[,addr=<dbusaddr>]
> [,gl=on|core|es|off][,rendernode=<file>]
> -display cocoa[,show-cursor=on|off][,left-command-key=on|off]
> -display none
> select display backend type
> The default display is equivalent to
> "-display gtk"
>
> The latter is indeed more helpful.
It is more helpful but maybe a bit overwhelming. Would it be possible to
only print the options with -display cocoa,help similar to how -device
help lists devices and -device sm501,help lists options for one device?
Adding info about default to -display help is really helpful though (that
could also be marked with (default) like in -machine help.
I'm not complaining, thanks for taking care of this so quickly but if it's
not too difficult to add separate -display cocoa,help and not list options
in -display help maybe that would be better and more consistent with other
help options.
Regards,
BALATON Zoltan
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Tested-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>
>
next prev parent reply other threads:[~2023-12-14 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 6:47 [PATCH] vl: Print display options for -display help Akihiko Odaki
2023-12-14 9:29 ` Philippe Mathieu-Daudé
2023-12-14 13:00 ` BALATON Zoltan [this message]
2023-12-15 11:36 ` Akihiko Odaki
2023-12-15 12:43 ` BALATON Zoltan
2023-12-15 12:54 ` Daniel P. Berrangé
2023-12-15 13:07 ` BALATON Zoltan
2023-12-17 6:38 ` Akihiko Odaki
2023-12-14 19:10 ` Marc-André Lureau
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=8f8d3317-c28b-3985-89d7-0fbd1ce4b56e@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=akihiko.odaki@daynix.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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.