[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
QEMU modules improvements objective (Was: Re: [RFC 0/3] Improve module a
QEMU modules improvements objective (Was: Re: [RFC 0/3] Improve module accelerator error message)
Mon, 5 Jul 2021 10:18:15 +0200
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
On 7/1/21 1:27 AM, Jose R. Ziviani wrote:
> I'm sending this as RFC because it's based on a patch still on
> review, so I'd like to see if it makes sense.
> Tt will improve the error message when an accelerator module could
> not be loaded. Instead of the current assert error, a formated
> message will be displayed.
>  https://patchwork.kernel.org/project/qemu-devel/list/?series=506379
> Jose R. Ziviani (3):
> modules: Add CONFIG_TCG_MODULAR in config_host
> modules: Implement module_is_loaded function
> qom: Improve error message in module_object_class_by_name()
> include/qemu/module.h | 3 +++
> meson.build | 3 +++
> qom/object.c | 30 ++++++++++++++++++++++++++++++
> util/module.c | 28 +++++++++++++++++++++-------
> 4 files changed, 57 insertions(+), 7 deletions(-)
Open question to all,
why don't we have/add the ability to configure
for all potentially modular pieces?
It should be possible to say, I want to build the storage plugins as modules,
TCG I would like it built-in, and KVM as a module,
or any combination of these.
The most useful combination I see for virtualization use of qemu is with TCG as
a module (M), KVM as built-in (Y), and various other optional pieces as modules
Should this not be the vision? To me it looks that way.
- QEMU modules improvements objective (Was: Re: [RFC 0/3] Improve module accelerator error message),
Claudio Fontana <=