It is very common to have many processor to run over the same machine but run different OS actually, so that timestamp alignment is key to do the right debugging when find something wrong.
Linux adopt schedule clock stopped, so that printk timestamp would get during suspend period which break such assumption in the old days. So this patch set is supposed to recover such behavior again. BTW, I am not sure whether we could add additional member in printk log structure, so that we could print out two piece of log with one including suspend time, while another not? Lei Wen (3): time: create __get_monotonic_boottime for WARNless calls timekeeping: move clocksource init to the early place printk: using booting time as the timestamp include/linux/time.h | 2 ++ init/main.c | 1 + kernel/printk/printk.c | 4 ++-- kernel/time/timekeeping.c | 55 ++++++++++++++++++++++++++++++++++++----------- 4 files changed, 48 insertions(+), 14 deletions(-) -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/