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] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 31 Oct 2020 03:59:50 +0100
From:   Thomas Gleixner <>
To:     Dongjiu Geng <>,
        Marc Zyngier <>
Cc:     Jason Cooper <>,
Subject: Re: Using fixed LPI number for some Device ID

On Sat, Oct 31 2020 at 10:19, Dongjiu Geng wrote:
>  Hi Marc,
>     Sorry to disturb you, Currently the LPI number is not fixed for
>  the device. The LPI number is dynamically allocated start from 8092.
>  For two OS which shares the ITS, One OS needs to configure the device
>  interrupt required by another OS, and the other OS uses a fixed
>  interrupt ID to respond the interrupt. Therefore, the LPI IRQ number
>  of the device needed be fixed. I want to upstream this feature that
>  allocate fixed LPI number for the device that is specified through
>  the DTS. What is your meaning?  Thanks

What's the purpose of resending the same thing within less than 24
hours? Do you really expect maintainers to be available 24/7 and being
able to respond within less than a day?

Powered by blists - more mailing lists