On Tue, Aug 28, 2018 at 1:58 AM, Marc Zyngier wrote:
> On Tue, 28 Aug 2018 05:53:26 +0100,
> Jia He wrote:
>>
>> In commit fe8e93504ce8 ("irqchip/gic-v3-its: Use full range of LPIs"),
>> it removes the cap for lpi_id_bits. But it will cause more pointless
>> memory footprint.
>>
>> There is a WAR
On 8/28/2018 4:58 PM, Marc Zyngier Wrote:
> On Tue, 28 Aug 2018 05:53:26 +0100,
> Jia He wrote:
>>
>> In commit fe8e93504ce8 ("irqchip/gic-v3-its: Use full range of LPIs"),
>> it removes the cap for lpi_id_bits. But it will cause more pointless
>> memory footprint.
>>
>> There is a WARN_ON when
On Tue, 28 Aug 2018 05:53:26 +0100,
Jia He wrote:
>
> In commit fe8e93504ce8 ("irqchip/gic-v3-its: Use full range of LPIs"),
> it removes the cap for lpi_id_bits. But it will cause more pointless
> memory footprint.
>
> There is a WARN_ON when my QDF2400 server boots up (pagesize is 4k)
> ==
In commit fe8e93504ce8 ("irqchip/gic-v3-its: Use full range of LPIs"),
it removes the cap for lpi_id_bits. But it will cause more pointless
memory footprint.
There is a WARN_ON when my QDF2400 server boots up (pagesize is 4k)
begin===
[0.00] GICv3: GIC: Using split
4 matches
Mail list logo