From owner-freebsd-current@FreeBSD.ORG Fri Nov 9 19:26:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFC4316A419 for ; Fri, 9 Nov 2007 19:26:28 +0000 (UTC) (envelope-from gavare@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id 28C0C13C4B8 for ; Fri, 9 Nov 2007 19:26:27 +0000 (UTC) (envelope-from gavare@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so107454ana for ; Fri, 09 Nov 2007 11:26:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:reply-to:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding:from; bh=ABafmDF18tzyZoCnqpCRIRpDqb3kSIhjACaEvUHn6D8=; b=iQMzrqE1+FVsQA2C83QStx1s7UKYug3swd/hMId//TTv/G+qMFpMe5hYXjkJVrWMbgg7Fithx2/4moNu84bpQWyQ9eTtQ6UbydExsYykR7se4vgj4lUJ2Vn/HRPFD2Cgdfv1Jrwr78MYzDIXIcxphKYiYUgRKu5qmyX+5fd0qSE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:reply-to:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding:from; b=B+Ie68YC3asYEy9LrtInePTu6cRHsdWuoqA91MIc6fPkX/VE2Iz0rGwy5QdtaAmjCJBvdPj1XBpGk5eQf8Gpqwfq2xhfxVwerZuNyze4va431icqQ+uV7YDMT/uW+6iGMS8ZdhFtKVZV5vXxMuQPQPqmF3pO65kUhCWQ4wbdCr4= Received: by 10.101.67.11 with SMTP id u11mr3455449ank.1194634742746; Fri, 09 Nov 2007 10:59:02 -0800 (PST) Received: from ?83.254.11.45? ( [83.254.11.45]) by mx.google.com with ESMTPS id d25sm2729344nfh.2007.11.09.10.59.00 (version=SSLv3 cipher=RC4-MD5); Fri, 09 Nov 2007 10:59:01 -0800 (PST) To: freebsd-current@freebsd.org Content-Type: text/plain Date: Fri, 09 Nov 2007 19:59:20 +0100 Message-Id: <1194634760.1749.9.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit From: Anders Gavare Subject: Re: device atpic to be deprecated? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: anders@gavare.se List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2007 19:26:28 -0000 Hi currenters! On Wednesday 29 March 2006, John Baldwin wrote: > On Wednesday 29 March 2006 12:08, Scott Long wrote: > > John Baldwin wrote: > > On Wednesday 29 March 2006 11:26, Scott Long wrote: > .. > >> >>>>On Wed, Mar 29, 2006 at 02:05:27AM -0600, Conrad J. Sabatier > >> >>>>wrote: > > >>>>>Is the plan still in effect to abolish this device? > > >>>> > > >>>>To my mind it wouldn't make much sense, given the sheer amount > > >>>>of hardware out there which doesn't have an IOAPIC, then again > > >>>>I'm probably out of touch with the state of interrupt handling > > >>>>in -CURRENT. > > >>> > > >>>All amd64 machines (which is where atpic would be removed) have > > >>>an APIC. > > >> > > >>That's kind of like saying that ISA will be removed because there > > >>is PCI > > >>=-) Having an APIC doesn't necessarily guarantee that it works. > > >>There have been enough reports of problems on the mailing lists > > >>over time that I think it's a bit premature to declare the ATPIC > > >>dead. Also, is the ATPIC code in amd64 causing problems, holding > > >>back progress, or creating a maintenance burden? > > > > > > I think that once the lapic timer stuff was added almost all of > > > the APIC issues I was aware of went away on amd64 that were fixed > > > by using device atpic instead. Most of the earlier problems were > > > due to chipsets not setting up pin 0 as extint, etc. but all that > > > is no longer relevant when we switched to using the lapic timer > > > and stopped using irq0 and irq8 with APIC. This is the first I've > > > heard since the lapic timer stuff that APIC didn't work on an > > > amd64 box, and device atpic has been off by default in HEAD for > > > quite a while now. If we were able to require APIC on amd64, then > > > we might be able to try out some optimizations and other things I > > > haven't bothered with since they wouldn't be feasible on i386. > > > > Fine, remove it. > > I have to make sure it really works for everyone first though before > removing it would really be viable. :-/ The GENERIC 7.0-BETA2 kernel does not boot on my 1.8 GHz amd64 laptop (and HP Pavilion ze2000). Not in safe mode, not without ACPI, not without apic0/sio0/sio1 (which is the usual trick on this machine). After some detective work, however, I noticed that with "device atpic" added, 7.0-BETA2 works fine on this machine. (I took a chance and updated my sources from 6-STABLE to 7-STABLE, added the device, and now I am running 7.0-BETA2. If I hadn't already had FreeBSD installed, it would not have been possible to get it to boot, though, so this feels kind of critical.) My question is: Is it possible to add "device atpic" again in time for the 7.0 release? What is the possible negative impact of adding it? Anders