From: David Daney <ddaney@caviumnetworks.com>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: [PATCH -queue 1/3] MIPS: add a common mips_sched_clock()
Date: Mon, 01 Feb 2010 09:07:17 -0800 [thread overview]
Message-ID: <4B670A45.3010105@caviumnetworks.com> (raw)
In-Reply-To: <198fc72d92823547c9be132616fd2ebc2091ff39.1265022593.git.wuzhangjin@gmail.com>
Wu Zhangjin wrote:
> + "dmultu\t%[cnt],%[mult]\n\t"
> + "nor\t%[t1],$0,%[shift]\n\t"
> + "mfhi\t%[t2]\n\t"
> + "mflo\t%[t3]\n\t"
> + "dsll\t%[t2],%[t2],1\n\t"
> + "dsrlv\t%[rv],%[t3],%[shift]\n\t"
> + "dsllv\t%[t1],%[t2],%[t1]\n\t"
This is unlikely to work in 32-bit kernels.
David Daney
next prev parent reply other threads:[~2010-02-01 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 11:13 [PATCH -queue 1/3] MIPS: add a common mips_sched_clock() Wu Zhangjin
2010-02-01 11:13 ` [PATCH -queue 2/3] MIPS: cavium-octeon: rewrite the sched_clock() based on mips_sched_clock() Wu Zhangjin
2010-02-01 11:13 ` [PATCH -queue v8 3/3] MIPS: r4k: Add a high resolution sched_clock() Wu Zhangjin
2010-02-01 17:07 ` David Daney [this message]
2010-02-26 17:35 ` [PATCH -queue 1/3] MIPS: add a common mips_sched_clock() Wu Zhangjin
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=4B670A45.3010105@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@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