[lkml]   [2013]   [Feb]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: No sysfs directory for openvswitch module when built-in
On Mon, 2013-02-04 at 16:29 +1030, Rusty Russell wrote:
> Cong Wang <> 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 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.

 \ /
  Last update: 2013-02-05 19:21    [W:0.095 / U:1.352 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site