From owner-freebsd-acpi@FreeBSD.ORG  Thu Feb 10 14:49:45 2005
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
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 36FEE16A4CE
	for <freebsd-acpi@freebsd.org>; Thu, 10 Feb 2005 14:49:45 +0000 (GMT)
Received: from f26.mail.ru (f26.mail.ru [194.67.57.194])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DFA7643D31
	for <freebsd-acpi@freebsd.org>; Thu, 10 Feb 2005 14:49:44 +0000 (GMT)
	(envelope-from _pppp@mail.ru)
Received: from mail by f26.mail.ru with local 
	id 1CzFdX-000HO8-00
	for freebsd-acpi@freebsd.org; Thu, 10 Feb 2005 17:49:43 +0300
Received: from [81.200.13.122] by win.mail.ru with HTTP;
	Thu, 10 Feb 2005 17:49:43 +0300
From: dima <_pppp@mail.ru>
To: freebsd-acpi@freebsd.org
Mime-Version: 1.0
X-Mailer: mPOP Web-Mail 2.19
X-Originating-IP: [81.200.13.122]
Date: Thu, 10 Feb 2005 17:49:43 +0300
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 8bit
Message-Id: <E1CzFdX-000HO8-00._pppp-mail-ru@f26.mail.ru>
Subject: interrupt routing
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: dima <_pppp@mail.ru>
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Feb 2005 14:49:45 -0000

I am preparing a new server for production use. It is dual Opteron Tyan S2882 motherboard containing 2 1000BaseTX NICs and 2 SCSI controllers onboard. Running 5.3-RELEASE-p5 (i386).
The interrupt assignment performed by ACPI looks kinda strange:
$ ps -ax
[irq24: bge0 ahd0]
[irq25: bge1 ahd1]
I actually want NICs and SCSI controllers run in different kernel threads.
$ pciconf -lv
ahd0@pci2:6:0:  class=0x010000 card=0x005e9005 chip=0x801d9005 rev=0x10 hdr=0x00
    vendor   = 'Adaptec Inc'
    device   = 'AIC-7902B Ultra320 SCSI Controller'
    class    = mass storage
    subclass = SCSI
ahd1@pci2:6:1:  class=0x010000 card=0x005e9005 chip=0x801d9005 rev=0x10 hdr=0x00
    vendor   = 'Adaptec Inc'
    device   = 'AIC-7902B Ultra320 SCSI Controller'
    class    = mass storage
    subclass = SCSI
bge0@pci2:9:0:  class=0x020000 card=0x164414e4 chip=0x164814e4 rev=0x03 hdr=0x00
    vendor   = 'Broadcom Corporation'
    device   = 'BCM5704 NetXtreme Dual Gigabit Adapter'
    class    = network
    subclass = ethernet
bge1@pci2:9:1:  class=0x020000 card=0x164414e4 chip=0x164814e4 rev=0x03 hdr=0x00
    vendor   = 'Broadcom Corporation'
    device   = 'BCM5704 NetXtreme Dual Gigabit Adapter'
    class    = network
    subclass = ethernet
All the devices are assigned IRQ10 in BIOS and I didnt found a way to change the settings there.
I have found a year-old discussion on -current
http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019964.html
about assigning physical IRQ lines to PCI devices; so I want to know if there is a way to force ACPI assign virtual interrupts a similar way.