From: "H. Peter Anvin" <hpa@zytor.com>
To: "K. Y. Srinivasan" <kys@microsoft.com>,
x86@kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, jasowang@redhat.com,
tglx@linutronix.de, JBeulich@suse.com, bp@alien8.de
Cc: Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/1] X86: Probe for PIC and set legacy_pic appropriately
Date: Fri, 11 Apr 2014 15:35:43 -0700 [thread overview]
Message-ID: <53486E3F.1020307@zytor.com> (raw)
In-Reply-To: <1397257344-3035-1-git-send-email-kys@microsoft.com>
On 04/11/2014 04:02 PM, K. Y. Srinivasan wrote:
>
> diff --git a/arch/x86/kernel/i8259.c b/arch/x86/kernel/i8259.c
> index 2e977b5..0a57a19 100644
> --- a/arch/x86/kernel/i8259.c
> +++ b/arch/x86/kernel/i8259.c
> @@ -299,11 +299,22 @@ static void unmask_8259A(void)
> static void init_8259A(int auto_eoi)
> {
> unsigned long flags;
> + unsigned char probe_val = 0xfb;
>
> i8259A_auto_eoi = auto_eoi;
>
> raw_spin_lock_irqsave(&i8259A_lock, flags);
>
> + /* Check to see if we have a PIC */
> + outb(probe_val, PIC_MASTER_IMR);
> + probe_val = inb(PIC_MASTER_IMR);
> + if (probe_val == 0xff) {
> + printk(KERN_INFO "Using NULL legacy PIC\n");
> + legacy_pic = &null_legacy_pic;
> + raw_spin_unlock_irqrestore(&i8259A_lock, flags);
> + return;
> + }
> +
> outb(0xff, PIC_MASTER_IMR); /* mask all of 8259A-1 */
> outb(0xff, PIC_SLAVE_IMR); /* mask all of 8259A-2 */
>
I think it is important to document what this actually means here. 0xfb
is "mask all except for the cascade."
Arguably, we should do this after masking the slave PIC.
On a whole other subject... the whole __byte() logic is a just plain
horrific piece of crap. Clearly whomever wrote it had never heard of a
union.
I'm still horrifically confused, though, why we mask IRQ 2 (the cascade
interrupt) in i8259.c, but we explicitly do *not* mask IRQ 2 in
boot/pm.c (nor in the assembly code on which boot/pm.c was based.) In
fact, it looks like we never unmask it. I'm guessing that the masking
status of the cascade input simply doesn't matter.
At the very least, though, we shouldn't have 0xfb as a magic number, but
use ~(1U << PIC_CASCADE_IR).
-hpa
next prev parent reply other threads:[~2014-04-11 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 23:02 [PATCH 1/1] X86: Probe for PIC and set legacy_pic appropriately K. Y. Srinivasan
2014-04-11 22:35 ` H. Peter Anvin [this message]
2014-04-11 22:49 ` KY Srinivasan
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=53486E3F.1020307@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=apw@canonical.com \
--cc=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.