From owner-freebsd-arch Tue Aug 20 17:54:17 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B77537B400 for ; Tue, 20 Aug 2002 17:54:15 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D14E43E6E for ; Tue, 20 Aug 2002 17:54:15 -0700 (PDT) (envelope-from baka@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1921) id EE801AE216; Tue, 20 Aug 2002 17:54:14 -0700 (PDT) Date: Tue, 20 Aug 2002 17:54:14 -0700 From: Jon Mini To: Poul-Henning Kamp Cc: Alexander Leidinger , arch@FreeBSD.ORG Subject: Re: timestamping kernel messages Message-ID: <20020821005414.GJ3751@elvis.mu.org> References: <20020820133215.0545063d.Alexander@Leidinger.net> <24056.1029843322@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <24056.1029843322@critter.freebsd.dk> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Poul-Henning Kamp [phk@critter.freebsd.dk] wrote : > I think we need to revamp the console/logging system in toto. > > I think we should have a pseudo-device for console/log use, > which stores thing in a circular buffer. > > Syslogd would then retreive stuff from that buffer, somewhat > like what it does today. > > For tty console usage, we should have a kernel thread which > picks things out of the buffer and prints it on the chosen > console, and putting a timestamp on it would be a Good Thing. I, also, am not happy with the current console code. It has several problems that really irritate me, such as the fact that messages are sent to the console one character at a time, resulting in jumbled messages like: | MSoMuPn:t iAnPg CrPoUo t# 1f rLoamu nucfhse:d/!d | ev/ad0a It would be very nice to at least see printf() and friends insert messages into per-cpu line buffers that are sent to the console at every newline (of course we'd have to toggle that behaviour while taking input from the console). Funneling console activity through a circular buffer with one write channel and several read channels could be useful, especially if its also available from userland. I've got patches that do this to klog (I would like to see the msgbuf stuff go). Being able to "tail -f /var/klog" and get a trace of console activity is nice. > This would also give us a good architecture for hooking up > ethernet consoles. Do you mean console over TCP? I'd really like to see gdb -k over TCP, and asynchronous, too. It would be nice to only tie one kernel thread to a gdb process and not the entire system. -- Jonathan Mini http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message