From: Ben Hutchings <bhutchings@solarflare.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
Jesse Gross <jesse@nicira.com>,
"David S. Miller" <davem@davemloft.net>, Greg KH <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: No sysfs directory for openvswitch module when built-in
Date: Tue, 5 Feb 2013 17:59:44 +0000 [thread overview]
Message-ID: <1360087184.2857.2.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <87boc0liug.fsf@rustcorp.com.au>
On Mon, 2013-02-04 at 16:29 +1030, Rusty Russell wrote:
> Cong Wang <xiyou.wangcong@gmail.com> writes:
> > Hello, Rusty, Jesse,
> >
> > I met an interesting problem when I compile openvswitch module as a
> > built-in (actually I compile ALL kernel modules as built-in), there is
> > no /sys/module/openvswitch/ directory created by the kernel in this
> > case.
> ...
> > What's worse, the user-space init script thinks openvswitch module is
> > not loaded by checking the exist of this directory, therefore refuses
> > to start.
>
> We only know built-in "modules" exist if we see a parameter or version
> which mention them. Looking for /sys/module/openvswitch/ is almost as
> flawed as looking in /proc/modules.
>
> I hacked up something which lists KBUILD_MODNAME for every element in my
> kernel which did EXPORT_KERNEL or module_init, and most of them can
> never be modules, though any could have parameters. Even if we changed
> the build system so we could tell things which "could have been a
> module", it's silly.
[...]
Isn't this information already provided by modules.builtin?
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-02-05 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 14:15 No sysfs directory for openvswitch module when built-in Cong Wang
2013-02-04 5:59 ` Rusty Russell
2013-02-05 14:28 ` Cong Wang
2013-02-05 17:59 ` Ben Hutchings [this message]
2013-02-06 23:38 ` Rusty Russell
2013-02-04 16:19 ` Stephen Hemminger
2013-02-05 6:08 ` Ben Pfaff
2013-02-05 10:49 ` Cong Wang
2013-02-05 19:15 ` Ben Pfaff
2013-02-05 22:11 ` Stephen Hemminger
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=1360087184.2857.2.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=greg@kroah.com \
--cc=jesse@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=xiyou.wangcong@gmail.com \
/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).