From owner-freebsd-current@FreeBSD.ORG  Wed Nov 14 00:46:42 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F342916A418;
	Wed, 14 Nov 2007 00:46:41 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b])
	by mx1.freebsd.org (Postfix) with ESMTP id 5508713C4B8;
	Wed, 14 Nov 2007 00:46:41 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <473A4570.9020908@FreeBSD.org>
Date: Wed, 14 Nov 2007 01:46:40 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: julian@FreeBSD.org,  current@FreeBSD.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Loss of detail from kthreads
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2007 00:46:42 -0000

Hi,

Since the conversion from kprocs to kthreads there is a loss of 
precision in how kernel process names are reported, because they now 
mostly report the kproc name which is very generic.

e.g. if you only use top -S then you only have "idle", "intr" processes, 
etc.  You have to use top -SH, but then you also see the userland 
threads, and there might be hundreds of them obscuring the kernel 
threads.  Also, ps now only displays the kproc:

root      12 100.0  0.0     0   136  ??  RL   Sat01PM   6:28.30 [intr]

so you can't see which interrupt(s) are using CPU.

Finally, I noticed that DDB only displays the kproc name in e.g. allpcpu:

cpuid        = 1
curthread    = 0xcb41da50: pid 12 "intr"
curpcb       = 0xe992cd90
fpcurthread  = none
idlethread   = 0xc67b7420: pid 11 "idle"
APIC ID      = 1
currentldt   = 0x50

Probably other things are also affected.  All of these make kernel 
analysis and debugging much less convenient, so this seems to me to be a 
step backwards.  Are you still working on fixing these issues?

Kris