Subject: Re: port-amd64/37461: x86 cpu dmesg output is noisy
To: None <port-amd64-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Andrew Doran <ad@netbsd.org>
List: netbsd-bugs
Date: 12/09/2007 01:30:02
The following reply was made to PR port-amd64/37461; it has been noted by GNATS.

From: Andrew Doran <ad@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-amd64/37461: x86 cpu dmesg output is noisy
Date: Sun, 9 Dec 2007 01:25:11 +0000

 On Sun, Dec 02, 2007 at 06:35:00AM +0000, jmcneill@invisible.ca wrote:
 
 > System: NetBSD black.invisible.ca 4.99.38 NetBSD 4.99.38 (GENERIC) #74: Sun Dec 2 01:20:32 EST 2007 jmcneill@black.invisible.ca:/export/home/jmcneill/branches/jmcneill-pm/src/sys/arch/amd64/compile/GENERIC amd64
 > Architecture: x86_64
 > Machine: amd64
 > >Description:
 > 	dmesg output for cpu0 on a Core 2 Duo by default is massive:
 
 I think most of the CPU ident stuff should move into userland. The kernel
 doesn't need much of it to operate, as far as I remember only basic info
 about the cache, the frequency, cpu family and features. It should not be
 too hard to port the code to userland and make the info available there.
 cpuctl might be a good location for it.
 
 Thanks,
 Andrew