From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Mark Cave-Ayland <mark.caveayland@nutanix.com>,
qemu-devel@nongnu.org, Helge Deller <deller@gmx.de>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Clément Mathieu--Drif" <clement.mathieu--drif@eviden.com>,
"Yi Liu" <yi.l.liu@intel.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Amit Shah" <amit@kernel.org>, "Zhao Liu" <zhao1.liu@intel.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Sergio Lopez" <slp@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v2 03/16] hw/i386/x86: Remove X86MachineClass::fwcfg_dma_enabled field
Date: Fri, 2 May 2025 12:45:14 +0200 [thread overview]
Message-ID: <54d72848-9108-4b04-a46c-1f82492e06cb@linaro.org> (raw)
In-Reply-To: <2acc8c0c-f563-4d27-b73d-ce4c0f8ef424@nutanix.com>
On 2/5/25 11:08, Mark Cave-Ayland wrote:
> On 01/05/2025 19:36, Philippe Mathieu-Daudé wrote:
>
>> The X86MachineClass::fwcfg_dma_enabled boolean was only used
>> by the pc-q35-2.6 and pc-i440fx-2.6 machines, which got
>> removed. Remove it and simplify.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> include/hw/i386/x86.h | 2 --
>> hw/i386/microvm.c | 3 ---
>> hw/i386/multiboot.c | 7 +------
>> hw/i386/x86-common.c | 3 +--
>> hw/i386/x86.c | 2 --
>> 5 files changed, 2 insertions(+), 15 deletions(-)
>>
>> diff --git a/include/hw/i386/x86.h b/include/hw/i386/x86.h
>> index fc460b82f82..29d37af11e6 100644
>> --- a/include/hw/i386/x86.h
>> +++ b/include/hw/i386/x86.h
>> @@ -29,8 +29,6 @@
>> struct X86MachineClass {
>> MachineClass parent;
>> - /* use DMA capable linuxboot option rom */
>> - bool fwcfg_dma_enabled;
>> /* CPU and apic information: */
>> bool apic_xrupt_override;
>> };
>> diff --git a/hw/i386/multiboot.c b/hw/i386/multiboot.c
>> index 6e6b96bc345..bfa7e8f1e83 100644
>> --- a/hw/i386/multiboot.c
>> +++ b/hw/i386/multiboot.c
>> @@ -153,7 +153,6 @@ int load_multiboot(X86MachineState *x86ms,
>> int kernel_file_size,
>> uint8_t *header)
>> {
>> - bool multiboot_dma_enabled = X86_MACHINE_GET_CLASS(x86ms)-
>> >fwcfg_dma_enabled;
>> int i, is_multiboot = 0;
>> uint32_t flags = 0;
>> uint32_t mh_entry_addr;
>> @@ -402,11 +401,7 @@ int load_multiboot(X86MachineState *x86ms,
>> fw_cfg_add_bytes(fw_cfg, FW_CFG_INITRD_DATA, mb_bootinfo_data,
>> sizeof(bootinfo));
>> - if (multiboot_dma_enabled) {
>> - option_rom[nb_option_roms].name = "multiboot_dma.bin";
>> - } else {
>> - option_rom[nb_option_roms].name = "multiboot.bin";
>> - }
>> + option_rom[nb_option_roms].name = "multiboot_dma.bin";
>
> Question: now that all machines support DMA-capable fw_cfg, does that
> mean that the non-DMA options roms above can also be removed?
All x86 machines, but there are still 2 not supporting it: HPPA and
MIPS Loongson-3:
hw/hppa/machine.c:204: fw_cfg = fw_cfg_init_mem(addr, addr + 4);
hw/mips/loongson3_virt.c:289: fw_cfg = fw_cfg_init_mem_wide(cfg_addr,
cfg_addr + 8, 8, 0, NULL);
next prev parent reply other threads:[~2025-05-02 10:45 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 18:36 [PATCH v2 00/16] hw/i386/pc: Remove deprecated 2.6 and 2.7 PC machines Philippe Mathieu-Daudé
2025-05-01 18:36 ` [PATCH v2 01/16] hw/i386/pc: Remove deprecated pc-q35-2.6 and pc-i440fx-2.6 machines Philippe Mathieu-Daudé
2025-05-02 8:53 ` Mark Cave-Ayland
2025-05-05 8:43 ` Thomas Huth
2025-05-01 18:36 ` [PATCH v2 02/16] hw/i386/pc: Remove PCMachineClass::legacy_cpu_hotplug field Philippe Mathieu-Daudé
2025-05-02 8:57 ` Mark Cave-Ayland
2025-05-02 11:02 ` Philippe Mathieu-Daudé
2025-05-05 8:50 ` Thomas Huth
2025-05-01 18:36 ` [PATCH v2 03/16] hw/i386/x86: Remove X86MachineClass::fwcfg_dma_enabled field Philippe Mathieu-Daudé
2025-05-02 9:08 ` Mark Cave-Ayland
2025-05-02 10:45 ` Philippe Mathieu-Daudé [this message]
2025-05-05 9:06 ` Thomas Huth
2025-05-08 12:56 ` Philippe Mathieu-Daudé
2025-05-01 18:36 ` [PATCH v2 04/16] hw/i386/pc: Remove pc_compat_2_6[] array Philippe Mathieu-Daudé
2025-05-02 9:09 ` Mark Cave-Ayland
2025-05-05 9:07 ` Thomas Huth
2025-05-05 9:19 ` Thomas Huth
2025-05-05 10:01 ` Philippe Mathieu-Daudé
2025-05-01 18:36 ` [PATCH v2 05/16] hw/intc/apic: Remove APICCommonState::legacy_instance_id field Philippe Mathieu-Daudé
2025-05-02 9:14 ` Mark Cave-Ayland
2025-05-02 11:15 ` Philippe Mathieu-Daudé
2025-05-05 9:09 ` Thomas Huth
2025-05-01 18:36 ` [PATCH v2 06/16] hw/core/machine: Remove hw_compat_2_6[] array Philippe Mathieu-Daudé
2025-05-02 9:16 ` Mark Cave-Ayland
2025-05-05 9:13 ` Thomas Huth
2025-05-05 9:58 ` Philippe Mathieu-Daudé
2025-05-08 7:29 ` Philippe Mathieu-Daudé
2025-05-01 18:36 ` [PATCH v2 07/16] hw/virtio/virtio-mmio: Remove VirtIOMMIOProxy::format_transport_address field Philippe Mathieu-Daudé
2025-05-02 9:17 ` Mark Cave-Ayland
2025-05-01 18:36 ` [PATCH v2 08/16] hw/i386/pc: Remove deprecated pc-q35-2.7 and pc-i440fx-2.7 machines Philippe Mathieu-Daudé
2025-05-02 9:18 ` Mark Cave-Ayland
2025-05-05 9:14 ` Thomas Huth
2025-05-05 10:35 ` Thomas Huth
2025-05-05 10:38 ` Philippe Mathieu-Daudé
2025-05-01 18:36 ` [PATCH v2 09/16] hw/i386/pc: Remove pc_compat_2_7[] array Philippe Mathieu-Daudé
2025-05-02 9:20 ` Mark Cave-Ayland
2025-05-05 9:21 ` Thomas Huth
2025-05-01 18:36 ` [PATCH v2 10/16] hw/audio/pcspk: Remove PCSpkState::migrate field Philippe Mathieu-Daudé
2025-05-02 9:21 ` Mark Cave-Ayland
2025-05-05 9:22 ` Thomas Huth
2025-05-01 18:36 ` [PATCH v2 11/16] hw/core/machine: Remove hw_compat_2_7[] array Philippe Mathieu-Daudé
2025-05-02 9:22 ` Mark Cave-Ayland
2025-05-01 18:36 ` [PATCH v2 12/16] hw/i386/intel_iommu: Remove IntelIOMMUState::buggy_eim field Philippe Mathieu-Daudé
2025-05-02 9:24 ` Mark Cave-Ayland
2025-05-01 18:36 ` [PATCH v2 13/16] hw/intc/ioapic: Remove IOAPICCommonState::version field Philippe Mathieu-Daudé
2025-05-02 9:31 ` Mark Cave-Ayland
2025-05-02 11:12 ` Philippe Mathieu-Daudé
2025-05-01 18:36 ` [PATCH v2 14/16] hw/virtio/virtio-pci: Remove VirtIOPCIProxy::ignore_backend_features field Philippe Mathieu-Daudé
2025-05-02 9:33 ` Mark Cave-Ayland
2025-05-01 18:36 ` [PATCH v2 15/16] hw/char/virtio-serial: Do not expose the 'emergency-write' property Philippe Mathieu-Daudé
2025-05-02 9:41 ` Mark Cave-Ayland
2025-05-02 11:08 ` Philippe Mathieu-Daudé
2025-05-01 18:36 ` [PATCH v2 16/16] hw/virtio/virtio-pci: Remove VIRTIO_PCI_FLAG_PAGE_PER_VQ definition Philippe Mathieu-Daudé
2025-05-02 9:44 ` 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=54d72848-9108-4b04-a46c-1f82492e06cb@linaro.org \
--to=philmd@linaro.org \
--cc=amit@kernel.org \
--cc=anisinha@redhat.com \
--cc=chenhuacai@kernel.org \
--cc=clement.mathieu--drif@eviden.com \
--cc=deller@gmx.de \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=jasowang@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kraxel@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mark.caveayland@nutanix.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=slp@redhat.com \
--cc=thuth@redhat.com \
--cc=wangyanan55@huawei.com \
--cc=yi.l.liu@intel.com \
--cc=zhao1.liu@intel.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).