On 12/5/2019 6:17 PM, Marc Zyngier wrote:
Hi Gaurav,
On 2019-12-05 10:55, Gaurav Kohli wrote:
As per GIC specification, we can configure gic for more no of cpusWhich LPI region? We're talking about RDs, right... Or does LPI mean
then the available cpus in the soc, But this can cause mem abort
while iterating lpi region for non existent cpu as we don't map
something other than GIC LPIs for you?
Yes RDs only.
Yes, suppose gic is configured for 8 cpus but soc has only 4 cpus.redistrubutor region for non-existent cpu.Sorry, but I'm not sure I grasp your problem. Let me try and rephrase it:
To avoid this issue, put one more check of valid mpidr.
- Your GIC is configured for (let's say) 8 CPUs, and your SoC has only 4.
Then in this case gic_iterate will iterate till it get TYPER_LAST.
But as gic is configured for 8, So last bit sets in eight
redistributor regions only.
- As part of the probing, the driver iterates on the RD regions and explodes
 because something isn't mapped?
That'd be a grave bug, but I believe the issue is somewhere else.
There are 4 cpus present, that's why we have mapped 4 redistributor
only, but during probe below function keeps iterating and give mem
abort for 5th cpu.
static void gic_update_vlpi_properties(void)
{
gic_iterate_rdists(__gic_update_vlpi_properties);
}
We can solve this problem by mapping all eight redistributor in dt,
but ideally code should also able to handle this and we can avoid
mappin?