public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: linux-kernel@vger.kernel.org, hskinnemoen@gmail.com, linux.mdb@gmail.com
Subject: Re: [PATCH 03/31] Add debugger entry points for AVR32
Date: Thu, 28 Jan 2016 21:16:49 +0100	[thread overview]
Message-ID: <20160128201649.GA11179@samfundet.no> (raw)
In-Reply-To: <1454010377-28501-1-git-send-email-jeffmerkey@gmail.com>

Around Thu 28 Jan 2016 12:46:17 -0700 or thereabout, Jeffrey Merkey wrote:
> This patch series adds an export which can be set by system debuggers to
> direct the hard lockup and soft lockup detector to trigger a breakpoint
> exception and enter a debugger if one is active.  It is assumed that if
> someone sets this variable, then an breakpoint handler of some sort will
> be actively loaded or registered via the notify die handler chain.
> 
> This addition is extremely useful for debugging hard and soft lockups
> real time and quickly from a console debugger.
> 
> Signed-off-by: Jeffrey Merkey <jeffmerkey@gmail.com>

Acked-by: Hans-Christian Egtvedt <egtvedt@samfundet.no>

> ---
>  arch/avr32/include/asm/kdebug.h | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/arch/avr32/include/asm/kdebug.h b/arch/avr32/include/asm/kdebug.h
> index f930ce2..f67caf0 100644
> --- a/arch/avr32/include/asm/kdebug.h
> +++ b/arch/avr32/include/asm/kdebug.h
> @@ -1,6 +1,10 @@
>  #ifndef __ASM_AVR32_KDEBUG_H
>  #define __ASM_AVR32_KDEBUG_H
>  
> +static inline void arch_breakpoint(void)
> +{
> +}

Will not this just be optimized away? Are you expecting other developers to
add a no-op assembler instruction into this function body?

<snipp>
-- 
Best regards, Hans-Christian Egtvedt

  reply	other threads:[~2016-01-28 20:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 19:46 [PATCH 03/31] Add debugger entry points for AVR32 Jeffrey Merkey
2016-01-28 20:16 ` Hans-Christian Noren Egtvedt [this message]
2016-01-28 20:20   ` Jeffrey Merkey

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=20160128201649.GA11179@samfundet.no \
    --to=egtvedt@samfundet.no \
    --cc=hskinnemoen@gmail.com \
    --cc=jeffmerkey@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.mdb@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