Re: [RFC PATCH 2/2] irqchip: irq-ti-sci-inta: Introduce IRQ affinity support

[Marc Zyngier <maz@kernel.org>]

On Fri, 27 Jan 2023 17:53:55 +0000,
"Raghavendra, Vignesh" <vigneshr@ti.com> wrote:
>

[...]

> >> @@ -504,11 +509,45 @@ static void ti_sci_inta_ack_irq(struct irq_data *data)
> >>  		ti_sci_inta_manage_event(data, VINT_STATUS_OFFSET);
> >>  }
> >>  
> >> +#ifdef CONFIG_SMP
> >> +static int ti_sci_inta_set_affinity(struct irq_data *d,
> >> +				    const struct cpumask *mask_val, bool force)
> >> +{
> >> +	struct ti_sci_inta_event_desc *event_desc;
> >> +	struct ti_sci_inta_vint_desc *vint_desc;
> >> +	struct irq_data *parent_irq_data;
> >> +
> >> +	if (cpumask_equal(irq_data_get_effective_affinity_mask(d), mask_val))
> >> +		return 0;
> >> +
> >> +	event_desc = irq_data_get_irq_chip_data(d);
> >> +	if (event_desc) {
> >> +		vint_desc = to_vint_desc(event_desc, event_desc->vint_bit);
> >> +
> >> +		/*
> >> +		 * Cannot set affinity if there is more than one event
> >> +		 * mapped to same VINT
> >> +		 */
> >> +		if (bitmap_weight(vint_desc->event_map, MAX_EVENTS_PER_VINT) > 1)
> >> +			return -EINVAL;
> >> +
> >> +		vint_desc->affinity_managed = true;
> >> +
> >> +		irq_data_update_effective_affinity(d, mask_val);
> >> +		parent_irq_data = irq_get_irq_data(vint_desc->parent_virq);
> >> +		if (parent_irq_data->chip->irq_set_affinity)
> >> +			return parent_irq_data->chip->irq_set_affinity(parent_irq_data, mask_val, force);
> > 
> > This looks completely wrong.
> > 
> > You still have a chained irqchip on all paths, and have to do some
> > horrible probing to work out:
> > 
> > - which parent interrupt this is
> > 
> > - how many interrupts are connected to it
> > 
> > And then the fun begins:
> > 
> > - You have one interrupt that is standalone, so its affinity can be
> >   moved
> > 
> > - An unrelated driver gets probed, and one of its interrupts gets
> >   lumped together with the one above
> > 
> > - Now it cannot be moved anymore, and userspace complains
> > 
> > The rule is very simple: chained irqchip, no affinity management.
> > Either you reserve a poll of direct interrupts that have affinity
> 
> This is what I am trying to accomplish, that is, reserve a pool of
> direct interrupts that can be used by certain drivers that require IRQ
> steering for performance. But I don't see a way to indicate from client
> drivers to allocate from this reserved pool (there is no hint in
> request_irq() call that ends up in .irq_request_resources() that I can use)
> 
> I can try and virtually split INTA into two irqchips perhaps, with one
> part modeled as chained irqchip and other as stacked for the reserved
> pool (and would have to spawn of two child msi-domains I presume).
> But, there is only one DT node for this irqchip and thus clients cannot
> request IRQ for reserved pool.

I don't see why DT should be aware of this. You only need to decide at
allocation time which one is where, and plug it at the right level.

And you probably only need *one* chained interrupt that muxes
everything that cannot be allocated direct path.

> Wondering if you have any pointers here?

I don't. But this shouldn't be too hard to bolt onto the existing
framework.

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel