From: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Ungerer <gerg@linux-m68k.org>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: coldfire: Prevent spurious interrupts when masking IMR
Date: Tue, 4 Feb 2025 21:14:49 +0100 [thread overview]
Message-ID: <56cd8c0c-2cdf-47a5-8ee3-cb338acdc374@yoseli.org> (raw)
In-Reply-To: <CAMuHMdXkq57WjUPeg3kTsgi-YSw23qV-gK4gVxymOSKGGTDuQQ@mail.gmail.com>
Hi Geert,
On 04/02/2025 20:27, Geert Uytterhoeven wrote:
> Hi Jean-Michel,
>
> On Tue, 4 Feb 2025 at 19:38, Jean-Michel Hautbois
> <jeanmichel.hautbois@yoseli.org> wrote:
>> The ColdFire interrupt controller can generate spurious interrupts if an
>> interrupt source is masked in the IMR while the CPU interrupt priority
>> mask (SR[I]) is set lower than the interrupt level.
>>
>> The reference manual states:
>>
>> To avoid this situation for interrupts sources with levels 1-6, first
>> write a higher level interrupt mask to the status register, before
>> setting the mask in the IMR or the module’s interrupt mask register.
>> After the mask is set, return the interrupt mask in the status register
>> to its previous value.
>>
>> It can be tested like this:
>> - Prepare a iperf3 server on the coldfire target (iperf3 -s -D)
>> - Start a high priority cyclictest:
>> cyclictest --secaligned -m -p 99 -i 2500 -q
>> - Start iperf3 -c $COLDFIRE_IP -t 0
>>
>> After a few seconds the dmesg may display:
>> [ 84.784301] irq 24, desc: dbc502da, depth: 1, count: 0, unhandled: 0
>> [ 84.784455] ->handle_irq(): 0ba0aca3, handle_bad_irq+0x0/0x1e0
>> [ 84.784610] ->irq_data.chip(): c6779d4f, 0x41652544
>> [ 84.784719] ->action(): 00000000
>> [ 84.784770] unexpected IRQ trap at vector 18
>>
>> With this patch, I never saw it in a few hours testing.
>>
>> Signed-off-by: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
>
> Thanks for your patch!
>
>> --- a/arch/m68k/coldfire/intc-simr.c
>> +++ b/arch/m68k/coldfire/intc-simr.c
>> @@ -58,6 +58,14 @@ static inline unsigned int irq2ebit(unsigned int irq)
>>
>> #endif
>>
>> +static inline void intc_irq_setlevel(unsigned long level)
>> +{
>> + asm volatile ("move.w %0,%%sr"
>> + : /* no outputs */
>> + : "d" (0x2000 | ((level) << 8))
>> + : "memory");
>> +}
>> +
>> /*
>> * There maybe one, two or three interrupt control units, each has 64
>> * interrupts. If there is no second or third unit then MCFINTC1_* or
>> @@ -67,13 +75,17 @@ static inline unsigned int irq2ebit(unsigned int irq)
>> static void intc_irq_mask(struct irq_data *d)
>> {
>> unsigned int irq = d->irq - MCFINT_VECBASE;
>> + unsigned long flags = arch_local_save_flags();
>>
>> + intc_irq_setlevel(7);
>
> Can't all of the above just be replaced by
>
> unsigned long flags = arch_local_irq_save();
>
Thanks for reviewing.
You are right, it should be (very) similar...
Testing it, and if it works, I will send a v2.
Thanks !
JM
>> if (MCFINTC2_SIMR && (irq > 127))
>> __raw_writeb(irq - 128, MCFINTC2_SIMR);
>> else if (MCFINTC1_SIMR && (irq > 63))
>> __raw_writeb(irq - 64, MCFINTC1_SIMR);
>> else
>> __raw_writeb(irq, MCFINTC0_SIMR);
>> +
>> + arch_local_irq_restore(flags);
>> }
>>
>> static void intc_irq_unmask(struct irq_data *d)
>>
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2025-02-04 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 18:38 Jean-Michel Hautbois
2025-02-04 19:27 ` Geert Uytterhoeven
2025-02-04 20:14 ` Jean-Michel Hautbois [this message]
2025-02-04 20:17 ` Jean-Michel Hautbois
2025-02-05 7:07 ` Jean-Michel Hautbois
2025-02-05 8:14 ` Geert Uytterhoeven
2025-02-05 9:34 ` Jean-Michel Hautbois
2025-02-05 11:26 ` Jean-Michel Hautbois
2025-02-12 12:47 ` Greg Ungerer
2025-02-18 13:17 ` Jean-Michel Hautbois
2025-02-18 13:30 ` Greg Ungerer
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=56cd8c0c-2cdf-47a5-8ee3-cb338acdc374@yoseli.org \
--to=jeanmichel.hautbois@yoseli.org \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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®