ee29074d3b
Don't piggy back the SMP receive signal code to do the context version change handling. Instead allocate another fixed PIL number for this asynchronous cross-call. We can't use smp_call_function() because this thing is invoked with interrupts disabled and a few spinlocks held. Also, fix smp_call_function_mask() to count "cpus" correctly. There is no guarentee that the local cpu is in the mask yet that is exactly what this code was assuming. Signed-off-by: David S. Miller <davem@davemloft.net>
29 lines
949 B
C
29 lines
949 B
C
/* $Id: pil.h,v 1.1 2002/01/23 11:27:36 davem Exp $ */
|
|
#ifndef _SPARC64_PIL_H
|
|
#define _SPARC64_PIL_H
|
|
|
|
/* To avoid some locking problems, we hard allocate certain PILs
|
|
* for SMP cross call messages that must do a etrap/rtrap.
|
|
*
|
|
* A cli() does not block the cross call delivery, so when SMP
|
|
* locking is an issue we reschedule the event into a PIL interrupt
|
|
* which is blocked by cli().
|
|
*
|
|
* In fact any XCALL which has to etrap/rtrap has a problem because
|
|
* it is difficult to prevent rtrap from running BH's, and that would
|
|
* need to be done if the XCALL arrived while %pil==15.
|
|
*/
|
|
#define PIL_SMP_CALL_FUNC 1
|
|
#define PIL_SMP_RECEIVE_SIGNAL 2
|
|
#define PIL_SMP_CAPTURE 3
|
|
#define PIL_SMP_CTX_NEW_VERSION 4
|
|
|
|
#ifndef __ASSEMBLY__
|
|
#define PIL_RESERVED(PIL) ((PIL) == PIL_SMP_CALL_FUNC || \
|
|
(PIL) == PIL_SMP_RECEIVE_SIGNAL || \
|
|
(PIL) == PIL_SMP_CAPTURE || \
|
|
(PIL) == PIL_SMP_CTX_NEW_VERSION)
|
|
#endif
|
|
|
|
#endif /* !(_SPARC64_PIL_H) */
|