From: sashiko-bot@kernel.org
To: "Caleb James DeLisle" <cjd@cjdns.fr>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] mips: econet: add multi-vpe capability to EN751221
Date: Tue, 28 Jul 2026 19:06:21 +0000 [thread overview]
Message-ID: <20260728190621.CCD601F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728184959.102441-2-cjd@cjdns.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Unconditionally masking hardware interrupts in en751221_init_secondary breaks the secondary CPU's timer if the system boots with VEIC disabled.
--
--- Patch [1]: [PATCH 1/2] mips: econet: add multi-vpe capability to EN751221 ---
commit 29d4bfd90711d72516d1c7a3132dda2ae50742fc
Author: Caleb James DeLisle <cjd@cjdns.fr>
mips: econet: add multi-vpe capability to EN751221
This commit registers SMP_MT on startup and overrides init_secondary with
CPU interrupt unmasking required by the EN751221 VEIC intc hardware.
> diff --git a/arch/mips/econet/init.c b/arch/mips/econet/init.c
> --- a/arch/mips/econet/init.c
> +++ b/arch/mips/econet/init.c
[ ... ]
> +static void en751221_init_secondary(void)
> +{
> + write_c0_status((read_c0_status() & ~ST0_IM) |
> + (STATUSF_IP0 | STATUSF_IP1));
> +}
> +
> +static int __init en751221_register_vsmp_smp_ops(void)
> +{
> + if (!cpu_has_mipsmt)
> + return -ENODEV;
[Severity: High]
If the system boots with VEIC disabled (e.g., falling back to cascading mode),
will this break the secondary CPU's timer?
By registering these VEIC-specific SMP operations here without checking
cpu_has_veic, en751221_init_secondary() will execute on the secondary CPU.
Since en751221_init_secondary() clears ST0_IM unconditionally, it masks
hardware interrupts including the timer interrupt. Could this lead to
boot stalls or RCU hangs on non-VEIC setups?
> +
> + en75_smp_ops = vsmp_smp_ops;
> + en75_smp_ops.init_secondary = en751221_init_secondary;
> + register_smp_ops(&en75_smp_ops);
> + return 0;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728184959.102441-1-cjd@cjdns.fr?part=1
next prev parent reply other threads:[~2026-07-28 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 18:49 [PATCH 0/2] mips: econet: add multi-vpe capability to EN751221 Caleb James DeLisle
2026-07-28 18:49 ` [PATCH 1/2] " Caleb James DeLisle
2026-07-28 19:06 ` sashiko-bot [this message]
2026-07-28 19:36 ` Caleb James DeLisle
2026-07-28 18:49 ` [PATCH 2/2] mips: dts: econet: Describe dual-VPE 34Kc processor Caleb James DeLisle
2026-07-28 19:09 ` sashiko-bot
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=20260728190621.CCD601F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=cjd@cjdns.fr \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.