From: Ingo Molnar <mingo@kernel.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Fix XT-PIC-XT-PIC in /proc/interrupts
Date: Mon, 27 Oct 2014 13:44:09 +0100 [thread overview]
Message-ID: <20141027124409.GA22947@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1410271207230.3413@eddie.linux-mips.org>
* Maciej W. Rozycki <macro@linux-mips.org> wrote:
> On Mon, 27 Oct 2014, Ingo Molnar wrote:
>
> > What's the effect of this change on the output for non-8259A irq
> > controllers?
>
> Good question, I didn't expect any other IRQ controller to be used for
> ISA interrupts (the APIC is handled elsewhere). I have checked the
> sources and the only other controller that can be used for `legacy_pic'
> is `dummy_irq_chip' (cf. `default_legacy_pic' vs `null_legacy_pic' in
> arch/x86/kernel/i8259.c). That affects `init_ISA_irqs' only (the other
> place, `make_8259A_irq', has a reference to `i8259A_chip' hardcoded).
>
> In this case the output would change from "dummy-dummy" to "dummy",
> which IMHO has just as much value as the change from "XT-PIC-XT-PIC" to
> "XT-PIC". However I don't think you'd be able to request such IRQs so
> they will never show up in /proc/interrupts, making this observation
> largely irrelevant. If you think I may be wrong here, then can you
> please find such a system and try this change with it (or can someone
> else reading this make this check for me by any chance)? Unfortunately
> all x86 hardware I have does have an 8259A pair.
>
> Also please note that both places explicitly refer to the name of the
> IRQ chip being installed as the name of the handler as well, with
> `i8259A_chip.name' and `chip->name' respectively, this is hardcoded.
> So no matter which chip is used there'll be a duplicate name in
> /proc/interrupts.
>
> Does this answer address your concern?
Yeah, it addresses it, I'll queue up your fix, thanks!
Ingo
next prev parent reply other threads:[~2014-10-27 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 16:06 [PATCH] x86: Fix XT-PIC-XT-PIC in /proc/interrupts Maciej W. Rozycki
2014-10-27 7:47 ` Ingo Molnar
2014-10-27 12:29 ` Maciej W. Rozycki
2014-10-27 12:44 ` Ingo Molnar [this message]
2014-10-28 11:13 ` [tip:x86/urgent] x86/irq: " tip-bot for Maciej W. Rozycki
2014-10-28 11:18 ` tip-bot for Maciej W. Rozycki
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=20141027124409.GA22947@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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