Re: [RFC][PATCH 1/5] x86: Remove const_udelay() caring about whichcpu var it uses

From: Christoph Lameter
Date: Mon Sep 19 2011 - 17:51:17 EST


On Mon, 19 Sep 2011, Steven Rostedt wrote:

> The __const_udelay() code originally used raw_smp_processor_id()
> in its calculations for a delaying. Probably because if it were
> to migrate, it would take much longer to do so than the requested
> delay.
>
> Switch from this_cpu_read() to __this_cpu_read() to document that
> the read is racy and we do not care.

Is preemption disabled by all callers to __const_udelay?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/