Re: [RFC PATCH 0/3] single-binary: make QAPI generated files common

On 4/25/25 08:38, Markus Armbruster wrote: > Pierrick Bouvier <pierrick.bouvier(a)linaro.org&gt; writes: > > > Note: This RFC was posted to trigger a discussion around this topic, and it's > > not expected to merge it as it is. > > > > Context > > ======= > > > > Linaro is working towards heterogeneous emulation, mixing several architectures > > in a single QEMU process. The first prerequisite is to be able to build such a > > binary, which we commonly name "single-binary" in our various series. > > An (incomplete) list of series is available here: > > https://patchew.org/search?q=project%3AQEMU+single-binary > > > > We don't expect to change existing command line interface or any observable > > behaviour, it should be identical to existing binaries. If anyone notices a > > difference, it will be a bug. > > Define "notice a difference" :) More on that below. > Given a single-binary *named* exactly like an existing qemu-system-X binary, any user or QEMU management layer should not be able to distinguish it from the real qemu-system-X binary. The new potential things will be: - introduction of an (optional) -target option, which allows to override/disambiguate default target detected. - potentially more boards/cpus/devices visible, once we start developing heterogeneous emulation. See it as a new CONFIG_{new_board} present. Out of that, once the current target is identified, based on argv[0], there should be absolutely no difference, whether in the behaviour, UI, command line, or the monitor interfaces.