* Chris J Arges <chris.j.ar...@canonical.com> wrote:
> > diff --git a/arch/x86/kernel/apic/vector.c b/arch/x86/kernel/apic/vector.c
> > index 6cedd7914581..79d6de6fdf0a 100644
> > --- a/arch/x86/kernel/apic/vector.c
> > +++ b/arch/x86/kernel/apic/vector.c
> > @@ -144,6 +144,8 @@ __assign_irq_vector(int irq, struct irq_cfg *cfg, const
> > struct cpumask *mask)
> > cfg->move_in_progress =
> > cpumask_intersects(cfg->old_domain, cpu_online_mask);
> > cpumask_and(cfg->domain, cfg->domain, tmp_mask);
> > + if (cfg->move_in_progress)
> > + dump_stack();
> > break;
> > }
> >
> >
>
> Should I add the dump_stack() to the 'new-domain move' area line
> ~184 since that's the path I seem to be triggering?
Yeah, please do, that's what I wanted to mark.
My guess is that it will show a stack dump to within set_affinity().
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
