From: Andi Kleen <ak@suse.de>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: acpi-devel@lists.sourceforge.net, len.brown@intel.com,
davidm@hpl.hp.com, jun.nakajima@intel.com,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ACPI PCI IRQ routing rework
Date: Mon, 17 May 2004 17:41:19 +0200 [thread overview]
Message-ID: <20040517174119.64d134b0.ak@suse.de> (raw)
In-Reply-To: <200405151120.45753.bjorn.helgaas@hp.com>
On Sat, 15 May 2004 11:20:45 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> I think it's better to pull all the PRT knowledge out of the arch
> code and do the IRQ allocation and IO-APIC programming at the time
> of pci_enable_device(). That reduces IRQ usage (since many PRT
> entries are never used) and is a step toward allowing the addition
> of new root bridges and PRTs at run-time.
I like this change very much. It should make PRT misrouting problems
easier to debug, because the system will be already up and running
then (at least with modular drivers).
Also things that are not needed are not configured and that reduces
the potential for bugs.
-Andi
next prev parent reply other threads:[~2004-05-17 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 17:20 [PATCH] ACPI PCI IRQ routing rework Bjorn Helgaas
[not found] ` <200405151120.45753.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-05-15 20:23 ` Bjorn Helgaas
2004-05-17 10:09 ` Sourav Sen
2004-05-17 15:41 ` Andi Kleen [this message]
[not found] <A11077E28200D51182EA00D0B77552530E8A8522@xin02.india.hp.com>
2004-05-17 14:57 ` Bjorn Helgaas
[not found] ` <200405170857.55814.bjorn.helgaas-VXdhtT5mjnY@public.gmane.org>
2004-05-18 4:39 ` Sourav Sen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040517174119.64d134b0.ak@suse.de \
--to=ak@suse.de \
--cc=acpi-devel@lists.sourceforge.net \
--cc=bjorn.helgaas@hp.com \
--cc=davidm@hpl.hp.com \
--cc=jun.nakajima@intel.com \
--cc=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox