From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org
Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Miroslav Rezanina <mrezanin@redhat.com>,
Bernhard Beschow <shentey@gmail.com>
Subject: Re: [PATCH 0/3] Make it possible to compile the x86 binaries without FDC
Date: Fri, 26 Apr 2024 07:08:35 +0200 [thread overview]
Message-ID: <184b50ac-d435-4531-9f3c-f4d54ee059fa@redhat.com> (raw)
In-Reply-To: <49984234-9a41-40aa-b1ea-448b8a02ab0e@linaro.org>
On 25/04/2024 22.56, Philippe Mathieu-Daudé wrote:
> Hi Thomas,
>
> On 25/4/24 20:43, Thomas Huth wrote:
>> For downstream versions of QEMU, we'd like to be able to compile QEMU
>> without the FDC code included (since it's not required for modern VMs
>> anymore and the FDC code has rather a bad reputation, see the VENOM CVE).
>
> IIRC you still need to keep the i440fx+piix machine DS due to
> migration compatibility, right?
>
> Are you able to migrate a VM booted with FDC to a non-FDC one?
Migration from a machine with FDC to one without is likely not possible. But
that's also not the purpose of this series. It's about having the
possibility to build a QEMU binary without FDC at all in case you don't have
to support old machine types with FDC anymore.
>> The q35 machine can already be instantiated without FDC, but for being
>> able to link a binary without the FDC code, the Kconfig file needs some
>> tweaks and there are two spots in the pc code that directly call functions
>> from the FDC code - those need to be disabled via #ifdefs.
>
> Is it useful to you to have q35 without FDC but i440fx+piix with?
> Or are you removing it from i440fx+piix due to shared code with q35?
I think it might get useful.
Thomas
next prev parent reply other threads:[~2024-04-26 5:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 18:43 [PATCH 0/3] Make it possible to compile the x86 binaries without FDC Thomas Huth
2024-04-25 18:43 ` [PATCH 1/3] hw/i386/pc: Allow to compile without CONFIG_FDC_ISA Thomas Huth
2024-05-06 14:26 ` Philippe Mathieu-Daudé
2024-04-25 18:43 ` [PATCH 2/3] hw/i386/Kconfig: Allow to compile Q35 without FDC_ISA Thomas Huth
2024-04-25 18:43 ` [RFC PATCH 3/3] hw/i386: Add the possibility to use i440fx and isapc without FDC Thomas Huth
2024-04-25 20:56 ` [PATCH 0/3] Make it possible to compile the x86 binaries " Philippe Mathieu-Daudé
2024-04-26 5:08 ` Thomas Huth [this message]
2024-04-29 10:31 ` Kevin Wolf
2024-05-06 14:27 ` Philippe Mathieu-Daudé
2024-05-06 15:59 ` Paolo Bonzini
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=184b50ac-d435-4531-9f3c-f4d54ee059fa@redhat.com \
--to=thuth@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mrezanin@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.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).