lkml.org 
[lkml]   [2014]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: x86: Inconsistent xAPIC synchronization in arch_irq_work_raise?

* Peter Zijlstra <peterz@infradead.org> wrote:

> On Tue, Jan 21, 2014 at 02:02:06PM +0100, Jan Kiszka wrote:
> > Hi all,
> >
> > while trying to plug a race in the CPU hotplug code on xAPIC systems, I
> > was analyzing IPI transmission patterns. The handlers in
> > arch/x86/include/asm/ipi.h first wait for ICR, then send. In contrast,
> > arch_irq_work_raise sends the self-IPI directly and then waits. This
> > looks inconsistent. Is it intended?
> >
> > BTW, the races are in wakeup_secondary_cpu_via_init and
> > wakeup_secondary_cpu_via_nmi (lacking IRQ disable around ICR accesses).
> > There we also send first, then wait for completion. But I guess that is
> > due to the code originally only being used during boot. Will send fixes
> > for those once the sync pattern is clear to me.
>
> Could be I had no clue what I was doing and copy/pasted the code until
> it compiled and ran.
>
> In fact, I've got no clue what an ICR is.

APIC ICR = Interrupt Command Register - this is the MMIO-mapped
register of the local APIC that (when written to) triggers the sending
of IPIs and (when read from) shows the status how the IPI is going or
whether a new IPI can be sent.

( Not to be confused with the APIC timer ICR, which is 'Initial Count
Register' and does something entirely different. )

Thanks,

Ingo


\
 
 \ /
  Last update: 2014-01-21 16:01    [W:0.150 / U:0.688 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site