From: Ralf Baechle <ralf@linux-mips.org>
To: Raghu Gandham <raghu@mips.com>
Cc: linux-mips@linux-mips.org, chris@mips.com
Subject: Re: [PATCH] Due to some broken bitfiles, we can't trust IntCtl
Date: Fri, 10 Jul 2009 17:13:58 +0100 [thread overview]
Message-ID: <20090710161358.GC1288@linux-mips.org> (raw)
In-Reply-To: <20090710084942.25804.864.stgit@linux-raghu>
On Fri, Jul 10, 2009 at 01:49:43AM -0700, Raghu Gandham wrote:
> diff --git a/arch/mips/include/asm/irq.h b/arch/mips/include/asm/irq.h
> index 09b08d0..ca0b5ed 100644
> --- a/arch/mips/include/asm/irq.h
> +++ b/arch/mips/include/asm/irq.h
> @@ -158,6 +158,7 @@ extern void free_irqno(unsigned int irq);
> * IE7. Since R2 their number has to be read from the c0_intctl register.
> */
> #define CP0_LEGACY_COMPARE_IRQ 7
> +#define CP0_LEGACY_PERFCNT_IRQ 7
>
> extern int cp0_compare_irq;
> extern int cp0_perfcount_irq;
> diff --git a/arch/mips/kernel/traps.c b/arch/mips/kernel/traps.c
> index 08f1edf..0b6e328 100644
> --- a/arch/mips/kernel/traps.c
> +++ b/arch/mips/kernel/traps.c
> @@ -1538,7 +1538,11 @@ void __cpuinit per_cpu_trap_init(void)
> */
> if (cpu_has_mips_r2) {
> cp0_compare_irq = (read_c0_intctl() >> 29) & 7;
> + if (!cp0_compare_irq)
> + cp0_compare_irq = CP0_LEGACY_COMPARE_IRQ;
> cp0_perfcount_irq = (read_c0_intctl() >> 26) & 7;
> + if (!cp0_perfcount_irq)
> + cp0_perfcount_irq = CP0_LEGACY_PERFCNT_IRQ;
> if (cp0_perfcount_irq == cp0_compare_irq)
> cp0_perfcount_irq = -1;
> } else {
Is there still any point in applying this patch? I thought only a bunch
of early bitfiles were affected but it was never actually taped out?
Ralf
next prev parent reply other threads:[~2009-07-10 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 8:49 [PATCH] Due to some broken bitfiles, we can't trust IntCtl Raghu Gandham
2009-07-10 16:13 ` Ralf Baechle [this message]
2009-07-10 17:53 ` Gandham, Raghu
2009-07-10 17:53 ` Gandham, Raghu
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=20090710161358.GC1288@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=chris@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=raghu@mips.com \
/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.