linux-kernel - Re: [PATCH] irqchip/gic: Convert to handle_strict_flow

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: <875yvmub3x.mognet@arm.com>
Date:   Mon, 30 Aug 2021 17:54:26 +0100
From:   Valentin Schneider <valentin.schneider@....com>
To:     Marc Zyngier <maz@...nel.org>
Cc:     Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] irqchip/gic: Convert to handle_strict_flow_irq()

On 15/08/21 07:54, Marc Zyngier wrote:
> In order to restore -next into a working state, I'm temporarily
> dropping this series. Hopefully, we can sort this out before the merge
> window and reinstate it.
>

So what I thought would be a small weekend job turned to be a bit more
involved...

- The throughput improvement with v4 is half of what it was on v3. I
  rebased v3 on the last tip/irq/core and this also took a hit, I'm digging
  into it.
- TX1 is being an absolute PITA to work with, I can't seem to boot anything
  else than the distro kernel ATM (grub commits seppuku).
- Last but not least, I'll soon be AWOL for 3 weeks, a good chunk of it
  involving sitting atop a mountain without electricity. So even if I can
  magically fix all of the above say tomorrow, I'd rather be available to
  ~watch~ handle any unforeseen fireworks.

Hopefully I'll catch the next revision :)

> Thanks,
>
>       M.
>
> --
> Without deviation from the norm, progress is not possible.