* De: Maxime Henrion <[EMAIL PROTECTED]> [ Data: 2002-11-22 ]
        [ Subjecte: Re: VM locking problem... And doscmd(8) ]
> John Baldwin wrote:
> > 
> > On 22-Nov-2002 Juli Mallett wrote:
> > > * De: Robert Watson <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
> > >       [ Subjecte: Re: VM locking problem... And doscmd(8) ]
> > >> For those of us that don't frequently (ever) use doscmd -- can you provide
> > >> a tarball of the necessary configuration files, executable, etc,
> > >> somewhere? 
> > > 
> > > I don't (ever) either, and am doing this without a config file (as far as
> > > I'm aware anyway), and using the following executable:
> > > 
> > > http://people.freebsd.org/~jmallett/boom.exe
> > 
> > There is some discussion on IRC, and Maxime is working on a fix.  The
> > problem is that if you use a TSS (for /dev/io or some such) then the
> > TSS gets kmem_free()'d in cpu_thread_exit().  However, cpu_thread_exit()
> > is a particularly bad time to be calling kmem_free() as you are holding
> > sched_lock in a critical section w/o any sleep mutexes when it is called.
> > :)  The solution I've discussed with Maxime is to create a
> > cpu_thread_dtor() callout called from thread_dtor() (which is called when
> > a thread is free()'d) and to move the kmem_free() of the TSS into
> > that function instead.
> 
> The attached patch fixes it for me.  It free()'s the TSS in the new
> cpu_thread_dtor() function as John suggested.

Works great, thanks!

juli.
-- 
Juli Mallett <[EMAIL PROTECTED]>
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to