From: Takayoshi Kochi <kochi@hpc.bs1.fc.nec.co.jp>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] skip _PRT entry for non-existent IOSAPICs
Date: Fri, 17 Jan 2003 06:41:29 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805710@msgid-missing> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 503 bytes --]
Hi,
On some machines that support I/O hot-plugging,
it happens that after boottime one or more IO SAPICs appear
after hot-plug event. Even in that case, ACPI _PRT entries
can exist for devices behind those IO SAPICs at boottime
for future use.
Currently iosapic.c will give up parsing _PRT entries
once one of them hits such a non-existent IO SAPIC.
This patch fixes the problem on 2.5 ia64 bk tree.
For 2.4, we don't have this problem now.
Thanks,
---
Takayoshi Kochi <kochi@hpc.bs1.fc.nec.co.jp>
[-- Attachment #2: iosapic.c.diff --]
[-- Type: Text/Plain, Size: 364 bytes --]
--- ia64-2.5/arch/ia64/kernel/iosapic.c Fri Dec 27 16:27:23 2002
+++ ia64-2.5.mod/arch/ia64/kernel/iosapic.c Fri Jan 17 15:31:50 2003
@@ -752,7 +752,7 @@
if (index < 0) {
printk(KERN_WARNING"IOSAPIC: GSI 0x%x has no IOSAPIC!\n", gsi);
- return;
+ continue;
}
addr = iosapic_lists[index].addr;
gsi_base = iosapic_lists[index].gsi_base;
reply other threads:[~2003-01-17 6:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590709805710@msgid-missing \
--to=kochi@hpc.bs1.fc.nec.co.jp \
--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