Function report | 
Source Code:include\trace\events\rcu.h | 
Create Date:2022-07-28 10:17:26 | 
| Last Modify:2020-03-12 14:18:49 | Copyright©Brick | 
| home page | Tree | 
| Annotation kernel can get tool activity | Download SCCT | Chinese | 
Name:Tracepoint for dyntick-idle entry/exit events
Proto:static inline void trace_rcu_dyntick(const char *polarity, long oldnesting, long newnesting, int dynticks)
Type:void
Parameter:
| Type | Parameter | Name | 
|---|---|---|
| const char * | polarity | |
| long | oldnesting | |
| long | newnesting | |
| int | dynticks | 
NULL
| Name | Describe | 
|---|---|
| rcu_eqs_enter | Enter an RCU extended quiescent state, which can be either the* idle loop or adaptive-tickless usermode execution.* We crowbar the ->dynticks_nmi_nesting field to zero to allow for* the possibility of usermode upcalls having messed up our count | 
| rcu_nmi_exit_common | If we are returning from the outermost NMI handler that interrupted an* RCU-idle period, update rdp->dynticks and rdp->dynticks_nmi_nesting* to let the RCU grace-period handling know that the CPU is back to* being RCU-idle | 
| rcu_eqs_exit | Exit an RCU extended quiescent state, which can be either the* idle loop or adaptive-tickless usermode execution.* We crowbar the ->dynticks_nmi_nesting field to DYNTICK_IRQ_NONIDLE to* allow for the possibility of usermode upcalls messing up our count of | 
| rcu_nmi_enter_common | _nmi_enter_common - inform RCU of entry to NMI context*@irq: Is this call from rcu_irq_enter?* If the CPU was idle from RCU's viewpoint, update rdp->dynticks and* rdp->dynticks_nmi_nesting to let the RCU grace-period handling know* that the CPU is active | 
| Source code conversion tool public plug-in interface  | X | 
|---|---|
| Support c/c++/esqlc/java Oracle/Informix/Mysql Plug-in can realize: logical Report Code generation and batch code conversion  |