Re: [git pull] scheduler updates

From: Ingo Molnar
Date: Mon Nov 17 2008 - 17:50:46 EST



* Venki Pallipadi <venkatesh.pallipadi@xxxxxxxxx> wrote:

> Patch being discussed on this thread (commit 0d12cdd) has a
> regression on one of the test systems here.
>
> With the patch, I see
>
> checking TSC synchronization [CPU#0 -> CPU#1]:
> Measured 28 cycles TSC warp between CPUs, turning off TSC clock.
> Marking TSC unstable due to check_tsc_sync_source failed
>
> Whereas, without the patch syncs pass fine on all CPUs
>
> checking TSC synchronization [CPU#0 -> CPU#1]: passed.
>
> Due to this, TSC is marke unstable, when it is not actually unstable.
> This is because syncs in check_tsc_wrap() goes away due to this commit.
>
> As per the discussion on this thread, correct way to fix this is to add
> explicit syncs as below?

ah. Yes.

Could you please check whether:

> + rdtsc_barrier();
> start = get_cycles();
> + rdtsc_barrier();
> /*
> * The measurement runs for 20 msecs:
> */
> @@ -61,7 +63,9 @@ static __cpuinit void check_tsc_warp(voi
> */
> __raw_spin_lock(&sync_lock);
> prev = last_tsc;
> + rdtsc_barrier();
> now = get_cycles();
> + rdtsc_barrier();

adding the barrier just _after_ the get_cycles() call (but not before
it) does the trick too? That should be enough in this case.

Ingo
--
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/