From: Hans Zhang <18255117159@163.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: manivannan.sadhasivam@linaro.org, kw@linux.com,
kishon@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
rockswang7@gmail.com
Subject: Re: [v8] misc: pci_endpoint_test: Fix overflow of bar_size
Date: Wed, 8 Jan 2025 00:12:32 +0800 [thread overview]
Message-ID: <58a23cfb-190f-44aa-a06a-d496cc252fb0@163.com> (raw)
In-Reply-To: <Z31O8B14sKd5eac-@ryzen>
On 2025/1/7 23:57, Niklas Cassel wrote:>>> The error:
>>> drivers/misc/pci_endpoint_test.c:315: undefined reference to `__udivmoddi4'
>>> sounds like the compiler is using a specialized instruction to do both div
>>> and mod in one. By removing the mod in patch 1/2, I expect that patch 2/2
>>> will no longer get this error.
>>
>> The __udivmoddi4 may be the way div and mod are combined.
>>
>> Delete remain's patch 1/2 according to your suggestion. I compiled it as a
>> KO module for an experiment.
>>
>> There are still __udivdi3 errors, so the do_div API must be used.
>
> Ok. Looking at do_div(), it seems to be the correct API to use
> for this problem. Just change bar_size type to u64 (instead of casting)
> and use do_div() ? That is how it is seems to be used in other drivers.
>
> I still think that a patch that removes the "remainder" code is a good
> cleanup, so please send it as patch 1/2, you can be the author, just add:
> Suggested-by: Niklas Cassel <cassel@kernel.org>
>
Thank you very much for Niklas' discussion on this patch. I will
resubmit two patches in the future.
Best regards
Hans
next prev parent reply other threads:[~2025-01-07 16:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 15:16 [v8] misc: pci_endpoint_test: Fix overflow of bar_size Hans Zhang
2025-01-06 11:49 ` Niklas Cassel
2025-01-06 13:56 ` Hans Zhang
2025-01-06 15:32 ` Hans Zhang
2025-01-07 10:32 ` Niklas Cassel
2025-01-07 11:27 ` Hans Zhang
2025-01-07 11:33 ` Niklas Cassel
2025-01-07 11:43 ` Hans Zhang
2025-01-07 11:47 ` Niklas Cassel
2025-01-07 12:09 ` Hans Zhang
2025-01-07 13:36 ` Niklas Cassel
2025-01-07 15:44 ` Hans Zhang
2025-01-07 15:57 ` Niklas Cassel
2025-01-07 16:12 ` Hans Zhang [this message]
2025-01-08 14:10 ` Arnd Bergmann
2025-01-08 14:13 ` Niklas Cassel
2025-01-09 2:59 ` Hans Zhang
2025-01-09 6:29 ` Arnd Bergmann
2025-01-09 9:19 ` Hans Zhang
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=58a23cfb-190f-44aa-a06a-d496cc252fb0@163.com \
--to=18255117159@163.com \
--cc=arnd@arndb.de \
--cc=cassel@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rockswang7@gmail.com \
/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