On Fri, Feb 28, 2014 at 2:33 PM, Andy Lutomirski <luto@xxxxxxxxxxxxxx> wrote: > I'm working on virtme > (https://git.kernel.org/cgit/utils/kernel/virtme/virtme.git/), a tool > to easily test a kernel without a disk image or any need to install > that kernel. I want to have full support for loading modules from a > kernel tree, but depmod is getting in the way. > > What I think I want is a way to generate modules.dep, etc in a > subdirectory of the kernel build directory. The hierarchy needs to be > such that: > > - modprobe --show-depends would work. > - I could symlink and/or bind-mount things into /lib/modules so that > modprobe, udev, etc all work. > > One approach that should work: > > .tmp_moddep/build: a symlink to '..' > .tmp_moddep/modules.dep, etc: the usual, with module paths that point > into build/ > > The problem is that getting depmod to generate anything remotely like > this is basically impossible. > > Here are two changes to depmod that would, I think, make this possible: > > 1. Add --moddir, an option to specify the target directory directly. > That is, if --moddir is used, then -b would be illegal, the kernel > version could not be specified, and cfg.dirname would be set to the > argument of --moddir, literally. > > 2. Allow relative paths to modules on the command line. Such paths > would be interpreted relative to cfg.dirname. (That would probably be > easiest if depmod would chdir into cfg.dirname.) > > To finish the job, modprobe would need a --moddir argument as well. > > Thoughts? Is there a different approach I should be taking here? Did you already take a look in the testsuite? We can execute modprobe and depmod there. Would that approach be feasible for you? Lucas De Marchi -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
