On Thu, 24 Sep 2015, Qais Yousef wrote:
> The CPUs we want to send the IPI to are not Linux CPUs only. My use case is
> about sending IPI to audio coprocessor.
> So "dest" doesn't have to be part of Linux online CPUs, hence we need to
> specify it so that the underlying controller will know how to
On 09/23/2015 05:50 PM, Jiang Liu wrote:
On 2015/9/23 22:49, Qais Yousef wrote:
+/**
+ * irq_reserve_ipi() - setup an IPI to destination cpumask
+ * @domain: IPI domain
+ * @dest: cpumask of cpus to receive the IPI
+ * @devid: devid that requested the reservation
+ *
+ * Allocate a virq that
On 2015/9/23 22:49, Qais Yousef wrote:
> Add a generic mechanism to dynamically allocate an IPI.
>
> With this change the user can call irq_reserve_ipi() to dynamically allocate
> an
> IPI and use the associate virq to send one to 1 or more cpus.
>
> No irq_get_irq_hwcfg() as I hope we can provi
Add a generic mechanism to dynamically allocate an IPI.
With this change the user can call irq_reserve_ipi() to dynamically allocate an
IPI and use the associate virq to send one to 1 or more cpus.
No irq_get_irq_hwcfg() as I hope we can provide an implementation without
hardware specific part. H
4 matches
Mail list logo
