From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeffrey Merkey <jeffmerkey@gmail.com>, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
akpm@linux-foundation.org, linux.mdb@gmail.com,
dzickus@redhat.com, dyoung@redhat.com, mnfhuang@gmail.com
Subject: Re: [PATCH 02/31] Add debugger entry points for X86
Date: Thu, 28 Jan 2016 12:20:30 -0800 [thread overview]
Message-ID: <56AA780E.7000002@zytor.com> (raw)
In-Reply-To: <1454010374-28459-1-git-send-email-jeffmerkey@gmail.com>
On 01/28/16 11:46, 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>
> ---
> arch/x86/include/asm/kdebug.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/x86/include/asm/kdebug.h b/arch/x86/include/asm/kdebug.h
> index e5f5dc9..cbe9004 100644
> --- a/arch/x86/include/asm/kdebug.h
> +++ b/arch/x86/include/asm/kdebug.h
> @@ -3,6 +3,11 @@
>
> #include <linux/notifier.h>
>
> +static inline void arch_breakpoint(void)
> +{
> + asm(" int $3");
> +}
> +
> struct pt_regs;
>
Even though apparently gas changed "int $3" to "int3" the latter is
actually a different instruction (with subtly different behavior) and
this may very well be corrected in gas at a future date.
So please encode this as "int3". It should also be "asm volatile" since
it has side effects unbeknownst to the compiler.
-hpa
next prev parent reply other threads:[~2016-01-28 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:46 [PATCH 02/31] Add debugger entry points for X86 Jeffrey Merkey
2016-01-28 20:20 ` H. Peter Anvin [this message]
2016-01-28 20:22 ` Jeffrey Merkey
2016-01-28 21:18 ` H. Peter Anvin
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=56AA780E.7000002@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=dyoung@redhat.com \
--cc=dzickus@redhat.com \
--cc=jeffmerkey@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=mingo@redhat.com \
--cc=mnfhuang@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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.