From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Alexey Klimov <alexey.klimov@linaro.org>,
k.kozlowski@samsung.com, linux-samsung-soc@vger.kernel.org
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
yury.norov@gmail.com, klimov.linux@gmail.com, kgene@kernel.org
Subject: Re: [RFC PATCH] clocksource: exynos_mct: use container_of() instead of this_cpu_ptr()
Date: Tue, 15 Sep 2015 10:47:49 +0200 [thread overview]
Message-ID: <55F7DB35.9070803@linaro.org> (raw)
In-Reply-To: <1441324198-14513-1-git-send-email-alexey.klimov@linaro.org>
On 09/04/2015 01:49 AM, Alexey Klimov wrote:
> Since evt structure is embedded in per-CPU mevt structure it's
> definitely faster to use container_of() to get access to mevt
> if we have evt (for example as incoming function argument) instead
> of more expensive approach with this_cpu_ptr(&percpu_mct_tick).
> this_cpu_ptr() on per-CPU mevt structure leads to access to cp15
> to get cpu id and arithmetic operations.
> Container_of() is cheaper since it's just one asm instruction.
> This should work if used evt pointer is correct and owned by
> local mevt structure.
>
> For example, before this patch set_state_shutdown() looks like:
>
> 4a4: e92d4010 push {r4, lr}
> 4a8: e3004000 movw r4, #0
> 4ac: ebfffffe bl 0 <debug_smp_processor_id>
> 4b0: e3003000 movw r3, #0
> 4b4: e3404000 movt r4, #0
> 4b8: e3403000 movt r3, #0
> 4bc: e7933100 ldr r3, [r3, r0, lsl #2]
> 4c0: e0844003 add r4, r4, r3
> 4c4: e59400c0 ldr r0, [r4, #192] ; 0xc0
> 4c8: ebffffd4 bl 420 <exynos4_mct_tick_stop.isra.1>
> 4cc: e3a00000 mov r0, #0
> 4d0: e8bd8010 pop {r4, pc}
>
> With this patch:
>
> 4a4: e92d4010 push {r4, lr}
> 4a8: e59000c0 ldr r0, [r0, #192] ; 0xc0
> 4ac: ebffffdb bl 420 <exynos4_mct_tick_stop.isra.1>
> 4b0: e3a00000 mov r0, #0
> 4b4: e8bd8010 pop {r4, pc}
>
> Also, for me size of exynos_mct.o decreased from 84588 bytes
> to 83956.
>
> Signed-off-by: Alexey Klimov <alexey.klimov@linaro.org>
> ---
Despite the RFC I applied the patch as it seems simple enough and it has
been reviewed by Krzysztof.
-- Daniel
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
prev parent reply other threads:[~2015-09-15 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 23:49 [RFC PATCH] clocksource: exynos_mct: use container_of() instead of this_cpu_ptr() Alexey Klimov
2015-09-10 4:21 ` Krzysztof Kozlowski
2015-09-15 8:47 ` Daniel Lezcano [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=55F7DB35.9070803@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=alexey.klimov@linaro.org \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=klimov.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yury.norov@gmail.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).