[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1281944854.1926.948.camel@laptop>
Date: Mon, 16 Aug 2010 09:47:34 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: mingo@...e.hu, linux-kernel@...r.kernel.org, chris@...stnet.net,
debian00@...ceadsl.fr, hpa@...or.com, jonathan.protzenko@...il.com,
mans@...sr.com, psastudio@...l.ru, rjw@...k.pl,
stephan.eicher@....de, sxxe@....de, thomas@...hlinux.org,
venki@...gle.com, wonghow@...il.com, stable@...nel.org
Subject: Re: [patch 1/3] sched: init rt_avg stat whenever rq comes online
On Fri, 2010-08-13 at 12:45 -0700, Suresh Siddha wrote:
> plain text document attachment (sched_reset_rt_avg_stat_online.patch)
> TSC's get reset after suspend/resume and this leads to a scenario of
> rq->clock (sched_clock_cpu()) less than rq->age_stamp. This leads
> to a big value returned by scale_rt_power() and the resulting big group
> power set by the update_group_power() is causing improper load balancing
> between busy and idle cpu's after suspend/resume.
ARGH, so i[357] westmere mobile stops TSC on some power state?
Why don't we sync it back to the other CPUs instead?
Or does it simply mark TSCs unstable and leaves it at that?
In any case, this needs to be fixed at the clock level, not like this.
--
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