On Fri, 26 Feb 2021 20:11:11 +0000,
Megha Dey <megha.dey@xxxxxxxxx> wrote:
>
> From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
>
> For devices which don't have a standard storage for MSI messages like the
> upcoming IMS (Interrupt Message Store) it's required to allocate storage
> space before allocating interrupts and after freeing them.
>
> This could be achieved with the existing callbacks, but that would be
> awkward because they operate on msi_alloc_info_t which is not uniform
> across architectures. Also these callbacks are invoked per interrupt but
> the allocation might have bulk requirements depending on the device.
>
> As such devices can operate on different architectures it is simpler to
> have separate callbacks which operate on struct device. The resulting
> storage information has to be stored in struct msi_desc so the underlying
> irq chip implementation can retrieve it for the relevant operations.
>
> Reviewed-by: Tony Luck <tony.luck@xxxxxxxxx>
> Signed-off-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
> Signed-off-by: Megha Dey <megha.dey@xxxxxxxxx>
> ---
> include/linux/msi.h | 8 ++++++++
> kernel/irq/msi.c | 11 +++++++++++
> 2 files changed, 19 insertions(+)
>
> diff --git a/include/linux/msi.h b/include/linux/msi.h
> index 46e879c..e915932 100644
> --- a/include/linux/msi.h
> +++ b/include/linux/msi.h
> @@ -323,6 +323,10 @@ struct msi_domain_info;
> * function.
> * @domain_free_irqs: Optional function to override the default free
> * function.
> + * @msi_alloc_store: Optional callback to allocate storage in a device
> + * specific non-standard MSI store
> + * @msi_alloc_free: Optional callback to free storage in a device
> + * specific non-standard MSI store
> *
> * @get_hwirq, @msi_init and @msi_free are callbacks used by
> * msi_create_irq_domain() and related interfaces
> @@ -372,6 +376,10 @@ struct msi_domain_ops {
> struct device *dev, int nvec);
> void (*domain_free_irqs)(struct irq_domain *domain,
> struct device *dev);
> + int (*msi_alloc_store)(struct irq_domain *domain,
> + struct device *dev, int nvec);
> + void (*msi_free_store)(struct irq_domain *domain,
> + struct device *dev);
> };
>
> /**
> diff --git a/kernel/irq/msi.c b/kernel/irq/msi.c
> index c54316d..047b59d 100644
> --- a/kernel/irq/msi.c
> +++ b/kernel/irq/msi.c
> @@ -434,6 +434,12 @@ int __msi_domain_alloc_irqs(struct irq_domain *domain, struct device *dev,
> if (ret)
> return ret;
>
> + if (ops->msi_alloc_store) {
> + ret = ops->msi_alloc_store(domain, dev, nvec);
What is supposed to happen if we get aliasing devices (similar to what
we have with devices behind a PCI bridge)?
The ITS code goes through all kind of hoops to try and detect this
case when sizing the translation tables (in the .prepare callback),
and I have the feeling that sizing the message store is analogous.
Or do we all have the warm fuzzy feeling that aliasing is a thing of
the past and that we can ignore this potential problem?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
