From: yang.shi@linaro.org (Shi, Yang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: add HAVE_LATENCYTOP_SUPPORT config
Date: Mon, 14 Dec 2015 14:02:18 -0800 [thread overview]
Message-ID: <566F3C6A.1070704@linaro.org> (raw)
In-Reply-To: <20151110113408.GF6672@osiris>
Hi folks,
I tried to enable latencytop for arm64 and came across this discussion,
so any plan about when this will get merged into mainline? 4.5 merge window?
Thanks,
Yang
On 11/10/2015 3:34 AM, Heiko Carstens wrote:
>> From: Will Deacon <will.deacon@arm.com>
>> Date: Tue, 10 Nov 2015 11:10:04 +0000
>> Subject: [PATCH] Kconfig: remove HAVE_LATENCYTOP_SUPPORT
>>
>> As illustrated by a3afe70b83fd ("[S390] latencytop s390 support."),
>> HAVE_LATENCYTOP_SUPPORT is defined by an architecture to advertise an
>> implementation of save_stack_trace_tsk.
>>
>> However, as of 9212ddb5eada ("stacktrace: provide save_stack_trace_tsk()
>> weak alias") a dummy implementation is provided if STACKTRACE=y.
>> Given that LATENCYTOP already depends on STACKTRACE_SUPPORT and selects
>> STACKTRACE, we can remove HAVE_LATENCYTOP_SUPPORT altogether.
>>
>> Signed-off-by: Will Deacon <will.deacon@arm.com>
>> ---
>> arch/arc/Kconfig | 3 ---
>> arch/arm/Kconfig | 5 -----
>> arch/metag/Kconfig | 3 ---
>> arch/microblaze/Kconfig | 3 ---
>> arch/parisc/Kconfig | 3 ---
>> arch/powerpc/Kconfig | 3 ---
>> arch/s390/Kconfig | 3 ---
>> arch/sh/Kconfig | 3 ---
>> arch/sparc/Kconfig | 4 ----
>> arch/unicore32/Kconfig | 3 ---
>> arch/x86/Kconfig | 3 ---
>> lib/Kconfig.debug | 1 -
>> 12 files changed, 37 deletions(-)
>
> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2015-12-14 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 15:57 [PATCH] arm64: add HAVE_LATENCYTOP_SUPPORT config yalin wang
2015-11-06 16:05 ` Will Deacon
2015-11-06 16:11 ` yalin wang
2015-11-06 16:21 ` Will Deacon
2015-11-10 7:41 ` Heiko Carstens
2015-11-10 10:05 ` Will Deacon
2015-11-10 11:01 ` Heiko Carstens
2015-11-10 11:18 ` Will Deacon
2015-11-10 11:24 ` yalin wang
2015-11-10 11:34 ` Heiko Carstens
2015-12-14 22:02 ` Shi, Yang [this message]
2015-12-15 9:48 ` Will Deacon
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=566F3C6A.1070704@linaro.org \
--to=yang.shi@linaro.org \
--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).