From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: cache-uniphier: activate ways for secondary CPUs
Date: Tue, 26 Apr 2016 09:52:20 +0200 [thread overview]
Message-ID: <10871675.TbbhfWgNkx@wuerfel> (raw)
In-Reply-To: <CAK7LNAS4gYS3VswmnUj6OS0mBpYeSKLPnV26mO0yRiEtwEDoww@mail.gmail.com>
On Tuesday 26 April 2016 09:55:35 Masahiro Yamada wrote:
> Hi Arnd,
>
> 2016-04-26 7:13 GMT+09:00 Arnd Bergmann <arnd@arndb.de>:
> > On Friday 15 April 2016 16:05:46 Masahiro Yamada wrote:
> >> This outer cache allows to control active ways independently for
> >> each CPU, but currently nothing is done for secondary CPUs. In
> >> other words, all the ways are locked for secondary CPUs by default.
> >> This commit fixes it to fully bring out the performance of this
> >> outer cache.
> >>
> >> There would be two possible ways to achieve this:
> >>
> >> [1] Each CPU initializes active ways for itself. This can be done
> >> via the SSCLPDAWCR register. This is a banked register, so each
> >> CPU sees a different instance of the register.
> >>
> >> [2] The master CPU initializes active ways for all the CPUs. This
> >> is available via SSCDAWCARMR(N) registers. They are mapped at
> >> the address SSCDAWCARMR + 4 * N, where N is the CPU number.
> >>
> >> Currently, the outer cache frame work does not support a per-CPU
> >> init callback. So this commit adopts [2]; the master CPU iterates
> >> over possible CPUs setting up SSCDAWCARMR(N) registers.
> >>
> >> Unfortunately, the register offsets of SSCDAWCARMR(N) are different
> >> by SoC. We can live with it by checking the version register.
> >>
> >> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> >>
> >
> > Applied to next/soc, thanks!
> >
> > I'm a little lost with the patches you send, could you check that
> > I have applied all the ones you sent for 4.7 so far?
> >
> > Arnd
>
>
> Was this one really applied, or not yet?
>
> My intention was to send this one just for review,
> because outer-cache things are generally in Russell's field.
>
> If you have already applied it, I should drop it
> from Russell's patch tracker.
> (Sorry, I should have mentioned it.)
>
> Please let me know the status.
Sorry, my mistake, I accidentally sent out my mail early and
then did not put it into arm-soc in the end.
It's not in arm-soc and it should go through Russell's patch tracker.
Arnd
next prev parent reply other threads:[~2016-04-26 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 7:05 [PATCH] ARM: cache-uniphier: activate ways for secondary CPUs Masahiro Yamada
2016-04-25 22:13 ` Arnd Bergmann
2016-04-26 0:55 ` Masahiro Yamada
2016-04-26 7:52 ` Arnd Bergmann [this message]
2016-04-26 7:55 ` Masahiro Yamada
-- strict thread matches above, loose matches on Subject: below --
2016-04-21 2:01 Masahiro Yamada
2016-04-21 2:04 Masahiro Yamada
2016-04-26 8:11 Masahiro Yamada
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=10871675.TbbhfWgNkx@wuerfel \
--to=arnd@arndb.de \
--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