From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Cc: "Laurent Vivier" <laurent@vivier.eu>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-ppc@nongnu.org, "Artyom Tarasenko" <atar4qemu@gmail.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: Any plan for command line '-g' option (graphical resolution and depth)?
Date: Thu, 20 Feb 2025 10:50:15 +0100 [thread overview]
Message-ID: <e514d6db-781d-4afe-b057-9046c70044dc@redhat.com> (raw)
In-Reply-To: <97e66ba5-488f-4246-b4d9-466d29a86dff@linaro.org>
On 2/20/25 10:20, Philippe Mathieu-Daudé wrote:
> Hi,
>
> QEMU provides the global '-g' CLI option:
>
> $ qemu-system-foo --help
>
> -g WxH[xDEPTH] Set the initial graphical resolution and depth
>
> This option is used to pass resolution/depth information to guest
> firmwares in the machines defined in the following files:
>
> hw/ppc/mac_newworld.c
> hw/ppc/mac_oldworld.c
> hw/ppc/prep.c
> hw/ppc/spapr.c
> hw/sparc/sun4m.c
> hw/sparc64/sun4u.c
>
> Examples:
>
> - hw/ppc/spapr.c:1102:
>
> _FDT(fdt_setprop_cell(fdt, c, "qemu,graphic-width", graphic_width));
>
> - hw/sparc64/sun4u.c:716:
>
> fw_cfg_add_i16(fw_cfg, FW_CFG_SPARC64_WIDTH, graphic_width);
>
>
> Obviously we have default values, which are different per architecture!
> Clearly these ought to be machine properties.
Yes, we should have an easy way for machine to allow, in addition to -M
graphics=BOOLEAN, the structured property -M
graphics.{width,height,depth,enabled}. Then '-g' can desugar to -M
graphics.width=WW,graphics.height=HH,graphics.depth=BB.
> It is also used to set TYPE_NUBUS_MACFB properties in hw/m68k/q800.c.
> Here i suppose we could directly use '-global nubus-macfb.width=value'
> etc. although I'm not sure it is the recommended way.
>> Should we start deprecating '-g' as a whole?
Only if it's unused/useless. If the option is useful it could also be
used for EDID, for example (adding Gerd).
Global variables are hard to track, and the one-off nature of the option
makes it hard to figure out (without looking at the code) which machine
support it.
However, if the properties were available and introspectable via QOM,
then it wouldn't matter if the -g sugar remains as an isolated "case
QEMU_OPTION_g:" in system/vl.c. For an example see -boot/-smp or
-no-reboot/-no-shutdown.
Paolo
next prev parent reply other threads:[~2025-02-20 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 9:20 Any plan for command line '-g' option (graphical resolution and depth)? Philippe Mathieu-Daudé
2025-02-20 9:50 ` Paolo Bonzini [this message]
2025-02-20 10:22 ` Philippe Mathieu-Daudé
2025-02-20 11:28 ` Gerd Hoffmann
2025-02-20 11:13 ` Mark Cave-Ayland
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=e514d6db-781d-4afe-b057-9046c70044dc@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=berrange@redhat.com \
--cc=danielhb413@gmail.com \
--cc=kraxel@redhat.com \
--cc=laurent@vivier.eu \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).