[PATCH 2/2] irqchip: nvic: Use GENERIC_IRQ_MULTI_HANDLER

Ard Biesheuvel ardb at kernel.org
Thu Dec 2 03:05:48 PST 2021


On Thu, 2 Dec 2021 at 10:45, Arnd Bergmann <arnd at arndb.de> wrote:
>
> On Thu, Dec 2, 2021 at 10:33 AM Vladimir Murzin <vladimir.murzin at arm.com> wrote:
> >
> > On 12/2/21 9:23 AM, Arnd Bergmann wrote:
> > > On Thu, Dec 2, 2021 at 9:35 AM Ard Biesheuvel <ardb at kernel.org> wrote:
> > >>
> > >> It seems trivial enough to add that for v7m as well, so I will include
> > >> a patch for it in my v3. But I won't be able to test it, though.
> > >
> > > Ok, perfect. Adding Jesse to Cc, they are in the process of adding another
> > > Cortex-M based platform and should be able to test this by merging in your
> > > changes from [1] after you have uploaded the latest version.
> >
> > I'm happy to test it as well. I'm wondering if there are specific scenarios
> > (or maybe some tests) to consider?
>
> If the IRQ stacks fail in some way, it most likely won't boot at all, so as long
> as you can get into user space, I'd be 99% confident that it's good.
>
> For the MMU based platforms, the series lets us detect stack overflows
> when either the per-thread stack or the IRQ stack runs into an unmapped
> vmalloc page, and there are some unit tests that exercise this.
> I don't think you can do this with the MPU though, and certainly not when
> the MPU is disabled.
>

Latest version of the code is here, if anyone wants to test it:
https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=arm-up-ti-in-task-v3

Once Mr. Robot confirms that nothing is broken, I'll send it out to the ML.

-- 
Ard.



More information about the linux-arm-kernel mailing list