Re: dev_lock() question
From: Poul-Henning Kamp (phk_at_phk.freebsd.dk)
Date: 09/29/05
- Previous message: John Baldwin: "Re: dev_lock() question"
- In reply to: John Baldwin: "Re: dev_lock() question"
- Next in thread: John Baldwin: "Re: dev_lock() question"
- Reply: John Baldwin: "Re: dev_lock() question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: John Baldwin <jhb@FreeBSD.org> Date: Thu, 29 Sep 2005 21:36:53 +0200
In message <200509291455.59914.jhb@FreeBSD.org>, John Baldwin writes:
>On Thursday 29 September 2005 02:14 pm, Poul-Henning Kamp wrote:
>> In message <200509291408.18098.jhb@FreeBSD.org>, John Baldwin writes:
>> >Actually, you would think that it could be initialized either via an early
>> >SYSINIT() or in the init_mutexes() function in kern_mutex.c and thus not
>> > need the early check and avoid penalizing dev_lock().
>> >
>> >phk, how early his dev_lock needed?
>>
>> Far too early due to console madness (in syscons I belive).
>
>So would mutex_init() work?
Havn't tried. It basically has to work right before the copyright
is printed.
-- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
- Previous message: John Baldwin: "Re: dev_lock() question"
- In reply to: John Baldwin: "Re: dev_lock() question"
- Next in thread: John Baldwin: "Re: dev_lock() question"
- Reply: John Baldwin: "Re: dev_lock() question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]