From: Shaoqin Huang <shahuang@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-arm@nongnu.org, "Eric Auger" <eauger@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2] ramfb: Add property to control if load the romfile
Date: Mon, 9 Jun 2025 11:37:49 +0800 [thread overview]
Message-ID: <3f093907-34d3-40f7-956b-828c0c58f04a@redhat.com> (raw)
In-Reply-To: <aEKeNSc8mAZ8vhGj@redhat.com>
Hi Daniel,
On 6/6/25 3:52 PM, Daniel P. Berrangé wrote:
> On Fri, Jun 06, 2025 at 03:02:34AM -0400, Shaoqin Huang wrote:
>> Now the ramfb will load the vgabios-ramfb.bin unconditionally, but only
>> the x86 need the vgabios-ramfb.bin, this can cause that when use the
>> release package on arm64 it can't find the vgabios-ramfb.bin.
>>
>> Because only seabios will use the vgabios-ramfb.bin, load the rom logic
>> is x86-specific. For other !x86 platforms, the edk2 ships an EFI driver
>> for ramfb, so they don't need to load the romfile.
>>
>> So add a new property use_legacy_x86_rom in both ramfb and vfio_pci
>> device, because the vfio display also use the ramfb_setup() to load
>> the vgabios-ramfb.bin file.
>>
>> After have this property, the machine type can set the compatibility to
>> not load the vgabios-ramfb.bin if the arch doesn't need it.
>
> Can you make this a series, with an additional patch that updates the
> current in-dev machine types to use this new property, so we're clear
> about the proposed usage.
>
Ok. Thanks for notification. I will update it in the version 3.
>>
>> Signed-off-by: Shaoqin Huang <shahuang@redhat.com>
>> ---
>> hw/display/ramfb-standalone.c | 4 +++-
>> hw/display/ramfb-stubs.c | 2 +-
>> hw/display/ramfb.c | 6 ++++--
>> hw/vfio/display.c | 4 ++--
>> hw/vfio/pci.c | 1 +
>> hw/vfio/pci.h | 1 +
>> include/hw/display/ramfb.h | 2 +-
>> 7 files changed, 13 insertions(+), 7 deletions(-)
>>
>> diff --git a/hw/display/ramfb-standalone.c b/hw/display/ramfb-standalone.c
>> index 1be106b57f..af1175bf96 100644
>> --- a/hw/display/ramfb-standalone.c
>> +++ b/hw/display/ramfb-standalone.c
>> @@ -17,6 +17,7 @@ struct RAMFBStandaloneState {
>> QemuConsole *con;
>> RAMFBState *state;
>> bool migrate;
>> + bool use_legacy_x86_rom;
>> };
>>
>> static void display_update_wrapper(void *dev)
>> @@ -39,7 +40,7 @@ static void ramfb_realizefn(DeviceState *dev, Error **errp)
>> RAMFBStandaloneState *ramfb = RAMFB(dev);
>>
>> ramfb->con = graphic_console_init(dev, 0, &wrapper_ops, dev);
>> - ramfb->state = ramfb_setup(errp);
>> + ramfb->state = ramfb_setup(ramfb->use_legacy_x86_rom, errp);
>> }
>>
>> static bool migrate_needed(void *opaque)
>> @@ -62,6 +63,7 @@ static const VMStateDescription ramfb_dev_vmstate = {
>>
>> static const Property ramfb_properties[] = {
>> DEFINE_PROP_BOOL("x-migrate", RAMFBStandaloneState, migrate, true),
>> + DEFINE_PROP_BOOL("use-legacy-x86-rom", RAMFBStandaloneState, use_legacy_x86_rom, true),
>> };
>>
>> static void ramfb_class_initfn(ObjectClass *klass, void *data)
>> diff --git a/hw/display/ramfb-stubs.c b/hw/display/ramfb-stubs.c
>> index cf64733b10..b83551357b 100644
>> --- a/hw/display/ramfb-stubs.c
>> +++ b/hw/display/ramfb-stubs.c
>> @@ -8,7 +8,7 @@ void ramfb_display_update(QemuConsole *con, RAMFBState *s)
>> {
>> }
>>
>> -RAMFBState *ramfb_setup(Error **errp)
>> +RAMFBState *ramfb_setup(bool romfile, Error **errp)
>> {
>> error_setg(errp, "ramfb support not available");
>> return NULL;
>> diff --git a/hw/display/ramfb.c b/hw/display/ramfb.c
>> index 8c0f907673..9a17d97d07 100644
>> --- a/hw/display/ramfb.c
>> +++ b/hw/display/ramfb.c
>> @@ -135,7 +135,7 @@ const VMStateDescription ramfb_vmstate = {
>> }
>> };
>>
>> -RAMFBState *ramfb_setup(Error **errp)
>> +RAMFBState *ramfb_setup(bool romfile, Error **errp)
>> {
>> FWCfgState *fw_cfg = fw_cfg_find();
>> RAMFBState *s;
>> @@ -147,7 +147,9 @@ RAMFBState *ramfb_setup(Error **errp)
>>
>> s = g_new0(RAMFBState, 1);
>>
>> - rom_add_vga("vgabios-ramfb.bin");
>> + if (romfile) {
>> + rom_add_vga("vgabios-ramfb.bin");
>> + }
>> fw_cfg_add_file_callback(fw_cfg, "etc/ramfb",
>> NULL, ramfb_fw_cfg_write, s,
>> &s->cfg, sizeof(s->cfg), false);
>> diff --git a/hw/vfio/display.c b/hw/vfio/display.c
>> index ea87830fe0..8bfd8eb1e3 100644
>> --- a/hw/vfio/display.c
>> +++ b/hw/vfio/display.c
>> @@ -365,7 +365,7 @@ static bool vfio_display_dmabuf_init(VFIOPCIDevice *vdev, Error **errp)
>> &vfio_display_dmabuf_ops,
>> vdev);
>> if (vdev->enable_ramfb) {
>> - vdev->dpy->ramfb = ramfb_setup(errp);
>> + vdev->dpy->ramfb = ramfb_setup(vdev->use_legacy_x86_rom, errp);
>> if (!vdev->dpy->ramfb) {
>> return false;
>> }
>> @@ -494,7 +494,7 @@ static bool vfio_display_region_init(VFIOPCIDevice *vdev, Error **errp)
>> &vfio_display_region_ops,
>> vdev);
>> if (vdev->enable_ramfb) {
>> - vdev->dpy->ramfb = ramfb_setup(errp);
>> + vdev->dpy->ramfb = ramfb_setup(vdev->use_legacy_x86_rom, errp);
>> if (!vdev->dpy->ramfb) {
>> return false;
>> }
>> diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
>> index 7f1532fbed..4e4759c954 100644
>> --- a/hw/vfio/pci.c
>> +++ b/hw/vfio/pci.c
>> @@ -3564,6 +3564,7 @@ static const TypeInfo vfio_pci_dev_info = {
>>
>> static const Property vfio_pci_dev_nohotplug_properties[] = {
>> DEFINE_PROP_BOOL("ramfb", VFIOPCIDevice, enable_ramfb, false),
>> + DEFINE_PROP_BOOL("use_legacy_x86_rom", VFIOPCIDevice, use_legacy_x86_rom, true),
>> DEFINE_PROP_ON_OFF_AUTO("x-ramfb-migrate", VFIOPCIDevice, ramfb_migrate,
>> ON_OFF_AUTO_AUTO),
>> };
>> diff --git a/hw/vfio/pci.h b/hw/vfio/pci.h
>> index d94ecaba68..713956157e 100644
>> --- a/hw/vfio/pci.h
>> +++ b/hw/vfio/pci.h
>> @@ -177,6 +177,7 @@ struct VFIOPCIDevice {
>> bool no_kvm_ioeventfd;
>> bool no_vfio_ioeventfd;
>> bool enable_ramfb;
>> + bool use_legacy_x86_rom;
>> OnOffAuto ramfb_migrate;
>> bool defer_kvm_irq_routing;
>> bool clear_parent_atomics_on_exit;
>> diff --git a/include/hw/display/ramfb.h b/include/hw/display/ramfb.h
>> index a7e0019144..172aa6dc89 100644
>> --- a/include/hw/display/ramfb.h
>> +++ b/include/hw/display/ramfb.h
>> @@ -6,7 +6,7 @@
>> /* ramfb.c */
>> typedef struct RAMFBState RAMFBState;
>> void ramfb_display_update(QemuConsole *con, RAMFBState *s);
>> -RAMFBState *ramfb_setup(Error **errp);
>> +RAMFBState *ramfb_setup(bool romfile, Error **errp);
>>
>> extern const VMStateDescription ramfb_vmstate;
>>
>> --
>> 2.40.1
>>
>
> With regards,
> Daniel
--
Shaoqin
prev parent reply other threads:[~2025-06-09 3:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 7:02 [PATCH v2] ramfb: Add property to control if load the romfile Shaoqin Huang
2025-06-06 7:52 ` Daniel P. Berrangé
2025-06-06 8:06 ` Cédric Le Goater
2025-06-06 8:07 ` Cédric Le Goater
2025-06-09 5:16 ` Shaoqin Huang
2025-06-10 16:00 ` Alex Williamson
2025-06-06 9:04 ` Philippe Mathieu-Daudé
2025-06-06 9:15 ` Daniel P. Berrangé
2025-06-06 16:22 ` Pierrick Bouvier
2025-06-09 3:37 ` Shaoqin Huang [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=3f093907-34d3-40f7-956b-828c0c58f04a@redhat.com \
--to=shahuang@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=eauger@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 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).