From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752878AbaINSMs (ORCPT ); Sun, 14 Sep 2014 14:12:48 -0400 Received: from mail-vc0-f180.google.com ([209.85.220.180]:46081 "EHLO mail-vc0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752533AbaINSMq (ORCPT ); Sun, 14 Sep 2014 14:12:46 -0400 MIME-Version: 1.0 In-Reply-To: <5415D6ED.30508@yandex.ru> References: <20140914100545.3745.23394.stgit@localhost> <20140914153832.GC4064@kroah.com> <20140914172709.GA1569@redhat.com> <5415D6ED.30508@yandex.ru> Date: Sun, 14 Sep 2014 20:12:45 +0200 Message-ID: Subject: Re: [PATCH 0/3] Implement /proc/built-in file similar to /proc/modules From: Richard Weinberger To: tkhai@yandex.ru Cc: Oleg Nesterov , Greg KH , Michal Marek , Arnd Bergmann , linux-kbuild , LKML , Grant Likely , "Eric W. Biederman" , Andrew Morton , ktkhai@parallels.com, Sam Ravnborg Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 14, 2014 at 7:57 PM, Kirill Tkhai 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