From: Birger Koblitz <git@birger-koblitz.de>
To: Sander Vanheule <sander@svanheule.net>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Marc Zyngier <maz@kernel.org>,
Aleksander Jan Bajkowski <olek2@wp.pl>,
Hauke Mehrtens <hauke@hauke-m.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: smp-mt: enable all hardware interrupts on second VPE
Date: Sat, 9 Jul 2022 18:11:41 +0200 [thread overview]
Message-ID: <ea64c33f-9fc5-7c24-a101-da5d605863e1@birger-koblitz.de> (raw)
In-Reply-To: <468a2c8578d099eef0e0106fe273f73f5d70ef94.camel@svanheule.net>
Hi,
On 7/7/22 17:12, Sander Vanheule wrote:
> On Thu, 2022-07-07 at 16:39 +0200, Thomas Bogendoerfer wrote:
>> On Thu, Jul 07, 2022 at 02:57:15PM +0200, Martin Blumenstingl wrote:
>> IMHO there is the problem, irq-mips-cpu.c can only do CPU irq operations
>> on the same CPU. I've checked MIPS MT specs and it's possible do
>> modify CP0 registers between VPEs. Using that needs changes in
>> irq-mips-cpu.c. But mabye that's not woth the effort as probably
>> all SMP cabable platforms have some multi processort capable
>> interrupt controller implemented.
Not sure I can be of much help. That the patch works on the RTL SoCs is
mostly empirical and was found in the vendor code.
My understanding from the MIPS documentation is that it is not specified
what happens when a multi VPE capable IRQ controller triggers CPU
interrupts: if multiple VPEs are possible targets, then it is not
defined whether one of them gets them (and which one), multiple, or all.
So trying to control what happens between VPEs is probably SoC-dependent
functionality.
Cheers,
Birger
next prev parent reply other threads:[~2022-07-09 16:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 19:07 [PATCH] MIPS: smp-mt: enable all hardware interrupts on second VPE Aleksander Jan Bajkowski
2022-07-03 18:15 ` Sander Vanheule
2022-07-06 7:05 ` Marc Zyngier
2022-07-06 8:19 ` Thomas Bogendoerfer
2022-07-06 9:53 ` Marc Zyngier
2022-07-07 9:57 ` Thomas Bogendoerfer
2022-07-06 9:56 ` Martin Blumenstingl
2022-07-07 10:06 ` Thomas Bogendoerfer
2022-07-07 12:57 ` Martin Blumenstingl
2022-07-07 14:39 ` Thomas Bogendoerfer
2022-07-07 15:12 ` Sander Vanheule
2022-07-09 16:11 ` Birger Koblitz [this message]
2022-07-28 15:50 ` Martin Blumenstingl
2022-08-01 15:25 ` Thomas Bogendoerfer
2022-08-01 16:02 ` Sander Vanheule
2022-08-02 7:15 ` Birger Koblitz
2022-09-10 10:53 ` Aleksander Bajkowski
2022-09-12 14:02 ` Thomas Bogendoerfer
2022-07-05 10:35 ` Thomas Bogendoerfer
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=ea64c33f-9fc5-7c24-a101-da5d605863e1@birger-koblitz.de \
--to=git@birger-koblitz.de \
--cc=hauke@hauke-m.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=maz@kernel.org \
--cc=olek2@wp.pl \
--cc=sander@svanheule.net \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).