From owner-freebsd-arch@FreeBSD.ORG Sat Sep 20 19:34:36 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39AF01065672 for ; Sat, 20 Sep 2008 19:34:36 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 11BBE8FC16 for ; Sat, 20 Sep 2008 19:34:35 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m8KJYYFY045789 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Sep 2008 12:34:35 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <48D5504A.7080309@freebsd.org> Date: Sat, 20 Sep 2008 12:34:34 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: Matthew Dillon References: <200809191437.28550.jhb@freebsd.org> <20080920082949.GX81522@hoeg.nl> <20080920092034.GC49919@rink.nu> <48D52B76.9080606@freebsd.org> <200809201731.m8KHVPbq030945@apollo.backplane.com> In-Reply-To: <200809201731.m8KHVPbq030945@apollo.backplane.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: arch@freebsd.org Subject: Re: Trim interrupt messages in dmesg.. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2008 19:34:36 -0000 Matthew Dillon wrote: > :Actually the code is useless. We need a way to identify how each > :handler is registered. So long as we have that I'm fine with trimming > :the msgs. Sticking it under bootverbose is ok too though I'd still like > :a way to see how the handler is registered w/o have to reboot. > : > : Sam > > I would recommend augmenting vmstat -i to provide the required > information. > Doesn't belong there IMO but devinfo (where I hoped it might go) lacks the context to collect the info. Sam