From owner-freebsd-current@FreeBSD.ORG Sun Mar 29 23:41:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D5DD106564A for ; Sun, 29 Mar 2009 23:41:02 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from dhcp-172-28-76-41.eur.corp.google.com (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D1C068FC12; Sun, 29 Mar 2009 23:41:01 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <49D0070D.2060905@FreeBSD.org> Date: Mon, 30 Mar 2009 00:41:01 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302) MIME-Version: 1.0 To: wenji wu References: <49D0046C.8020909@FreeBSD.org> In-Reply-To: <49D0046C.8020909@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: LOCK_PROFILING does not work on FreeBSD 8.0-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2009 23:41:02 -0000 Kris Kennaway wrote: > wenji wu wrote: >>> Do you have both wenjikernel and WENJIKERNEL config files? >> >>>>>> (4) run "make installkernel kernconf=WENJIKERNEL" >>>>> KERNCONF and the value of this variable are both case-sensitive. >> >> No, I just have "wenjikernel". >> >> It was a typo in the email. >> >> As you know, even I have both wenjikernel and WENJIKERNEL config >> files, if I >> run "make installkernel kernconf xxxx", the install process won't go >> through. For a successful kernel installing, "kernconf" has to be >> upper-case >> as "KERNCONF". >> >> Nothing wrong with my compiling and installing process! It was an email >> typo. > > OK, but you've still not shown that you didn't accidentally make a > mistake somewhere along the way. > > I asked you to confirm the exact steps you took because something > doesn't make sense, so it's important to show what you actually did > rather than retyping from memory what you think you did, in case you had > made a mistake without noticing it. > > Here is the output of a FreeBSD 8.0 system showing that LOCK_PROFILING > does in fact work as expected: > > gohan10# uname -a > FreeBSD gohan10.freebsd.org 8.0-CURRENT FreeBSD 8.0-CURRENT #8: Sun Mar > 29 12:06:13 UTC 2009 gohan10# grep LOCK_PROFILING > root@gohan10.freebsd.org:/usr/src/sys/amd64/compile/CLUSTER amd64 > /usr/src/sys/amd64/conf/CLUSTER > options LOCK_PROFILING Sorry, that pasted badly, it should have read: gohan10# uname -a FreeBSD gohan10.freebsd.org 8.0-CURRENT FreeBSD 8.0-CURRENT #8: Sun Mar 29 12:06:13 UTC 2009 root@gohan10.freebsd.org:/usr/src/sys/amd64/compile/CLUSTER amd64 gohan10# grep LOCK_PROFILING /usr/src/sys/amd64/conf/CLUSTER options LOCK_PROFILING > gohan10# sysctl -a | grep debug.lock > debug.lock.prof.enable: 0 > debug.lock.prof.reset: 0 > debug.lock.prof.stats: > debug.lock.prof.rejected: 0 > debug.lock.prof.skipcount: 0 > debug.lock.prof.skipspin: 0 > > Kris > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >