From owner-freebsd-current@FreeBSD.ORG Sun Jul 18 02:30:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E701C16A4CE for ; Sun, 18 Jul 2004 02:30:46 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52C3E43D3F for ; Sun, 18 Jul 2004 02:30:44 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.0.200] ([192.168.0.200]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i6I2aXjp047455; Sat, 17 Jul 2004 20:36:33 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <40F9E0CB.4090106@samsco.org> Date: Sat, 17 Jul 2004 20:30:35 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7) Gecko/20040702 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Buelow References: <200407180146.i6I1kiQ9004838@apollo.backplane.com> <40F9DD1B.3050902@mukappabeta.de> In-Reply-To: <40F9DD1B.3050902@mukappabeta.de> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: panic: APIC: Previous IPI is stuck X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jul 2004 02:30:47 -0000 Matthias Buelow wrote: > Matthew Dillon wrote: > >> I would expect it to perform about the same as the existing code. >> The >> main reasons to use it are that it consolidates the half dozen IPI >> mechanisms used by FreeBSD-5 into *one* mechanism, it completely > > > Don't you (and others on this list) think that these things come a bit > late now? I have just subscribed to this list since I'm using 5.2.1 and > what I expected were discussions like, the last few bugs being ironed > out, things getting polished for a stable 5.x tree, and not grass-roots > discussions about the basic system architecture. This comes about 2-3 > years late, folks. Please get your things together and stabilize the > beast now. > The 'fix the bugs' discussions are going on too. However, this is the freebsd-current list, and it's always nice to discuss things that might be suitable further down the road. Scott