From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: exynos_defconfig Enable CONFIG_LOCKUP_DETECTOR.
Date: Tue, 13 Jan 2015 09:18:08 +0100 [thread overview]
Message-ID: <1421137088.8355.1.camel@AMDC1943> (raw)
In-Reply-To: <1421088614-4662-1-git-send-email-moon.linux@yahoo.com>
On wto, 2015-01-13 at 00:20 +0530, Anand Moon wrote:
> On enabling CONFIG_LOCKUP_DETECTOR the kernel to act as a watchdog
> to detect hard and soft lockups. Enabling CONFIG_LOCKUP_DETECTOR
> don't introduce much overhead on exyons SOC.
>
> CONFIG_LOCKUP_DETECTOR is enabled on multi_v7_defconfig.
>
> Changes since v3:
> * Made commit message more clear
> * Corrected difference between CONFIG_LOCKUP_DETECTOR and CONFIG_LOCKDEP.
>
> Tested on Exynos5422 ODROID XU3 board.
>
> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Signed-off-by: Anand Moon <moon.linux@yahoo.com>
Now it looks okay. My reviewed-by may stay on.
Best regards,
Krzysztof
> ---
> arch/arm/configs/exynos_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
> index 5ef14de..64b2fe9 100644
> --- a/arch/arm/configs/exynos_defconfig
> +++ b/arch/arm/configs/exynos_defconfig
> @@ -182,6 +182,7 @@ CONFIG_DETECT_HUNG_TASK=y
> CONFIG_DEBUG_RT_MUTEXES=y
> CONFIG_DEBUG_SPINLOCK=y
> CONFIG_DEBUG_MUTEXES=y
> +CONFIG_LOCKUP_DETECTOR=y
> CONFIG_DEBUG_INFO=y
> CONFIG_DEBUG_USER=y
> CONFIG_CRYPTO_SHA256=y
next prev parent reply other threads:[~2015-01-13 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 18:50 [PATCH v3] ARM: exynos_defconfig Enable CONFIG_LOCKUP_DETECTOR Anand Moon
2015-01-13 8:18 ` Krzysztof Kozlowski [this message]
2015-01-24 4:55 ` Kukjin Kim
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=1421137088.8355.1.camel@AMDC1943 \
--to=k.kozlowski@samsung.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).