[PATCH] irqchip/sifive-plic: use hartid as context_id in OF to fix AMP conflicts

[Thomas Gleixner]

On Tue, Oct 21 2025 at 09:14, Troy Mitchell wrote:
> On Mon, Oct 20, 2025 at 07:44:55PM +0200, Thomas Gleixner wrote:
>> On Mon, Oct 20 2025 at 11:49, Troy Mitchell wrote:
>> > In asymmetric multi-processing (AMP) scenarios, the original PLIC
>> > driver used the context loop index 'i' as context_id for OF (device
>> 
>> Which original driver and when did it stop to use the context loop index?
>> 
>> > tree) platforms. This caused multiple contexts from different harts
>> > (e.g., core0 and core4) to share the same enable_base, leading to
>> > conflicts when initializing the PLIC.
>> 
>> When did it stop to cause the issues? And if the issues have been
>> already resolved, what is this patch about?
> The issue still exists in the current driver.
> The PLIC driver for OF-based platforms assigns context_id = i inside
> the context loop, which assumes that all harts are numbered contiguously
> starting from 0.
>
> In AMP systems (e.g., when Linux boots from hart4 while hart0 runs another OS),
> this assumption breaks — multiple contexts from different clusters share the same
> enable_base(e.g., core4's enable_base = core0's enable_base), causing conflicts.
>
> This patch fixes the problem by assigning context_id based on the actual hartid,
> ensuring that each hart context maps to a unique enable region,
> while preserving behavior on SMP and UP systems.
>
> Does it make sense? I'll update my commit message in the next version.

Yes. Though this still applies:
 
>> # git grep 'This patch' Documentation/process/

Thanks,

        tglx