From: js07.lee@samsung.com (Jungseung Lee)
To: linux-arm-kernel@lists.infradead.org
Subject: [Q] L1_CACHE_BYTES on flush_pfn_alias function.
Date: Sun, 26 Jan 2014 14:13:43 +0900 [thread overview]
Message-ID: <003c01cf1a55$623979f0$26ac6dd0$@samsung.com> (raw)
In-Reply-To: <20140124154321.GI19052@arm.com>
Not to flush some more bytes. In the scenario, they can *omit* to flush last 32 bytes.
L1_CACHE_BYTES = 64 (ARM v7, CA9)
asm( "mcrr p15, 0, %1, %0, c14\n"
" mcr p15, 0, %2, c7, c10, 4"
:
: "r" (to), "r" (to + PAGE_SIZE - L1_CACHE_BYTES), "r" (zero)
: "cc");
-----Original Message-----
From: Catalin Marinas [mailto:catalin.marinas at arm.com]
Sent: Saturday, January 25, 2014 12:43 AM
Cc: linux-arm-kernel at lists.infradead.org; linux at arm.linux.org.uk; linux-kernel at vger.kernel.org
Subject: Re: [Q] L1_CACHE_BYTES on flush_pfn_alias function.
On Fri, Jan 17, 2014 at 09:54:42AM +0000, wrote:
> Follow the mailing-list
> http://comments.gmane.org/gmane.linux.ports.arm.omap/31686
>
> >>Setting the L1 cache line size larger than it actually is should be safe.
>
> the written code expected as L1_CACHE_BYTES should be real cache line
> size has bug.
> It looks like that flush_pfn_alias function should be fixed.
Did you actually notice any problem with flushing some more bytes? It's a clean+invalidate rather than invalidate, I don't see any problem.
--
Catalin
next prev parent reply other threads:[~2014-01-26 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 9:54 [Q] L1_CACHE_BYTES on flush_pfn_alias function 이정승
2014-01-24 15:43 ` Catalin Marinas
2014-01-26 5:13 ` Jungseung Lee [this message]
2014-01-27 16:43 ` Catalin Marinas
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='003c01cf1a55$623979f0$26ac6dd0$@samsung.com' \
--to=js07.lee@samsung.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).