linux-kernel - Re: [PATCH v14 3/8] genirq: Add mechanism to multiplex a single HW IPI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAK9=C2Vnp9gTqX7AHxqCaVzVx1qGGRE0fCG1uxQUnh6n0dSm-g@mail.gmail.com>
Date:   Fri, 2 Dec 2022 10:34:00 +0530
From:   Anup Patel <apatel@...tanamicro.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Palmer Dabbelt <palmer@...belt.com>,
        Paul Walmsley <paul.walmsley@...ive.com>,
        Marc Zyngier <maz@...nel.org>,
        Daniel Lezcano <daniel.lezcano@...aro.org>,
        Atish Patra <atishp@...shpatra.org>,
        Alistair Francis <Alistair.Francis@....com>,
        Anup Patel <anup@...infault.org>,
        linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v14 3/8] genirq: Add mechanism to multiplex a single HW IPI

On Fri, Dec 2, 2022 at 7:39 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>
> Anup!
>
> On Thu, Dec 01 2022 at 23:30, Anup Patel wrote:
> > On Thu, Dec 1, 2022 at 10:50 PM Thomas Gleixner <tglx@...utronix.de> wrote:
> >> > irqchip driver and it is shared by various RISC-V irqchip drivers.
> >>
> >> Sure, but now we have two copies of this. One in the Apple AIC and one
> >> here. The obvious thing to do is:
> >>
> >>    1) Provide generic infrastructure
> >>
> >>    2) Convert AIC to use it
> >
> > Mark Z already has a converted version of AIC driver.
> > https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=irq/ipi-mux
>
> You are submitting generic infrastructure which is supposed to go
> through the relevant maintainer tree and not be funneled through some
> riscv branch.
>
> So obviously this very maintainer asks the predictable question and also
> wants to see the Acked/Tested-by of the folks who maintain apple-AIC.

Not CCing apple-AIC maintainers was purely accidental.

Actually, I had started off ipi-mux with the intent to share across
RISC-V irqchip drivers. Only in recent patch revisions (based on
suggestion from Marc Z), I tried to converge and make it useful
for apple-AIC driver as well. Unfortunately, I don't have apple HW
for testing this so I was hoping someone will help.

Thanks to Marc Z, we now have a patch for apple-AIC driver as well.

>
> How is that supposed to work without integrating this patch into your
> series and without having the apple-AIC folks on cc?

Okay, I will include the apple-AIC patch from Marc Z in the next revision
and add apple-AIC folks in CC.

>
> You did not start kernel development as of yesterday, right?
>
> Thanks,
>
>         tglx

Regards,
Anup