Re: Modules loading modules?

On Wed, 28 Jul 2010, Andrew Doran wrote: If modload-from-modcmd is found necessary, sounds more like a case for the infamous recursive lock. Recursive lock is the way to go. I think the same lock should also cover all device configuration activites (i.e. autoconf) and any other heavy lifting

_lwp_setprivate and _lwp_makecontext

Hi all, I'm working on Thread Locale Storage support for NetBSD and I am facing an interesting issue with the libpthread integration. On i386 and AMD64, TLS support uses the segment register %gs or %fs to load the thread pointer. The location used as segment base is thread specific and stored in

UVM / pmap assertion under load

Trying to get a stress test consisting of a bunch of fsx, fsstress and dbench running this combination leads within minutes to a failed assertion (npte PG_RW) != 0 in file x86/x86/pmap.c. With some tracing I always get the same pattern: - fsx gets a trap(), user memory, write. - the uobj is a

Re: _lwp_setprivate and _lwp_makecontext

hi, Hi all, I'm working on Thread Locale Storage support for NetBSD and I am facing an interesting issue with the libpthread integration. On i386 and AMD64, TLS support uses the segment register %gs or %fs to load the thread pointer. The location used as segment base is thread specific and