[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1243945585.23657.5934.camel@twins>
Date: Tue, 02 Jun 2009 14:26:25 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Paul Mundt <lethal@...ux-sh.org>
Cc: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
Daniel Walker <dwalker@...o99.com>,
Linus Walleij <linus.ml.walleij@...il.com>,
Andrew Victor <linux@...im.org.za>,
Haavard Skinnemoen <hskinnemoen@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
John Stultz <johnstul@...ux.vnet.ibm.com>,
linux-arm-kernel@...ts.arm.linux.org.uk, linux-sh@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: sched_clock() clocksource handling.
On Tue, 2009-06-02 at 16:54 +0900, Paul Mundt wrote:
> @@ -212,6 +213,7 @@ extern struct clocksource *clock; /* current clocksource */
>
> #define CLOCK_SOURCE_WATCHDOG 0x10
> #define CLOCK_SOURCE_VALID_FOR_HRES 0x20
> +#define CLOCK_SOURCE_USE_FOR_SCHED_CLOCK 0x40
One more thing though, as John suggested, this bit might want a proper
comment explaining when a clocksource should and should not set this
bit.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists