On Thu, Apr 24, 2025 at 2:35 PM Pierrick Bouvier <pierrick.bouv...@linaro.org> wrote: > Feedback > ======== > > The goal of this series is to be spark a conversation around following topics: > > - Would you be open to such an approach? (expose all code, and restrict > commands > registered at runtime only for specific targets) > > - Are there unexpected consequences for libvirt or other consumers to expose > more definitions than what we have now? > > - Would you recommend another approach instead? I experimented with having per > target generated files, but we still need to expose quite a lot in headers, > so > my opinion is that it's much more complicated for zero benefit. As well, the > code size impact is more than negligible, so the simpler, the better.
Do you anticipate that Linux distributions will change how they package QEMU? For example, should they ship a single qemu-all package in addition to or as a replacement for the typical model today where qemu-system-aarch64, qemu-system-x86_64, etc are shipped as separate packages? It would be nice to hear from packager maintainers in this discussion so that there is a consensus between developers and package maintainers. Stefan
