From: Mark Salter <msalter@redhat.com>
To: Jeffrey Merkey <jeffmerkey@gmail.com>, linux-kernel@vger.kernel.org
Cc: a-jacquiot@ti.com, linux.mdb@gmail.com, linux-c6x-dev@linux-c6x.org
Subject: Re: [PATCH 18/31] Add debugger entry points for C6X
Date: Thu, 11 Feb 2016 17:52:57 -0500 [thread overview]
Message-ID: <1455231177.3767.62.camel@redhat.com> (raw)
In-Reply-To: <1454010428-29139-1-git-send-email-jeffmerkey@gmail.com>
On Thu, 2016-01-28 at 12:47 -0700, 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: Mark Salter <msalter@redhat.com>
> arch/c6x/include/asm/kdebug.h | 4 ++++
> 1 file changed, 4 insertions(+)
> create mode 100644 arch/c6x/include/asm/kdebug.h
>
> diff --git a/arch/c6x/include/asm/kdebug.h b/arch/c6x/include/asm/kdebug.h
> new file mode 100644
> index 0000000..5d09de1
> --- /dev/null
> +++ b/arch/c6x/include/asm/kdebug.h
> @@ -0,0 +1,4 @@
> +
> +static inline void arch_breakpoint(void)
> +{
> +}
prev parent reply other threads:[~2016-02-11 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:47 [PATCH 18/31] Add debugger entry points for C6X Jeffrey Merkey
2016-02-11 22:52 ` Mark Salter [this message]
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=1455231177.3767.62.camel@redhat.com \
--to=msalter@redhat.com \
--cc=a-jacquiot@ti.com \
--cc=jeffmerkey@gmail.com \
--cc=linux-c6x-dev@linux-c6x.org \
--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;
as well as URLs for NNTP newsgroup(s).