All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
	linux.mdb@gmail.com, sparclinux@vger.kernel.org
Subject: Re: [PATCH 30/31] Add debugger entry points for SPARC
Date: Thu, 28 Jan 2016 21:33:21 +0000	[thread overview]
Message-ID: <20160128213321.GA32054@ravnborg.org> (raw)
In-Reply-To: <1454010468-29651-1-git-send-email-jeffmerkey@gmail.com>

Hi Jeff.

> +++ b/arch/sparc/include/asm/kdebug.h
> @@ -5,4 +5,9 @@
>  #else
>  #include <asm/kdebug_32.h>
>  #endif
> +
> +static inline void arch_breakpoint(void)
> +{
> +	asm("ta	$0x7d");
> +}
>  #endif
There seems to be some debugger infrastructure present already for kgdb,
but I assume this cannot be used.
Anyway - trap 0x7d is a debugger trap in sparc32.
If CONFIG_KGDB is not defined then 0x7d is just a regular BAD_TRAP.

For sparc64 trap 0x7d is something different.
I did not conclude what was the right choice for neither.

	Sam

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
	linux.mdb@gmail.com, sparclinux@vger.kernel.org
Subject: Re: [PATCH 30/31] Add debugger entry points for SPARC
Date: Thu, 28 Jan 2016 22:33:21 +0100	[thread overview]
Message-ID: <20160128213321.GA32054@ravnborg.org> (raw)
In-Reply-To: <1454010468-29651-1-git-send-email-jeffmerkey@gmail.com>

Hi Jeff.

> +++ b/arch/sparc/include/asm/kdebug.h
> @@ -5,4 +5,9 @@
>  #else
>  #include <asm/kdebug_32.h>
>  #endif
> +
> +static inline void arch_breakpoint(void)
> +{
> +	asm("ta	$0x7d");
> +}
>  #endif
There seems to be some debugger infrastructure present already for kgdb,
but I assume this cannot be used.
Anyway - trap 0x7d is a debugger trap in sparc32.
If CONFIG_KGDB is not defined then 0x7d is just a regular BAD_TRAP.

For sparc64 trap 0x7d is something different.
I did not conclude what was the right choice for neither.

	Sam

  parent reply	other threads:[~2016-01-28 21:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 19:47 [PATCH 30/31] Add debugger entry points for SPARC Jeffrey Merkey
2016-01-28 19:47 ` Jeffrey Merkey
2016-01-28 21:32 ` kbuild test robot
2016-01-28 21:32   ` kbuild test robot
2016-01-28 21:33 ` Sam Ravnborg [this message]
2016-01-28 21:33   ` Sam Ravnborg
2016-01-28 21:35   ` Jeffrey Merkey
2016-01-28 21:35     ` Jeffrey Merkey
2016-01-28 21:44 ` kbuild test robot
2016-01-28 21:44   ` kbuild test robot

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=20160128213321.GA32054@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --cc=jeffmerkey@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.mdb@gmail.com \
    --cc=sparclinux@vger.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.