• S
    x86, trace: Introduce entering/exiting_irq() · eddc0e92
    Seiji Aguchi 提交于
    When implementing tracepoints in interrupt handers, if the tracepoints are
    simply added in the performance sensitive path of interrupt handers,
    it may cause potential performance problem due to the time penalty.
    
    To solve the problem, an idea is to prepare non-trace/trace irq handers and
    switch their IDTs at the enabling/disabling time.
    
    So, let's introduce entering_irq()/exiting_irq() for pre/post-
    processing of each irq handler.
    
    A way to use them is as follows.
    
    Non-trace irq handler:
    smp_irq_handler()
    {
    	entering_irq();		/* pre-processing of this handler */
    	__smp_irq_handler();	/*
    				 * common logic between non-trace and trace handlers
    				 * in a vector.
    				 */
    	exiting_irq();		/* post-processing of this handler */
    
    }
    
    Trace irq_handler:
    smp_trace_irq_handler()
    {
    	entering_irq();		/* pre-processing of this handler */
    	trace_irq_entry();	/* tracepoint for irq entry */
    	__smp_irq_handler();	/*
    				 * common logic between non-trace and trace handlers
    				 * in a vector.
    				 */
    	trace_irq_exit();	/* tracepoint for irq exit */
    	exiting_irq();		/* post-processing of this handler */
    
    }
    
    If tracepoints can place outside entering_irq()/exiting_irq() as follows,
    it looks cleaner.
    
    smp_trace_irq_handler()
    {
    	trace_irq_entry();
    	smp_irq_handler();
    	trace_irq_exit();
    }
    
    But it doesn't work.
    The problem is with irq_enter/exit() being called. They must be called before
    trace_irq_enter/exit(),  because of the rcu_irq_enter() must be called before
    any tracepoints are used, as tracepoints use  rcu to synchronize.
    
    As a possible alternative, we may be able to call irq_enter() first as follows
    if irq_enter() can nest.
    
    smp_trace_irq_hander()
    {
    	irq_entry();
    	trace_irq_entry();
    	smp_irq_handler();
    	trace_irq_exit();
    	irq_exit();
    }
    
    But it doesn't work, either.
    If irq_enter() is nested, it may have a time penalty because it has to check if it
    was already called or not. The time penalty is not desired in performance sensitive
    paths even if it is tiny.
    Signed-off-by: NSeiji Aguchi <seiji.aguchi@hds.com>
    Link: http://lkml.kernel.org/r/51C3238D.9040706@hds.comSigned-off-by: NH. Peter Anvin <hpa@linux.intel.com>
    Cc: Steven Rostedt <rostedt@goodmis.org>
    eddc0e92
therm_throt.c 13.8 KB