From owner-freebsd-current@FreeBSD.ORG  Fri Jan 20 05:13:00 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4D7AD16A41F
	for <current@freebsd.org>; Fri, 20 Jan 2006 05:13:00 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from a50.ironport.com (a50.ironport.com [63.251.108.112])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1539C43D46
	for <current@freebsd.org>; Fri, 20 Jan 2006 05:13:00 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from unknown (HELO [192.168.2.4]) ([10.251.60.95])
	by a50.ironport.com with ESMTP; 19 Jan 2006 21:12:59 -0800
X-IronPort-Anti-Spam-Filtered: true
Message-ID: <43D0715A.7020302@elischer.org>
Date: Thu, 19 Jan 2006 21:12:58 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.11) Gecko/20050727
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kris Kennaway <kris@obsecurity.org>
References: <43D05151.5070409@elischer.org>
	<20060120030105.GA5286@xor.obsecurity.org>
In-Reply-To: <20060120030105.GA5286@xor.obsecurity.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: current@freebsd.org
Subject: Re: kernel thread as real threads..
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: Fri, 20 Jan 2006 05:13:00 -0000

Kris Kennaway wrote:

>On Thu, Jan 19, 2006 at 06:56:17PM -0800, Julian Elischer wrote:
>  
>
>>some progrsss..
>>as the first few lines show, it's not quite perfect yet but it's most of 
>>the way there..
>>(Like proc 1 isn't init)
>>
>>SMP: AP CPU #1 Launched!
>>SMP: AP CPU #2 Launched!
>>SMP: AP CPU #3 Launched!
>>panic: blockable sleep lock (sleep mutex) buffer daemon lock @ 
>>/usr/src/sys/kern/vfs_bio.c:2048
>>cpuid = 2
>>KDB: enter: panic
>>[thread pid 0 tid 100051 ]
>>Stopped at      kdb_enter+0x2b: nop    
>>db> ps
>> pid   proc     uid  ppid  pgrp  flag   stat  wmesg    wchan  cmd
>>   1 c7cb1000    0     0     0 0000200 [SLPQ g_waitidle 
>>0xc07239ec][SLP] swapper
>>   0 c0723c40    0     0     0 0000288 (threaded)  swapper
>>  thread 0xc7d6a340 ksegrp 0xc7cb0960 [RUNQ] schedcpu
>>  thread 0xc7d6a4e0 ksegrp 0xc7cb09c0 [RUNQ] nfsiod 3
>>    
>>
>
>What about that threads don't show CPU usage or accumulate CPU time?
>This is annoying enough for user threads but would be a pretty serious
>usability limitation if it happened for kernel threads too.
>
>Kris
>  
>

the example I showed was the 'ps' from ddb which of course doesn't show 
any stats anyhow.

Well, stats are collected. It is just a case of getting them out and 
displayed..
It's kind of meaningless in KSE type threads but for libthr and kernel 
threads it would have meaning.

Anynow I just want to see what it takes to not have 40 extra proc 
structs hanging around.