On Sun, Sep 14, 2014 at 7:57 PM, Kirill Tkhai <tkhai@xxxxxxxxx> wrote: > On 14.09.2014 21:27, Oleg Nesterov wrote: >> On 09/14, Greg KH wrote: >>> >>> On Sun, Sep 14, 2014 at 02:18:13PM +0400, Kirill Tkhai wrote: >>>> This series implements a possibility to show the list of built-in drivers >>>> to userspace. The names of drivers will be the same as when they are modules. >>> >>> Have you looked at /sys/modules/ ? Doesn't that show what you want >>> here? >> >> Well, /sys/module/ doesn't list the modules (drivers) compiled in. Say, >> /sys/module/kernel. And it can't help a user to figure out that, say, the >> loop driver is already "loaded" because CONFIG_BLK_DEV_LOOP=y. >> >>> Module names aren't "standardized", we change them at times when needed, >>> just like CONFIG_ names. >> >> OK, but still the name will be the same, in /proc/modules or /proc/builtin. >> >>> What is your end goal here? As you say, config.gz is the real kernel >>> configuration, just having a list of modules built in isn't going to >>> help much in getting a working kernel config without it. >> >> Perhaps you are right... but otoh perhaps this can can be useful anyway. >> Again, a user can know about "insmod loop", but he can know nothing >> about CONFIG_ names. >> >> That said, I do not really understand 2/3. Not only I do not understand >> this kbuild magic, I am not sure I understand what /proc/built-in will >> actually show. > > It's a list of drivers, one driver per line: Built-in modules or drivers? :-) -- Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
