powerpc: Change the doorbell IPI calling convention
Change the doorbell callers to know about their msgsnd addressing, rather than have them set a per-cpu target data tag at boot that gets sent to the cause_ipi functions. The data is only used for doorbell IPI functions, no other IPI types, so it makes sense to keep that detail local to doorbell. Have the platform code understand doorbell IPIs, rather than the interrupt controller code understand them. Platform code can look at capabilities it has available and decide which to use. Signed-off-by: Nicholas Piggin <npiggin@gmail.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
This commit is contained in:

committed by
Michael Ellerman

parent
9b7ff0c658
commit
b866cc2199
@@ -834,15 +834,15 @@ static void xive_irq_free_data(unsigned int virq)
|
||||
|
||||
#ifdef CONFIG_SMP
|
||||
|
||||
static void xive_cause_ipi(int cpu, unsigned long msg)
|
||||
static void xive_cause_ipi(int cpu)
|
||||
{
|
||||
struct xive_cpu *xc;
|
||||
struct xive_irq_data *xd;
|
||||
|
||||
xc = per_cpu(xive_cpu, cpu);
|
||||
|
||||
DBG_VERBOSE("IPI msg#%ld CPU %d -> %d (HW IRQ 0x%x)\n",
|
||||
msg, smp_processor_id(), cpu, xc->hw_ipi);
|
||||
DBG_VERBOSE("IPI CPU %d -> %d (HW IRQ 0x%x)\n",
|
||||
smp_processor_id(), cpu, xc->hw_ipi);
|
||||
|
||||
xd = &xc->ipi_data;
|
||||
if (WARN_ON(!xd->trig_mmio))
|
||||
|
Reference in New Issue
Block a user