From: takahiro.akashi@linaro.org (AKASHI Takahiro)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] arm64: kgdb: fix single stepping
Date: Fri, 23 Sep 2016 17:32:58 +0900 [thread overview]
Message-ID: <20160923083257.GL30248@linaro.org> (raw)
In-Reply-To: <20160923081618.GH18056@kroah.com>
On Fri, Sep 23, 2016 at 10:16:18AM +0200, Greg KH wrote:
> On Fri, Sep 23, 2016 at 04:33:24PM +0900, AKASHI Takahiro wrote:
> > Kgdb support on arm64 was merged in v3.15, but from its first appearance,
> > "signle step" has never worked well.
> >
> > This patch fixes all the error cases I found so far.
> > The original patch[1] was splitted into three pieces, ones for each case.
> > patch#1, #2 should be applied to all the version, v3.15 and later.
> > pathc#3 only for v3.16 and later.
>
> As this is not a regression (i.e. it has never worked), why is this
> something for stable releases?
Because, I think, that is a bug.
The author seems to have believed that it worked.
Please see:
commit 44679a4f
Author: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
Date: Tue Jan 28 11:20:19 2014 +0000
arm64: KGDB: Add step debugging support
Thanks,
-Takahiro AKASHI
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2016-09-23 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 7:33 [PATCH v2 0/3] arm64: kgdb: fix single stepping AKASHI Takahiro
2016-09-23 7:33 ` [PATCH v2 1/3] " AKASHI Takahiro
2016-09-23 7:33 ` [PATCH v2 2/3] arm64: kgdb: prevent kgdb from being invoked recursively AKASHI Takahiro
2016-09-23 10:02 ` Will Deacon
2016-09-23 7:33 ` [PATCH v2 3/3] arm64: kgdb: disable interrupts while a software step is enabled AKASHI Takahiro
2016-09-23 8:16 ` [PATCH v2 0/3] arm64: kgdb: fix single stepping Greg KH
2016-09-23 8:32 ` AKASHI Takahiro [this message]
2016-09-23 8:43 ` Greg KH
2016-09-23 9:27 ` AKASHI Takahiro
2016-09-23 9:23 ` Greg KH
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=20160923083257.GL30248@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 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).