Hi,
Isaku Yamahata writes:
Kouya SHIMURA write on 2007年1月26日 19:06:
Hi
NEW_TLBFLUSH_CLOCK_PERIOD_SOFTIRQ is used but not registered.
I've never experienced but system will panic in the very long run.
I wonder why Isaku missed it.
Ouch!
It doesn't cause panic, but it just becomes slow.
So I missed it.
No, it will cause a null-pointer exception at do_softirq() in Xen.
(*softirq_handlers[i])();
(XEN) $$$$$ PANIC in domain 0 (k6=0xf000000007c38000): ***
xen_handle_domain_access: exception table lookup failed, iip=0xf000000004043e60,
addr=0x0, spinning...
[snip]
(XEN) [<f000000004043e60>] do_softirq+0x120/0x1b0
(XEN) sp=f000000007c3fe00 bsp=f000000007c39390
I tried it by means of setting tlbflush_clock to huge value.
Anyway, I think it is not concerned with Anthony's problem.
Thanks,
Kouya