Date: Sun, 12 Apr 2009 12:26:02 -0700 From: Bakul Shah <bakul@bitblocks.com> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: jtidwell <necanthrope@gmail.com>, freebsd-emulation@freebsd.org Subject: Re: cannot get kqemu to load with kldload Message-ID: <20090412192602.661B45B23@mail.bitblocks.com> In-Reply-To: Your message of "Sun, 12 Apr 2009 20:56:24 %2B0200." <20090412185624.GB65339@triton.kn-bremen.de> References: <22999502.post@talk.nabble.com> <22999521.post@talk.nabble.com> <200904121415.n3CEFDCf025538@triton.kn-bremen.de> <20090412182939.E23F15B23@mail.bitblocks.com> <20090412185624.GB65339@triton.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 12 Apr 2009 20:56:24 +0200 Juergen Lock <nox@jelal.kn-bremen.de> wrote: > On Sun, Apr 12, 2009 at 11:29:39AM -0700, Bakul Shah wrote: > > > > But this brings up another problem with kqemu: if you are > > using SCHED_4BSD with 7.x or current, kqemu is not guaranteed > > to work. > > Oh, so the code it then uses in kqemu_schedule() is ule only? > Does the old scheduler still use sched_lock? > > [...] > struct thread *td = curthread; > thread_lock(td); > mi_switch(SW_VOL, NULL); > thread_unlock(td); > [...] You'd have to ask a scheduling expert but it appears that 4BSD sticks sched_lock in thread lock so it should just work (checked only in -current). So I take back my complaint :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090412192602.661B45B23>