Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Asking for path to modules (was: How do I keep testing current-amd64 witout so much trouble?)

On Mon, Dec 29, 2008 at 04:05:23AM -0800, Paul Goyette wrote:

> On Mon, 29 Dec 2008, Andrew Doran wrote:
> >On Fri, Dec 26, 2008 at 10:17:49AM -0500, Christos Zoulas wrote:
> >
> >>I don't know. but I think that the simplest solution for LOCKDEBUG
> >>kernels is to avoid the issue by not allowing spinouts while we
> >>are sleeping for input, using a global variable. It is ugly, but I
> >>don't have a better idea right now.
> >
> >I pointed out in a seperate forum that kernel_lock should no longer be
> >required in this path. Removing the KERNEL_LOCK() call in init_main.c
> >should solve the problem.
> Do you mean the KERNEL_LOCK() call in configure() in 
> kern/subr_autoconf.c:484?

I changed this so it shouldn't be a problem.

I think the proposed change is not complete because the boot loader also
pulls in modules. I have no objection to adding it to the list of questions
for 'boot -a', but without a command to set the default in the boot loader
it's a bit useless. An override set in the boot loader could, on x86, be
passed in with a bootinfo entry and in turn set the kernel's default.


Home | Main Index | Thread Index | Old Index