From: Kirill Tkhai <tkhai@yandex.ru>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "mmarek@suse.cz" <mmarek@suse.cz>,
"arnd@arndb.de" <arnd@arndb.de>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"oleg@redhat.com" <oleg@redhat.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"ktkhai@parallels.com" <ktkhai@parallels.com>,
"sam@ravnborg.org" <sam@ravnborg.org>
Subject: Re: [PATCH 0/3] Implement /proc/built-in file similar to /proc/modules
Date: Mon, 15 Sep 2014 15:50:03 +0400 [thread overview]
Message-ID: <923151410781803@web9m.yandex.ru> (raw)
In-Reply-To: <20140914185631.GB18506@kroah.com>
14.09.2014, 22:56, "Greg KH" <gregkh@linuxfoundation.org>:
> On Sun, Sep 14, 2014 at 10:35:58PM +0400, Kirill Tkhai wrote:
>> On 14.09.2014 22:13, Greg KH wrote:
>>> On Sun, Sep 14, 2014 at 10:05:46PM +0400, Kirill Tkhai wrote:
>>>> On 14.09.2014 21:39, Greg KH wrote:
>>>>> On Sun, Sep 14, 2014 at 09:31:58PM +0400, Kirill Tkhai wrote:
>>>>>> On 14.09.2014 19:38, 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?
>>>>>> There are only the drivers in "/sys/module" which have parameters.
>>>>>> Drivers without parameters do not appear there.
>>>>> Ah, didn't realize that. Should be easy to fix though, if you really
>>>>> wanted to list the modules. Much better than a random proc file that
>>>>> you have to parse :)
>>>> But it looks like one file is better than many new directories.
>>> Why?
>> It's just an unification with /proc/modules. Why should we do any
>> difference between external and built-in modules? It's the same,
>> it's similar, it's better to parse when they can be shown similar.
>
> /proc/modules is for loaded modules, and it includes lots of information
> that tools rely on. It is also a very old file, no new
> non-process-related proc/ files should be created anymore. It's been
> that way since sysfs was created (and one of the reasons for sysfs.)
>>> No, they want the functionality that a module provides, not the module
>>> name, or some random configuation option.
>>>
>>> It seems like you are trying to solve a problem that isn't there. What
>>> program is broken right now that this new proc file (or sysfs directory)
>>> would fix?
>> The initial reason was I'm building custom kernels for more than 10
>> years (not so long, I agree), and every boot I see a big list of modules
>> from distribution /etc/module, which can't be autoloaded. I prefer to
>> build drivers in kernel. I tried to find is there a way for userspace to
>> understand that a module are present, but there is no a way. So this is
>> a reason.
>
> I don't understand, my distro doesn't have any modules listed in
> /etc/module that aren't autoloaded, perhaps you should work with your
> distro on that :)
>
> And how would these patches remove those config files?
>
> Again, focus on kernel functionality, not module names or config
> options, and you should be fine.
Ok, I have no objections anymore.
Thanks,
Kirill
next prev parent reply other threads:[~2014-09-15 11:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 10:18 [PATCH 0/3] Implement /proc/built-in file similar to /proc/modules Kirill Tkhai
2014-09-14 10:18 ` [PATCH 1/3] kbuild: Make targets names tree-wide unique on x86 Kirill Tkhai
2014-09-14 15:57 ` Peter Foley
2014-09-14 18:09 ` Kirill Tkhai
2014-09-14 10:18 ` [PATCH 2/3] core: Save list of built-in drivers names Kirill Tkhai
2014-09-14 10:19 ` [PATCH 3/3] core: create /proc/built-in file to show the list of built-in drivers Kirill Tkhai
2014-09-14 15:38 ` [PATCH 0/3] Implement /proc/built-in file similar to /proc/modules Greg KH
2014-09-14 17:27 ` Oleg Nesterov
2014-09-14 17:57 ` Kirill Tkhai
2014-09-14 18:12 ` Richard Weinberger
2014-09-14 18:58 ` Kirill Tkhai
2014-09-14 20:00 ` Oleg Nesterov
2014-09-14 17:31 ` Kirill Tkhai
2014-09-14 17:39 ` Greg KH
2014-09-14 18:05 ` Kirill Tkhai
2014-09-14 18:13 ` Greg KH
2014-09-14 18:35 ` Kirill Tkhai
2014-09-14 18:56 ` Greg KH
2014-09-15 11:50 ` Kirill Tkhai [this message]
2014-09-16 15:40 ` Lucas De Marchi
2014-09-15 9:17 ` Michal Marek
2014-09-15 9:12 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=923151410781803@web9m.yandex.ru \
--to=tkhai@yandex.ru \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=ktkhai@parallels.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=oleg@redhat.com \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).