Hello, Why in kernel/time.c:timer_interrupt , write_seqlock() locks also vsyscall variables? The comment says: We also need to lock the vsyscall variables, because both do_timer() and us change them. I don't understand why... And do_timer() is called by main_timer_handler in all cases? Regards, -- noone is alone. -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
