From: vincent.siles@provenrun.com (Vincent Siles)
To: linux-arm-kernel@lists.infradead.org
Subject: lsl / lsr possible confusion in v7_flush_dcache_all
Date: Thu, 8 Sep 2016 11:15:20 +0200 [thread overview]
Message-ID: <20160908091520.GE14909@vsiles-Desktop> (raw)
Hi !
While reading the v7_flush_dcache_all (arch/arm/mm/cache-v7.S), I
stumbled upon this line:
# r10 is the current cache level
127: add r2, r10, r10, lsr #1 @ work out 3x current cache level
If we want r2 to be 3 * r10, we should compute r10 + (r10 << 1), which
is lsl, not lsr.
I check for a recent kernel, the issue seems to still be here:
repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
revision: d71f058617564750261b673ea9b3352382b9cde4
Best regards,
Vincent Siles
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160908/ea8d9bbd/attachment.sig>
next reply other threads:[~2016-09-08 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 9:15 Vincent Siles [this message]
2016-09-08 9:38 ` lsl / lsr possible confusion in v7_flush_dcache_all Will Deacon
2016-09-08 9:50 ` Vincent Siles
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=20160908091520.GE14909@vsiles-Desktop \
--to=vincent.siles@provenrun.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).