From: Heiko Stuebner <heiko@sntech.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Lin Huang <hl@rock-chips.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Douglas Anderson <dianders@chromium.org>,
linux-rockchip@lists.infradead.org,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: rk3399: Add capacity-dmips-mhz attributes
Date: Sun, 03 Mar 2019 14:35:40 +0100 [thread overview]
Message-ID: <17649285.loQdcguGhd@phil> (raw)
In-Reply-To: <20190302131030.2091-1-marc.zyngier@arm.com>
Am Samstag, 2. März 2019, 14:10:30 CET schrieb Marc Zyngier:
> The RK3399 has the interesting property to be a so called "big-little"
> system, where not all the CPUs are equal (the A53s are much weaker
> than the A72s).
>
> So far, we're not telling the OS that there is such a difference in
> processing capacity, and Linux assumes that they are equal. Too bad.
>
> Let's tell the OS about this by using the capacity-dmips-mhz
> property. The values used here are those used on the Juno platform,
> which is quite similar. This leads to the scheduler knowing that
> it can pack more tasks on the A72s, and leads to a better interactive
> experience.
>
> Tested-by: Robin Murphy <robin.murphy@arm.com>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Subject "arm64: dts: rockchip: foobar on rk3399" for the future please :-)
I've fixed that up and applied the patch for 5.2
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-03-03 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 13:10 [PATCH v2] arm64: rk3399: Add capacity-dmips-mhz attributes Marc Zyngier
2019-03-03 13:35 ` Heiko Stuebner [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=17649285.loQdcguGhd@phil \
--to=heiko@sntech.de \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=hl@rock-chips.com \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=robin.murphy@arm.com \
/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).