All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet.Gupta1@synopsys.com (Vineet Gupta)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] arc: warn only once if DW2_UNWIND is disabled
Date: Tue, 28 Jun 2016 10:00:56 +0530	[thread overview]
Message-ID: <5771FD80.1090906@synopsys.com> (raw)
In-Reply-To: <1466668839-28210-1-git-send-email-abrodkin@synopsys.com>

On Thursday 23 June 2016 01:30 PM, Alexey Brodkin wrote:
> If CONFIG_ARC_DW2_UNWIND is disabled every time arc_unwind_core()
> gets called following message gets printed in debug console:
> ----------------->8---------------
> CONFIG_ARC_DW2_UNWIND needs to be enabled
> ----------------->8---------------
> 
> That message makes sense if user indeed wants to see a backtrace or
> get nice function call-graphs in perf but what if user disabled
> unwinder for the purpose? Why pollute his debug console?
> 
> So instead we'll warn user about possibly missing feature once and
> let him decide if that was what he or she really wanted.
> 
> Signed-off-by: Alexey Brodkin <abrodkin at synopsys.com>
> Cc: stable at vger.kernel.org  [3.18+]

Does this really need to be stable backport ?

> ---
>  arch/arc/kernel/stacktrace.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arc/kernel/stacktrace.c b/arch/arc/kernel/stacktrace.c
> index e0efff1..b9192a6 100644
> --- a/arch/arc/kernel/stacktrace.c
> +++ b/arch/arc/kernel/stacktrace.c
> @@ -142,7 +142,7 @@ arc_unwind_core(struct task_struct *tsk, struct pt_regs *regs,
>  	 * prelogue is setup (callee regs saved and then fp set and not other
>  	 * way around
>  	 */
> -	pr_warn("CONFIG_ARC_DW2_UNWIND needs to be enabled\n");
> +	pr_warn_once("CONFIG_ARC_DW2_UNWIND needs to be enabled\n");
>  	return 0;
>  
>  #endif
> 

WARNING: multiple messages have this Message-ID (diff)
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	<linux-snps-arc@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
	<"[3.18+]"@synopsys.com>
Subject: Re: [PATCH] arc: warn only once if DW2_UNWIND is disabled
Date: Tue, 28 Jun 2016 10:00:56 +0530	[thread overview]
Message-ID: <5771FD80.1090906@synopsys.com> (raw)
In-Reply-To: <1466668839-28210-1-git-send-email-abrodkin@synopsys.com>

On Thursday 23 June 2016 01:30 PM, Alexey Brodkin wrote:
> If CONFIG_ARC_DW2_UNWIND is disabled every time arc_unwind_core()
> gets called following message gets printed in debug console:
> ----------------->8---------------
> CONFIG_ARC_DW2_UNWIND needs to be enabled
> ----------------->8---------------
> 
> That message makes sense if user indeed wants to see a backtrace or
> get nice function call-graphs in perf but what if user disabled
> unwinder for the purpose? Why pollute his debug console?
> 
> So instead we'll warn user about possibly missing feature once and
> let him decide if that was what he or she really wanted.
> 
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: stable@vger.kernel.org  [3.18+]

Does this really need to be stable backport ?

> ---
>  arch/arc/kernel/stacktrace.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arc/kernel/stacktrace.c b/arch/arc/kernel/stacktrace.c
> index e0efff1..b9192a6 100644
> --- a/arch/arc/kernel/stacktrace.c
> +++ b/arch/arc/kernel/stacktrace.c
> @@ -142,7 +142,7 @@ arc_unwind_core(struct task_struct *tsk, struct pt_regs *regs,
>  	 * prelogue is setup (callee regs saved and then fp set and not other
>  	 * way around
>  	 */
> -	pr_warn("CONFIG_ARC_DW2_UNWIND needs to be enabled\n");
> +	pr_warn_once("CONFIG_ARC_DW2_UNWIND needs to be enabled\n");
>  	return 0;
>  
>  #endif
> 

  reply	other threads:[~2016-06-28  4:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  8:00 [PATCH] arc: warn only once if DW2_UNWIND is disabled Alexey Brodkin
2016-06-23  8:00 ` Alexey Brodkin
2016-06-28  4:30 ` Vineet Gupta [this message]
2016-06-28  4:30   ` Vineet Gupta
2016-06-28  5:38   ` Alexey Brodkin
2016-06-28  5:38     ` Alexey Brodkin

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=5771FD80.1090906@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=linux-snps-arc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.