From: Chen Gang <gang.chen.5i5j@gmail.com>
To: James Hogan <james.hogan@imgtec.com>
Cc: rostedt@goodmis.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-metag@vger.kernel.org
Subject: Re: [PATCH] arch: metag: lib: add "umoddi3.S" file for __umoddi3()
Date: Fri, 20 Dec 2013 18:20:14 +0800 [thread overview]
Message-ID: <52B419DE.8050706@gmail.com> (raw)
In-Reply-To: <52B40E44.9040603@imgtec.com>
On 12/20/2013 05:30 PM, James Hogan wrote:
> On 20/12/13 01:44, Chen Gang wrote:
>> On 12/19/2013 09:47 PM, James Hogan wrote:
>>> No, I believe there shouldn't be any use of the C 64bit division/modulo
>>> operations in generic kernel code in the first place, so like I said
>>> before the code in question should be fixed to use the proper functions
>>> in <linux/math64.h>.
>>>
>>
>> OK, thanks, your idea is one of fix ways.
>>
>> Hmm... for me, it is still not a bad idea to add "__umoddi3" to metag.
>
> NAK
>
> Please read this:
> http://yarchive.net/comp/linux/64bit_divide.html
>
OK, thanks, that sounds reasonable to me. For kernel, we really need
treat it carefully.
Hmm... but do you know why we need some 64-bit functions which are
implemented under "arch/metag/lib/*.S"? can we use <linux/math64.h>
instead of them? (e.g 64-bit '/').
And for me, 64-bit '/' and '%' are related operations, if provide one,
we also need provide the other (or neither of them are provided).
Thanks.
--
Chen Gang
Open, share and attitude like air, water and life which God blessed
next prev parent reply other threads:[~2013-12-20 10:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 12:05 [PATCH] arch: metag: lib: add "umoddi3.S" file for __umoddi3() Chen Gang
2013-12-19 12:17 ` James Hogan
2013-12-19 13:37 ` Chen Gang
2013-12-19 13:47 ` James Hogan
2013-12-20 1:44 ` Chen Gang
2013-12-20 9:30 ` James Hogan
2013-12-20 10:20 ` Chen Gang [this message]
2013-12-20 10:48 ` James Hogan
2013-12-20 11:51 ` Chen Gang
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=52B419DE.8050706@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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