on 16/12/2011 01:16 Hans Petter Selasky said the following:
> I think I was not aware about the Giant locking maybe having something to do
> about this. I was just thinking about this recently, that syscons and all
> keyboard stuff, currently is Giant locked. Scary?
Nope :-)
I think that no sysc
Replying further...
on 16/12/2011 00:56 Hans Petter Selasky said the following:
> On Thursday 15 December 2011 15:17:01 Andriy Gapon wrote:
>> Hmm... I looked at the history of ukbd.c (which I should have done from the
>> very start) and I see two relevant revisions:
>> http://svnweb.freebsd.org/
On Saturday 17 December 2011 15:57:24 Andriy Gapon wrote:
> on 16/12/2011 01:16 Hans Petter Selasky said the following:
> > I think I was not aware about the Giant locking maybe having something to
> > do about this. I was just thinking about this recently, that syscons and
> > all keyboard stuff,
On Saturday 17 December 2011 15:57:30 Andriy Gapon wrote:
> Replying further...
>
> > Not directly, but indirect. You know, if you pause thread 1 (which I
> > thought was thread 0), then other thread will get a chance to run.
>
> pause() could be a sufficient action to let other thread run, but i
I look at the following code:
static void
module_init(void *arg)
{
sx_init(&modules_sx, "module subsystem sx lock");
TAILQ_INIT(&modules);
EVENTHANDLER_REGISTER(shutdown_final, module_shutdown, NULL,
SHUTDOWN_PRI_DEFAULT);
}
SYSINIT(module, SI_SUB_KLD, SI_ORD
5 matches
Mail list logo
