From: Meelis Roos <mroos@linux.ee>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 2.6.35-rc* regression: ERROR: Unable to locate IOAPIC for GSI *
Date: Wed, 14 Jul 2010 14:43:31 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1007141441460.18009@math.ut.ee> (raw)
In-Reply-To: <AANLkTikYc5N5ihRBJI_n3yGfcRxjplxbYGtGzJZ1ufzc@mail.gmail.com>
> related commit:
>
> commit 9a0a91bb56d2915cdb8585717de38376ad20fef9
> Author: Eric W. Biederman <ebiederm@xmission.com>
> Date: Tue Mar 30 01:07:03 2010 -0700
>
> x86, acpi/irq: Teach acpi_get_override_irq to take a gsi not an isa_irq
>
> In perverse acpi implementations the isa irqs are not identity mapped
> to the first 16 gsi. Furthermore at least the extended interrupt
> resource capability may return gsi's and not isa irqs. So since
> what we get from acpi is a gsi teach acpi_get_overrride_irq to
> operate on a gsi instead of an isa_irq.
>
> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
> LKML-Reference: <1269936436-7039-2-git-send-email-ebiederm@xmission.com>
> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
[2c2df8418ac7908eec4558407b83f16739006c54] x86, acpi/irq: Introduce apci_isa_irq_to_gsi
This ise the commit that introduces the ERROR: lines in dmesg. Related
to the same irq mapping changes.
The right way to silence these error lines in dmesg is the change
proposed by hpa, about only trying to ouse ioapic whet we are in ioapic
mode?
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2010-07-14 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 13:53 Meelis Roos
2010-07-08 20:27 ` Yinghai Lu
2010-07-08 20:53 ` Yinghai Lu
2010-07-08 20:59 ` Eric W. Biederman
2010-07-08 21:08 ` Yinghai Lu
2010-07-14 11:43 ` Meelis Roos [this message]
2010-07-08 22:24 ` Meelis Roos
2010-07-09 7:26 ` Ingo Molnar
2010-07-09 10:02 ` Meelis Roos
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=alpine.SOC.1.00.1007141441460.18009@math.ut.ee \
--to=mroos@linux.ee \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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
all inboxes | Powered by JetHome®