eee45687e9
in all the places/cases IPI messages will be generated, at least be consistent with how the call_data pointer is assigned and cleared (ie, all done inside the spinlock. Ensure that its NULL before continuing, just to try and identify situations where things are going horribly wrong. |
||
|---|---|---|
| .. | ||
| clock.c | ||
| exception.s | ||
| locore.s | ||
| mp_machdep.c | ||
| mptable.c | ||
| pmap.c | ||
| xen_clock_util.c | ||
| xen_machdep.c | ||
| xen_rtc.c | ||