Hi, > Based on the information you provided, the reason this whole series > exists seems to be to remove the need to update modules in multiple > places.
Well, I'm trying to improve the way we handle module meta-data (see other mail just send for details). > Is there a real need to copy over the mechanism from the kernel, or > are the requirements actually different/simpler here? Even though the exact kind of meta-data is different (qemu wants know qom types implemented by module, kernel wants know what hardware a module can drive) the fundamental problem is the same: We need some meta-data about modules for lookup. The workflow is simliar too: The meta-data is stored in a .modinfo elf section. Then a utility collects that data and stores them in a database. For the kernel 'depmod' stores the data in /lib/modules/$version/modules.$name (with modules.alias being the largest database). I'm trying to have qemu-modinfo store this in modinfo.json. take care, Gerd
