[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071209081138.GB4954@uranus.ravnborg.org>
Date: Sun, 9 Dec 2007 09:11:38 +0100
From: Sam Ravnborg <sam@...nborg.org>
To: Tejun Heo <htejun@...il.com>
Cc: Linux Kernel <linux-kernel@...r.kernel.org>, notting@...hat.com,
rusty@...tcorp.com.au, kay.sievers@...y.org,
Greg KH <greg@...ah.com>
Subject: Re: [PATCH] kbuild: implement modules.order, take #2
On Fri, Dec 07, 2007 at 09:04:30PM +0900, Tejun Heo wrote:
> When multiple built-in modules (especially drivers) provide the same
> capability, they're prioritized by link order specified by the order
> listed in Makefile. This implicit ordering is lost for loadable
> modules.
>
> When driver modules are loaded by udev, what comes first in
> modules.alias file is selected. However, the order in this file is
> indeterministic (depends on filesystem listing order of installed
> modules). This causes confusion.
>
> The solution is two-parted. This patch updates kbuild such that it
> generates and installs modules.order which contains the name of
> modules ordered according to Makefile. The second part is update to
> depmod such that it generates output files according to this file.
>
> Note that both obj-y and obj-m subdirs can contain modules and
> ordering information between those two are lost from beginning.
> Currently obj-y subdirs are put before obj-m subdirs.
>
> Sam Ravnborg cleaned up Makefile modifications and suggested using awk
> to remove duplicate lines from modules.order instead of using separate
> C program.
>
> Signed-off-by: Tejun Heo <htejun@...il.com>
> Cc: Sam Ravnborg <sam@...nborg.org>
> Cc: Bill Nottingham <notting@...hat.com>
> Cc: Rusty Russell <rusty@...tcorp.com.au>
> Cc: Greg Kroah-Hartman <gregkh@...e.de>
> Cc: Kay Sievers <kay.sievers@...y.org>
Applied to kbuild.git.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists