From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH] ARM: Merge v7 and v8 outer cache operations
Date: Thu, 2 Apr 2015 08:57:15 +0200 [thread overview]
Message-ID: <20150402085715.4e8466db@lilith> (raw)
In-Reply-To: <20150330093936.GC17971@leverpostej>
Hello Mark,
On Mon, 30 Mar 2015 10:39:36 +0100, Mark Rutland <mark.rutland@arm.com>
wrote:
> On Fri, Mar 27, 2015 at 02:11:48PM +0000, Albert ARIBAUD wrote:
> > Hello Mark,
> >
> > On Thu, 12 Feb 2015 15:56:52 +0000, Mark Rutland <mark.rutland@arm.com>
> > wrote:
> > > On Sat, Jan 31, 2015 at 03:08:54AM +0000, fenghua at phytium.com.cn wrote:
> > > > From: David Feng <fenghua@phytium.com.cn>
> > > >
> > > > Armv7 and Armv8 allow outer cache exist, it is outside of the architecture
> > > > defined cache hierarchy and can not be manipulated by architecture defined
> > > > instructions. It's processor specific.
> > > > This patch merge v7_outer_cache_* and v8 l3_cache_*.
> > >
> > > This commit message is a little misleading, though it probably makes
> > > sense to have something of this sort ARMv8. Info dump below.
>
> [...]
>
> > So, does the commit message require rewriting?
>
> Yup. My complaint was that outer caches _can_ be manipulated by
> architecturally defined instructions, but only for maintenance by VA. So
> it's wrong to say that they cannot be manipulated by archtiecturally
> defined instructions.
Thanks. I expect a new version of this patch, then (and a non-RFC one
if the commit message is the only thing to fix).
> Mark.
Amicalement,
--
Albert.
prev parent reply other threads:[~2015-04-02 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 3:08 [U-Boot] [RFC PATCH] ARM: Merge v7 and v8 outer cache operations fenghua at phytium.com.cn
2015-02-12 15:37 ` Tom Rini
2015-02-12 15:56 ` Mark Rutland
2015-03-27 14:11 ` Albert ARIBAUD
2015-03-30 9:39 ` Mark Rutland
2015-04-02 6:57 ` Albert ARIBAUD [this message]
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=20150402085715.4e8466db@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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