All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: linux-next: Tree for Feb 11 (intel_pstate.c)
Date: Mon, 11 Feb 2013 09:29:09 -0800	[thread overview]
Message-ID: <51192A65.2020509@intel.com> (raw)
In-Reply-To: <511919C7.5080502@infradead.org>

On 02/11/2013 08:18 AM, Randy Dunlap wrote:
> On 02/10/13 23:47, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130208:
>>
>
> on i386:
>
> drivers/built-in.o: In function `intel_pstate_timer_func':
> intel_pstate.c:(.text+0x4ce97e): undefined reference to `__udivdi3'
> drivers/built-in.o: In function `intel_pstate_cpu_init':
> intel_pstate.c:(.cpuinit.text+0x974): undefined reference to `__udivdi3'
>
>
DOOH :-(  This patch fixes the issue.  I will work with Rafael to get it into
his next branch.

diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
index 86ad482..e879963 100644
--- a/drivers/cpufreq/intel_pstate.c
+++ b/drivers/cpufreq/intel_pstate.c
@@ -456,7 +456,8 @@ static inline void intel_pstate_calc_busy(struct cpudata *cp
         core_pct = div64_u64(sample->aperf * 100, sample->mperf);
         sample->freq = cpu->pstate.turbo_pstate * core_pct * 1000;

-       sample->core_pct_busy = sample->pstate_pct_busy * core_pct / 100;
+       sample->core_pct_busy = div_s64((sample->pstate_pct_busy * core_pct),
+                                       100);
  }

      reply	other threads:[~2013-02-11 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11  7:47 linux-next: Tree for Feb 11 Stephen Rothwell
2013-02-11  7:47 ` Stephen Rothwell
2013-02-11 16:18 ` linux-next: Tree for Feb 11 (intel_pstate.c) Randy Dunlap
2013-02-11 17:29   ` Dirk Brandewie [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51192A65.2020509@intel.com \
    --to=dirk.brandewie@gmail.com \
    --cc=dirk.j.brandewie@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.