linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: Re: linux-next: Tree for Dec 5 (soc/qcom/qcom_stats)
Date: Tue, 5 Dec 2023 09:29:05 -0800	[thread overview]
Message-ID: <a173781e-b3b6-47a7-8bda-fb289fd9ffd5@infradead.org> (raw)
In-Reply-To: <50d8f1dd-4df2-446a-bd82-47d96637b507@infradead.org>



On 12/5/23 09:17, Randy Dunlap wrote:
> 
> 
> On 12/4/23 18:57, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20231204:
>>
> 
> on powerpc 32-bit:
> 
> ERROR: modpost: "__udivdi3" [drivers/soc/qcom/qcom_stats.ko] undefined!
> 
> 

Hi,

Looks like this is coming from the use of mult_frac() if I am reading the
generated .s file correctly:

 # ../drivers/soc/qcom/qcom_stats.c:224: 		entry[i].dur = mult_frac(MSEC_PER_SEC, entry[i].dur, ARCH_TIMER_FREQ);
	mulhwu 3,22,4	 # tmp194, tmp190, MEM[(long long unsigned int *)_107 + 16B]
	mulli 9,9,1000	 # tmp185, MEM[(long long unsigned int *)_107 + 16B],
	mulli 4,4,1000	 # tmp3, MEM[(long long unsigned int *)_107 + 16B],
	add 3,9,3	 #, tmp185, tmp194
	bl __udivdi3		 #

-- 
~Randy

      reply	other threads:[~2023-12-05 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  2:57 linux-next: Tree for Dec 5 Stephen Rothwell
2023-12-05 17:17 ` linux-next: Tree for Dec 5 (soc/qcom/qcom_stats) Randy Dunlap
2023-12-05 17:29   ` Randy Dunlap [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=a173781e-b3b6-47a7-8bda-fb289fd9ffd5@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=andersson@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).