From owner-freebsd-acpi@FreeBSD.ORG Fri Nov 12 07:12:59 2004 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9256616A4CE; Fri, 12 Nov 2004 07:12:59 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 355BE43D31; Fri, 12 Nov 2004 07:12:59 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAC7EeZT002819; Fri, 12 Nov 2004 00:14:40 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <419462B1.6090103@freebsd.org> Date: Fri, 12 Nov 2004 00:13:53 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411111737.00537.jhb@FreeBSD.org> In-Reply-To: <200411111737.00537.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.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: acpi@freebsd.org cc: gallatin@freebsd.org Subject: Re: New ACPI PCI Link Routing code X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Nov 2004 07:12:59 -0000 John Baldwin wrote: > I've done some work on the ACPI PCI link code to make it a bit more like $PIR > in that it is link centric and uses actual new-bus devices for each device > link. One benefit of this is that unused links will be disabled now which > might help with interrupt aliasing problems on machines using APICs. Also, > instead of routing IRQs for links via PCI device numbers using tunables, they > are now routed via the link name ala $PIR. Thus, one uses > 'hw.pci.link.LNKA.irq=X' to route LNKA to IRQ X. Also, when choosing a > virgin interrupt, we no longer try to guess at which IRQs might be used by > ISA devices. Instead, we only use known-good IRQs including IRQs that the > BIOS has already used and the SCI if the link is being routed via ISA IRQs. > The patch is at http://www.FreeBSD.org/~jhb/patches/acpi_pci_link.patch > Please test and let me know if there are any problems, thanks. > I had to hack up acpi_pcib_acpi.c in order to get it to compile. The result boots, but it doesn't seem to change anything and doesn't help the interrupt aliasing issues that I have. The dmesg is at http://people.freebsd.org/~scottl/dmesg.wv1u.nov12. The interrupt aliasing manifests itself as irq 16 getting all of the interrupts from both irq 30 and 49. 30 and 49 still get their interrupts, and they don't get each other's interrupts. Scott