From: Dirk Behme <dirk.behme@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores
Date: Fri, 18 Dec 2015 11:58:33 +0000 [thread overview]
Message-ID: <5673F4E9.9070205@gmail.com> (raw)
In-Reply-To: <CAMuHMdVVL9T6U8npb5kOLdP3PmS6Lhx0b9O3FKgxd2HQcUedFw@mail.gmail.com>
Hi Geert,
On 18.12.2015 12:02, Geert Uytterhoeven wrote:
> Hi Dirk,
>
> On Sat, Dec 12, 2015 at 8:16 AM, Dirk Behme <dirk.behme@gmail.com> wrote:
>> From: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>>
>> This patch adds Cortex-A53 CPU cores to r8a7795 SoC for a total of 8
>> cores (4 x Cortex-A57 + 4 x Cortex-A53).
>>
>> Signed-off-by: Takeshi Kihara <takeshi.kihara.df@renesas.com>
>> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>
> Thanks, I can confirm this works.
>
> However, as the scheduler is not big.LITTLE aware (running processes are not
> migrated automatically to the faster CA57 cores when these are idle), it makes
> performance less deterministic.
What's the plan, then?
Waiting for big.LITTLE getting merged before enabling the A53? Or not
using the A53 at all?
Best regards
Dirk
prev parent reply other threads:[~2015-12-18 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 7:16 [PATCH 1/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores Dirk Behme
2015-12-12 7:16 ` [PATCH 2/2] arm64: dts: r8a7795: Add L2 cache-controller nodes Dirk Behme
2015-12-18 11:03 ` Geert Uytterhoeven
2015-12-18 11:56 ` Dirk Behme
2015-12-18 13:33 ` Geert Uytterhoeven
2015-12-18 13:46 ` Sudeep Holla
2015-12-18 11:02 ` [PATCH 1/2] arm64: dts: r8a7795: Add Cortex-A53 CPU cores Geert Uytterhoeven
2015-12-18 11:58 ` Dirk Behme [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=5673F4E9.9070205@gmail.com \
--to=dirk.behme@gmail.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).