On 6/16/21 11:28 AM, Gerd Hoffmann wrote: >>> Hmm, what would be the use case? Right now qemu has the all-or-nothing >>> approach for modules, i.e. if modules are enabled everything we can >>> build as module will be built as module, and I havn't seen any drawbacks >>> so far. So, why would one compile parts of qemu as module and other >>> parts not? >> >> From my point of view, as a QEMU package maintainer, the all-or-nothing >> module >> approach is great - specially for accelerators - because we can create a set >> of officially supported packages and another set of optional modules, that >> users may get them if they want to. > > Same here ;) > >> However, please correct me if I'm wrong, I understand that an accelerator as >> a >> module will add an overhead that some user won't be willing to pay. So, give >> them the option to have built-in accelerators seems a good idea. > > Modules add some overhead, yes, and there are surely use-cases where you
Where do we expect the overhead to be, and of which nature? Do we already know about such an impact? Thanks, CLaudio > don't want accel modules. I would just expect people don't want the > other modules either then, but maybe I'm wrong. > > take care, > Gerd >
