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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 10 Dec 2020 18:20:46 -0500
To:     Thomas Gleixner <>,
        LKML <>
Cc:     Peter Zijlstra <>,
        Marc Zyngier <>, Juergen Gross <>,
        Stefano Stabellini <>,,
        "James E.J. Bottomley" <>,
        Helge Deller <>,
        afzal mohammed <>,, Russell King <>,,
        Mark Rutland <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Christian Borntraeger <>,
        Heiko Carstens <>,,
        Jani Nikula <>,
        Joonas Lahtinen <>,
        Rodrigo Vivi <>,
        David Airlie <>,
        Daniel Vetter <>,
        Pankaj Bharadiya <>,
        Chris Wilson <>,
        Wambui Karuga <>,,,
        Tvrtko Ursulin <>,
        Linus Walleij <>,, Lee Jones <>,
        Jon Mason <>,
        Dave Jiang <>,
        Allen Hubbe <>,,
        Lorenzo Pieralisi <>,
        Rob Herring <>,
        Bjorn Helgaas <>,
        Michal Simek <>,,
        Karthikeyan Mitran <>,
        Hou Zhiqiang <>,
        Tariq Toukan <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,,, Saeed Mahameed <>,
        Leon Romanovsky <>
Subject: Re: [patch 27/30] xen/events: Only force affinity mask for percpu

On 12/10/20 2:26 PM, Thomas Gleixner wrote:
> All event channel setups bind the interrupt on CPU0 or the target CPU for
> percpu interrupts and overwrite the affinity mask with the corresponding
> cpumask. That does not make sense.
> The XEN implementation of irqchip::irq_set_affinity() already picks a
> single target CPU out of the affinity mask and the actual target is stored
> in the effective CPU mask, so destroying the user chosen affinity mask
> which might contain more than one CPU is wrong.
> Change the implementation so that the channel is bound to CPU0 at the XEN
> level and leave the affinity mask alone. At startup of the interrupt
> affinity will be assigned out of the affinity mask and the XEN binding will
> be updated. 

If that's the case then I wonder whether we need this call at all and instead bind at startup time.


> Only keep the enforcement for real percpu interrupts.

Powered by blists - more mailing lists