timer_interrupt 在ppc上面的疑惑 请指教

tc1989tc

2.6.22 timer_interrupt如下：

1. void timer_interrupt(struct pt_regs * regs)
   
2. {
   
3.         struct pt_regs *old_regs;
   
4.         int next_dec;
   
5.         unsigned long cpu = smp_processor_id();
   
6.         unsigned jiffy_stamp = last_jiffy_stamp(cpu);
   
7.         extern void do_IRQ(struct pt_regs *);
   
8. 
   
9.         if (atomic_read(&ppc_n_lost_interrupts) != 0)
   
10.                 do_IRQ(regs);
    
11. 
    
12.         old_regs = set_irq_regs(regs);
    
13.         irq_enter();
    
14. 
    
15.         while ((next_dec = tb_ticks_per_jiffy - tb_delta(&jiffy_stamp)) <= 0) {
    
16.                 jiffy_stamp += tb_ticks_per_jiffy;
    
17.                
    
18.                 profile_tick(CPU_PROFILING);
    
19.                 update_process_times(user_mode(regs));
    
20. 
    
21.                   if (smp_processor_id())
    
22.                         continue;
    
23. 
    
24.                 /* We are in an interrupt, no need to save/restore flags */
    
25.                 write_seqlock(&xtime_lock);
    
26.                 tb_last_stamp = jiffy_stamp;
    
27.                 do_timer(1);
    
28. 
    
29.                 /*
    
30.                  * update the rtc when needed, this should be performed on the
    
31.                  * right fraction of a second. Half or full second ?
    
32.                  * Full second works on mk48t59 clocks, others need testing.
    
33.                  * Note that this update is basically only used through
    
34.                  * the adjtimex system calls. Setting the HW clock in
    
35.                  * any other way is a /dev/rtc and userland business.
    
36.                  * This is still wrong by -0.5/+1.5 jiffies because of the
    
37.                  * timer interrupt resolution and possible delay, but here we
    
38.                  * hit a quantization limit which can only be solved by higher
    
39.                  * resolution timers and decoupling time management from timer
    
40.                  * interrupts. This is also wrong on the clocks
    
41.                  * which require being written at the half second boundary.
    
42.                  * We should have an rtc call that only sets the minutes and
    
43.                  * seconds like on Intel to avoid problems with non UTC clocks.
    
44.                  */
    
45.                 if ( ppc_md.set_rtc_time && ntp_synced() &&
    
46.                      xtime.tv_sec - last_rtc_update >= 659 &&
    
47.                      abs((xtime.tv_nsec / 1000) - (1000000-1000000/HZ)) < 500000/HZ) {
    
48.                           if (ppc_md.set_rtc_time(xtime.tv_sec+1 + timezone_offset) == 0)
    
49.                                 last_rtc_update = xtime.tv_sec+1;
    
50.                         else
    
51.                                 /* Try again one minute later */
    
52.                                 last_rtc_update += 60;
    
53.                 }
    
54.                 write_sequnlock(&xtime_lock);
    
55.         }
    
56.         if ( !disarm_decr[smp_processor_id()] )
    
57.                 set_dec(next_dec);
    
58.         last_jiffy_stamp(cpu) = jiffy_stamp;
    
59. 
    
60.         if (ppc_md.heartbeat && !ppc_md.heartbeat_count--)
    
61.                 ppc_md.heartbeat();
    
62. 
    
63.         irq_exit();
    
64.         set_irq_regs(old_regs);
    
65. }

复制代码

遇到内核panic信息如下：
Call Trace:
[C035B9E0] [C0006888] show_stack+0x34/0x194 (unreliable)
[C035BA10] [C005C2D4] softlockup_tick+0xa4/0xf4
[C035BA30] [C00388E4] run_local_timers+0x18/0x28
[C035BA40] [C0038924] update_process_times+0x30/0x7c
[C035BA50] [C004F344] tick_sched_timer+0xf4/0x304
[C035BAB0] [C004B4E0] hrtimer_interrupt+0x25c/0x2b4
[C035BB20] [C000A524] timer_interrupt+0x74/0x330
。。。。。。。

linux版本为2.6.22 在ppc上面，按照上面的打印消息
去查看timer_interrupt 函数，但是并没有看到调用hrtimer_interrupt啊？ 请问上面的打印堆栈不准确？
但是在3.18.1版本能追溯到timer_interrupt -->__timer_interrupt -->hrtimer_interrupt 的调用

yadihu101

hrtimer_interrupt 不是在软中断中被激活的吗？