linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 0/3] AArch64: KGDB support
Date: Tue, 7 Jan 2014 12:11:47 +0000	[thread overview]
Message-ID: <20140107121147.GE29456@arm.com> (raw)
In-Reply-To: <20140106181201.GE1096@mudshark.cambridge.arm.com>

On Mon, Jan 06, 2014 at 06:12:01PM +0000, Will Deacon wrote:
> On Thu, Dec 19, 2013 at 11:50:48AM +0000, vijay.kilari at gmail.com wrote:
> > From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
> > 
> > Based on the step-handler and break-handler hooks patch from
> > Sandeepa, KGDB debugging support is added for EL1
> > debug in AArch64 mode. Any updates that come for Patch 1 from
> > Sandeepa will be rebased in next version
> > 
> > With second patch,register layout is updated to be inline with GDB tool.
> > Basic GDB connection, break point set/clear and info commands
> > are supported except step/next debugging
> > 
> > With third patch, step/next debugging support is added, where in
> > pc is updated to point to the instruction to be stepped and
> > stopped.
> > 
> > With fourth patch, the compile time breakpoint instruction
> > reordering is fixed by making kgbd_breakpoint() as noinline
> > 
> > Tested with ARM64 simulator
> > 
> > v6:
> >  - Change pstate register to 8 bytes to make endian nuetral.
> >    Use GDB below GDB patch to display pstate in Big endian mode.
> >    https://sourceware.org/ml/gdb-patches/2013-12/msg00720.html
> >    Thanks to Andrew.
> 
> Thanks for getting this new version out. Just a few things before it can be
> applied:
> 
>   1. Can you please use "arm64:" instead of "AArch64:" in the patch
>      subjects?
> 
>   2. Can you get an ack from somebody like Jason on the final patch please?
> 
>   3. Can you rebase onto the for-next/core branch at the arm64 repo:
> 
>        git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> 
>      you'll get a trivial conflict against arch/arm64/kernel/Makefile.

Just to be clear here, I would only recommend rebasing on top of this
branch if there are patches queued for upstream which are required by
the rebased patches and there isn't a topic branch already elsewhere. I
do *not* recommend this branch for any kind of development (though
testing is fine and we can fix the trivial Makefile conflicts
ourselves).

>   4. Can you make sure that the gdb patch you linked to actually gets
>      merged? There is still some discussion by the looks of it.

I guess the kernel patches will have to wait for the binutils patch to
go in. BTW, does this mean that kgdb on arm64 will only work with a
future version of gdb?

-- 
Catalin

  reply	other threads:[~2014-01-07 12:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 11:50 [PATCH v6 0/3] AArch64: KGDB support vijay.kilari at gmail.com
2013-12-19 11:50 ` [PATCH v6 1/3] AArch64: KGDB: Add Basic " vijay.kilari at gmail.com
2014-01-16 13:47   ` Catalin Marinas
2013-12-19 11:50 ` [PATCH v6 2/3] AArch64: KGDB: Add step debugging support vijay.kilari at gmail.com
2013-12-19 11:50 ` [PATCH v6 3/3] KGDB: make kgdb_breakpoint() as noinline vijay.kilari at gmail.com
2014-01-15 16:44   ` Jason Wessel
2014-01-15 16:48     ` Will Deacon
2014-01-06 18:12 ` [PATCH v6 0/3] AArch64: KGDB support Will Deacon
2014-01-07 12:11   ` Catalin Marinas [this message]
2014-01-15 10:17     ` Vijay Kilari
2014-01-15 23:31   ` Andrew Pinski
2014-01-16 13:45 ` Catalin Marinas
2014-01-18  8:02   ` Vijay Kilari
2014-01-20 10:23     ` Will Deacon
     [not found]       ` <CALicx6v-pxOxdx4Q+a_Rx4XdHPXvgbVoYuouJoBxRdENMzCvAA@mail.gmail.com>
     [not found]         ` <20140121183604.GQ30706@mudshark.cambridge.arm.com>
2014-01-22  4:31           ` Vijay Kilari
2014-01-22  7:50             ` Vijay Kilari
2014-01-22 10:31               ` Will Deacon
2014-01-22 14:54     ` 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=20140107121147.GE29456@arm.com \
    --to=catalin.marinas@arm.com \
    --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 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).