[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGjg+kGHxjrtb-Xn+mrJf0AgYhn+xB8awrpv94uhqOC=UBv3Kw@mail.gmail.com>
Date: Sun, 23 Dec 2012 19:42:29 +0800
From: Alex Shi <lkml.alex@...il.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Alex Shi <alex.shi@...el.com>,
Preeti U Murthy <preeti@...ux.vnet.ibm.com>, rob@...dley.net,
mingo@...hat.com, peterz@...radead.org, gregkh@...uxfoundation.org,
andre.przywara@....com, rjw@...k.pl, paul.gortmaker@...driver.com,
akpm@...ux-foundation.org, paulmck@...ux.vnet.ibm.com,
linux-kernel@...r.kernel.org, pjt@...gle.com,
vincent.guittot@...aro.org
Subject: Re: [PATCH 07/18] sched: compute runnable load avg in cpu_load and cpu_avg_load_per_task
>> @@ -2487,7 +2487,7 @@ static void __update_cpu_load(struct rq *this_rq, unsigned long this_load,
>> void update_idle_cpu_load(struct rq *this_rq)
>> {
>> unsigned long curr_jiffies = ACCESS_ONCE(jiffies);
>> - unsigned long load = this_rq->load.weight;
>> + unsigned long load = (unsigned long)this_rq->cfs.runnable_load_avg;
>
> So shouldn't this line be guarded with CONFIG_SMP too?
Thanks reminder. Yes, I already found this problem and plan to resend
the patch base on latest tree.
>
> Thanks,
--
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