From owner-freebsd-hackers Tue Mar 26 11:59:12 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA11928 for hackers-outgoing; Tue, 26 Mar 1996 11:59:12 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA11923 for ; Tue, 26 Mar 1996 11:59:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.6.12/8.6.5) with SMTP id LAA09163; Tue, 26 Mar 1996 11:58:45 -0800 Message-Id: <199603261958.LAA09163@Root.COM> X-Authentication-Warning: implode.Root.COM: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-hackers@freebsd.org (FreeBSD hackers) Subject: Re: kgdb / remote gdb of the kernel? In-reply-to: Your message of "Tue, 26 Mar 1996 18:56:00 +0100." <199603261756.SAA14992@uriah.heep.sax.de> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 26 Mar 1996 11:58:45 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Bruce Evans wrote: > >> - associated clocks. The i586 cycle counter isn't affected by interrupts >> being enabled, so it may get way ahead of the (slow) current time. > >Why is this abuse of the i586 cycle counter still being used as a >clock replacement? I thought it was pretty clear after David's visit >at Intel that we should no longer use it. It was certainly clear to me. It's fundamentally incompatible with APM. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project