From: Markus Armbruster <armbru@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Andrew Keesler <ankeesler@google.com>,
berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v5 1/1] hw/display: Allow injection of virtio-gpu EDID name
Date: Wed, 09 Jul 2025 12:39:30 +0200 [thread overview]
Message-ID: <87jz4hps0t.fsf@pond.sub.org> (raw)
In-Reply-To: <CAJ+F1C+qHhefC+Mg7jxK=TfYhVSMF2PZqwBcXLoGN29t34jFCg@mail.gmail.com> ("Marc-André Lureau"'s message of "Wed, 9 Jul 2025 10:28:10 +0400")
Marc-André Lureau <marcandre.lureau@gmail.com> writes:
> Hi
>
> On Tue, Jul 8, 2025 at 9:07 PM Andrew Keesler <ankeesler@google.com> wrote:
>>
>> Thanks to 72d277a7, 1ed2cb32, and others, EDID (Extended Display
>> Identification Data) is propagated by QEMU such that a virtual display
>> presents legitimate metadata (e.g., name, serial number, preferred
>> resolutions, etc.) to its connected guest.
>>
>> This change adds the ability to specify the EDID name for a particular
>> virtio-vga display. Previously, every virtual display would have the same
>> name: "QEMU Monitor". Now, we can inject names of displays in order to test
>> guest behavior that is specific to display names. We provide the ability to
>> inject the display name from the frontend since this is guest visible
>> data. Furthermore, this makes it clear where N potential display outputs
>> would get their name from (which will be added in a future change).
>>
>> Note that we have elected to use a struct here for output data for
>> extensibility - we intend to add per-output fields like resolution in a
>> future change.
>>
>> It should be noted that EDID names longer than 12 bytes will be truncated
>> per spec (I think?).
>>
>> Testing: verified that when I specified 2 outputs for a virtio-gpu with
>> edid_name set, the names matched those that I configured with my vnc
>> display.
>>
>> -display vnc=localhost:0,id=aaa,display=vga,head=0 \
>> -display vnc=localhost:1,id=bbb,display=vga,head=1 \
>> -device '{"driver":"virtio-vga",
>> "max_outputs":2,
>> "id":"vga",
>> "outputs":[
>> {
>> "name":"AAA",
>> },
>> {
>> "name":"BBB",
>> }
>> ]}'
>>
>
> (there are still invalid trailing ',' in this example)
Yes:
$ qemu-system-x86_64: -device {"driver":"virtio-vga", "max_outputs":2, "id":"vga", "outputs":[ { "name":"AAA", }, { "name":"BBB", }]}: JSON parse error, expecting value
Should be fixed for the merge.
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
>
>> Signed-off-by: Andrew Keesler <ankeesler@google.com>
prev parent reply other threads:[~2025-07-09 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 17:07 [PATCH v5 0/1] Allow injection of virtio-gpu EDID name Andrew Keesler
2025-07-08 17:07 ` [PATCH v5 1/1] hw/display: " Andrew Keesler
2025-07-09 6:28 ` Marc-André Lureau
2025-07-09 10:39 ` Markus Armbruster [this message]
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=87jz4hps0t.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=ankeesler@google.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@gmail.com \
--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.