From: Daniel Lezcano <daniel.lezcano-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Alexandre Courbot
<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] clocksource/drivers/tegra: allow timer irq affinity change
Date: Tue, 27 Oct 2015 11:14:59 +0100 [thread overview]
Message-ID: <562F4EA3.7000202@linaro.org> (raw)
In-Reply-To: <1445787630-13251-1-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
On 10/25/2015 04:40 PM, Lucas Stach wrote:
> Allow the timer core to change the smp affinity of the broadcast timer
> irq by setting CLOCK_EVT_FEAT_DYNIRQ flag.
>
> This reduces interrupt pressure and wakeups on CPU0 as well as vastly
> reducing the number of timer broadcast IPIs.
Did you test this patch on a tegra2 ?
--
<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
next prev parent reply other threads:[~2015-10-27 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 15:40 [PATCH] clocksource/drivers/tegra: allow timer irq affinity change Lucas Stach
[not found] ` <1445787630-13251-1-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-10-27 10:14 ` Daniel Lezcano [this message]
[not found] ` <562F4EA3.7000202-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-10-27 20:22 ` Lucas Stach
[not found] ` <1445977362.2535.1.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-10-27 20:54 ` Daniel Lezcano
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=562F4EA3.7000202@linaro.org \
--to=daniel.lezcano-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org \
--cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).