qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	kraxel@redhat.com, qemu-devel@nongnu.org,
	Gautam Agrawal <gutamnagrawal@gmail.com>
Subject: Re: [PATCH v3] Warn user if the vga flag is passed but no vga device is created
Date: Fri, 6 May 2022 18:10:07 +0200	[thread overview]
Message-ID: <b754d9a3-1762-71d2-417a-3c61ae87f3de@redhat.com> (raw)
In-Reply-To: <CAFEAcA8i5t0i61HT0NEV5BHYEkK_ipSAeNGuc+3Zg3uqTGkzYQ@mail.gmail.com>

On 5/6/22 17:47, Peter Maydell wrote:
>>        if (!vga_model && !default_vga) {
>>            vga_interface_type = VGA_DEVICE;
>> +          vga_interface_created = true;
>>        }
>>        if (!has_defaults || machine_class->no_serial) {
>>            default_serial = 0;
>
> Can you explain why that's right? qemu_disable_default_devices()
> isn't creating any devices at all, so it's not clear to me
> (a) why it's setting vga_interface_type or (b) why setting
> vga_interface_created to true is OK.

VGA_DEVICE means the device has been specified on the command line, but 
the board should otherwise behave as if "-vga something" was there.

While the device has not been created yet, it will be in 
qemu_create_cli_devices(), and that's what !default_vga means at this 
point of the function.

This in fact means that almost all three occurrences of 
"vga_interface_type != VGA_NONE" are wrong. :(

Paolo


  reply	other threads:[~2022-05-06 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 12:25 [PATCH v3] Warn user if the vga flag is passed but no vga device is created Gautam Agrawal
2022-05-05  8:54 ` Peter Maydell
2022-05-06 14:24 ` Stefan Hajnoczi
2022-05-06 14:31   ` Thomas Huth
2022-05-06 14:48     ` Peter Maydell
2022-05-06 15:43       ` Paolo Bonzini
2022-05-06 15:47         ` Peter Maydell
2022-05-06 16:10           ` Paolo Bonzini [this message]
2022-05-06 16:29             ` Peter Maydell
2022-05-09 10:04               ` Gerd Hoffmann
2022-05-09  6:09         ` Thomas Huth

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=b754d9a3-1762-71d2-417a-3c61ae87f3de@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=gutamnagrawal@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@gmail.com \
    --cc=thuth@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).