lkml.org 
[lkml]   [2004]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: module.viomap support for ppc64
From
Date
On Fri, 2004-08-20 at 15:57, Olaf Hering wrote:
> On Fri, Aug 20, Rusty Russell wrote:
>
> > Current implementation of aliases is to load one at random: multiple
> > alias resolution is undefined because noone knew what we should do (load
> > them all? Load until one succeeds?). But note that that the base
> > config file overrides anything extracted from the modules themselves, so
> > users/distributions can always specify an exact match.
>
> How is the blacklist stuff supposed to work then? It must be possible
> to map an alias entry to a list of modules, and check if any of them is
> blacklisted. Then just 'for i in $DRIVERS ; do modprobe $i ; done'.

Olaf, I'm trying to understand the problem. We currently have a system
where modprobe resolves aliases, and that's good because it allows users
to override those aliases. We could have a "modprobe --resolve-aliases"
function, but that breaks down if the user puts in an install command,
which they should be able to do.

Looking through SLES and my Debian system, I see:
1) Modules which never want autoloading (eg. evbug)
2) Modules which defer to other modules (eg. de4x5)
3) Modules for which you want to suppress autoloading altogether because
they cause problems, or are handled by other subsystems.

For (1), the information should be contained in the module itself. This
will involve a kernel patch.

For (2), the information should be placed in /etc/modprobe.d/ overriding
those aliases the preferred way.

For (3), modprobe cannot have this in a config file, because what needs
to be blacklisted depends on who is invoking modprobe. For example,
there's a comment that ISDN modules on SuSE are not handled by hotplug,
but /etc/init.d/isdn.

So, a solution would be:
a) A "MODULE_NO_TABLES" macro which suppresses ID table alias
generation,
b) A -X argument to modprobe which says "don't load these modules", and
c) Change modprobe to load all the aliases which match, not just one? I
hadn't done this because I wasn't aware of anything which needed it: is
there something?

I think we're getting there: sorry if I seem a bit obtuse...
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.035 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site