All of lore.kernel.org
 help / color / mirror / Atom feed
From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/4] AArch64: KGDB: Add step debugging support
Date: Thu, 31 Oct 2013 11:35:58 +0900	[thread overview]
Message-ID: <5271C20E.4020104@linaro.org> (raw)
In-Reply-To: <1382094469-7971-4-git-send-email-vijay.kilari@gmail.com>

Hi,

On 10/18/2013 08:07 PM, vijay.kilari at gmail.com wrote:
> From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>
> Add KGDB software step debugging support for EL1 debug
> in AArch64 mode.
>
> diff --git a/arch/arm64/kernel/kgdb.c b/arch/arm64/kernel/kgdb.c
> index 50cef79..2b0b987 100644
> --- a/arch/arm64/kernel/kgdb.c
> +++ b/arch/arm64/kernel/kgdb.c
 > ...
>   int kgdb_arch_handle_exception(int exception_vector, int signo,
>   			       int err_code, char *remcom_in_buffer,
>   			       char *remcom_out_buffer,
>   			       struct pt_regs *linux_regs)
>   {
 > ...
> +	case 's':
> +		/*
> +		 * Update step address value with address passed
> +		 * with step packet.
> +		 * On debug exception return PC is copied to ELR
> +		 * So just update PC.
> +		 * If no step address is passed, resume from the address
> +		 * pointed by PC. Do not update PC
> +		 */
> +		kgdb_arch_update_addr(linux_regs, remcom_in_buffer);
>
> +		/*
> +		 * Enable single step handling
> +		 */
> +		if (!kernel_active_single_step())
> +			kernel_enable_single_step(linux_regs);
>   		err = 0;
>   		break;
>   	default:

Other architectures handle the state, by modifying kgdb_single_step or
kgdb_cpu_doing_single_step, when entering into or exiting from single
step mode.

Do you have a good reason that you don't need to do so on arm64?
(I'm just asking because my own kgdb patch follows the way that x86 does.)

-Takahiro AKASHI

  parent reply	other threads:[~2013-10-31  2:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 11:07 [PATCH v3 0/4] : AArch64: KGDB support vijay.kilari at gmail.com
2013-10-18 11:07 ` [PATCH v3 1/4] arm64: support single-step and breakpoint handler hooks vijay.kilari at gmail.com
2013-10-18 11:07 ` [PATCH v3 2/4] AArch64: KGDB: Add Basic KGDB support vijay.kilari at gmail.com
2013-10-31  0:23   ` Will Deacon
2013-11-04  6:55     ` Vijay Kilari
2013-10-31  2:21   ` AKASHI Takahiro
2013-11-04 10:53     ` Vijay Kilari
2013-10-18 11:07 ` [PATCH v3 3/4] AArch64: KGDB: Add step debugging support vijay.kilari at gmail.com
2013-10-31  0:27   ` Will Deacon
2013-10-31  2:35   ` AKASHI Takahiro [this message]
2013-11-04 11:21     ` Vijay Kilari
2013-10-18 11:07 ` [PATCH v3 4/4] KGDB: make kgdb_breakpoint() as noinline vijay.kilari at gmail.com
2013-10-25 15:40   ` Will Deacon
2013-10-29  5:12     ` Vijay Kilari

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=5271C20E.4020104@linaro.org \
    --to=takahiro.akashi@linaro.org \
    --cc=linux-arm-kernel@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.