public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: What is listed in /sys/module?
Date: Wed, 29 May 2013 10:27:35 +0200	[thread overview]
Message-ID: <20130529102735.3ce72ecc@endymion.delvare> (raw)

Hi Greg, Rusty,

I have a question related to /sys/module and can't seem to find the
answer by myself so I hope you can explain.

I noticed that /sys/module contains more than /proc/modules. At first I
thought that any potentially modular piece of code would show up
in /sys/module, so /sys/module would include both actual modules and
"built-in modules".

However I then noticed that some built-in modules do _not_ show up
in /sys/module. For example, I have USB and I2C core support built into
my 3.9.4 kernel, /sys/module/usbcore exists but /sys/module/i2c_core
does not. CONFIG_SENSORS_W83795=y did not give me /sys/module/w83795
either.

So my questions are:
1* What exactly is supposed to show up in /sys/module?
   Documentation/ABI/stable/sysfs-module says:

	/sys/module/MODULENAME
		The name of the module that is in the kernel.  This
		module name will show up either if the module is built
		directly into the kernel, or if it is loaded as a
		dynamic module.

  But my tests above contradict this statement.

And more precisely:
2* For what reason do some built-in modules show up in /sys/module and
   others do not? Is it a bug?

Thanks,
-- 
Jean Delvare

             reply	other threads:[~2013-05-29  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  8:27 Jean Delvare [this message]
2013-05-30  0:54 ` What is listed in /sys/module? Rusty Russell
2013-05-30  6:23   ` anish singh
2013-05-30  8:34     ` Jean Delvare
2013-05-30  9:26       ` anish singh
2013-05-30  9:38         ` Jean Delvare

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=20130529102735.3ce72ecc@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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