From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DrZwl-0002RS-If for qemu-devel@nongnu.org; Sun, 10 Jul 2005 07:26:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DrZwc-0002Mv-Ep for qemu-devel@nongnu.org; Sun, 10 Jul 2005 07:25:58 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DrZwa-0002GX-G9 for qemu-devel@nongnu.org; Sun, 10 Jul 2005 07:25:56 -0400 Received: from [81.103.221.48] (helo=mta08-winn.ispmail.ntl.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DrZos-0005kC-2u for qemu-devel@nongnu.org; Sun, 10 Jul 2005 07:17:58 -0400 Subject: Re: [Qemu-devel] kqemu freebsd host smp problems? From: Antony T Curtis In-Reply-To: <200507100439.j6A4dlMK074874@sakura.ninth-nine.com> References: <20050704010715.A36404@saturn.kn-bremen.de> <200507040037.j640bg0v085158@gate.bitblocks.com> <200507100439.j6A4dlMK074874@sakura.ninth-nine.com> Content-Type: text/plain Date: Sun, 10 Jul 2005 12:10:28 +0100 Message-Id: <1120993828.46929.7.camel@pcgem.xiphis.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Norikatsu Shigemura Cc: Craig Boston , jhb@FreeBSD.org, alc@FreeBSD.org, jeff@FreeBSD.org, qemu-devel@nongnu.org, freebsd-current@FreeBSD.org, Bakul Shah , Juergen Lock On Sun, 2005-07-10 at 13:39 +0900, Norikatsu Shigemura wrote: > On Sun, 03 Jul 2005 17:37:42 -0700 > Bakul Shah wrote: > > Lock writes: > > > Is kqemu and the freebsd wrapper smp aware? I just saw this panic > > > report again, > > > http://lists.freebsd.org/pipermail/freebsd-current/2005-May/050161.html > > > and noticed it apparently happened with an smp kernel. > > My guess is > > .d_flags = D_NEEDGIANT, > > needs to be added to the initializer of kqemu_cdevsw for the > > freebsd-current case. AFAIK this flag ensures only one > > thread can be in this driver at a time (but caveat emptor: I > > don't play in the kernel these days). > > I confirmed that qemu on latest FreeBSD 6-current got more > stability!!, but more little slowly:-( and a panic:-( too. IMO, That flag is not the cause of the panics and that it should(tm) work without requiring GIANT... I think it is possible that the kqemu code is freeing a page without unlocking it so that when another process does file IO which requires pages to be allocated, attempts to wire those pages results in failure and so a panic occurrs. Perhaps if a different method for allocating memory rather than contigmalloc/contigfree should be used by the kernel module. Offtopic - but am I the only person who has modified the if_tap driver to permit opening by non-superuser? -- Antony T Curtis, BSc. UNIX, Linux, *BSD, Networking antony.t.curtis@ntlworld.com C++, J2EE, Perl, MySQL, Apache IT Consultancy.