From owner-freebsd-arch@FreeBSD.ORG  Sat Sep 20 17:31:26 2008
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
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 298391065670
	for <arch@freebsd.org>; Sat, 20 Sep 2008 17:31:26 +0000 (UTC)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by mx1.freebsd.org (Postfix) with ESMTP id D801D8FC1A
	for <arch@freebsd.org>; Sat, 20 Sep 2008 17:31:25 +0000 (UTC)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com (localhost [127.0.0.1])
	by apollo.backplane.com (8.14.1/8.14.1) with ESMTP id m8KHVPAH030946
	for <arch@freebsd.org>; Sat, 20 Sep 2008 10:31:25 -0700 (PDT)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.14.1/8.13.4/Submit) id m8KHVPbq030945;
	Sat, 20 Sep 2008 10:31:25 -0700 (PDT)
Date: Sat, 20 Sep 2008 10:31:25 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200809201731.m8KHVPbq030945@apollo.backplane.com>
To: arch@freebsd.org
References: <200809191437.28550.jhb@freebsd.org>	<20080920082949.GX81522@hoeg.nl>
	<20080920092034.GC49919@rink.nu> <48D52B76.9080606@freebsd.org>
Cc: 
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 <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Sep 2008 17:31:26 -0000


: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.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>