Messages in this thread | | | Subject | RE: CONFIG_PRINTK_TIME woes | Date | Tue, 23 Aug 2005 07:07:17 -0700 | From | "Luck, Tony" <> |
| |
>I'd hate to have to test for something for CONFIG_PRINTK_TIME >every time sched_clock() is being called.
Me too.
>The quick fix would seem to be to only allow CONFIG_PRINTK_TIME >from kernel cmdline to make it happen a bit later. So basically >make int printk_time = 0 until command line is evaluated.
Good thought, but this won't work for ia64 in the hot-plug cpu case. There are a couple of printk() calls by new cpus as they boot before they have set-up their per-cpu areas. So there is no global state that can be checked to decide whether it is safe for printk() to call sched_clock().
-Tony - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |