From: Wei Li <liwei391@huawei.com> To: <daniel.thompson@linaro.org>, <jason.wessel@windriver.com>, <dianders@chromium.org>, <maz@kernel.org>, <mark.rutland@arm.com>, <mhiramat@kernel.org>, <davem@davemloft.net>, <will@kernel.org>, <catalin.marinas@arm.com> Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <liwei1412@163.com> Subject: [PATCH 0/4] arm64: kgdb/kdb: Fix single-step debugging issues Date: Sun, 10 May 2020 05:41:55 +0800 [thread overview] Message-ID: <20200509214159.19680-1-liwei391@huawei.com> (raw) This patch set is to fix several issues of single-step debugging in kgdb/kdb on arm64. It seems that these issues have been shelved a very long time, but i still hope to solve them, as the single-step debugging is an useful feature. Note: Based on patch "arm64: cacheflush: Fix KGDB trap detection", https://www.spinics.net/lists/arm-kernel/msg803741.html Wei Li (4): arm64: kgdb: Fix single-step exception handling oops arm64: Extract kprobes_save_local_irqflag() and kprobes_restore_local_irqflag() arm64: kgdb: Fix single-stepping into the irq handler wrongly arm64: kgdb: Set PSTATE.SS to 1 to reenable single-step arch/arm64/include/asm/debug-monitors.h | 6 ++++++ arch/arm64/kernel/debug-monitors.c | 28 ++++++++++++++++++++++++- arch/arm64/kernel/kgdb.c | 16 +++++++++++--- arch/arm64/kernel/probes/kprobes.c | 28 ++----------------------- 4 files changed, 48 insertions(+), 30 deletions(-) -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Wei Li <liwei391@huawei.com> To: <daniel.thompson@linaro.org>, <jason.wessel@windriver.com>, <dianders@chromium.org>, <maz@kernel.org>, <mark.rutland@arm.com>, <mhiramat@kernel.org>, <davem@davemloft.net>, <will@kernel.org>, <catalin.marinas@arm.com> Cc: liwei1412@163.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/4] arm64: kgdb/kdb: Fix single-step debugging issues Date: Sun, 10 May 2020 05:41:55 +0800 [thread overview] Message-ID: <20200509214159.19680-1-liwei391@huawei.com> (raw) This patch set is to fix several issues of single-step debugging in kgdb/kdb on arm64. It seems that these issues have been shelved a very long time, but i still hope to solve them, as the single-step debugging is an useful feature. Note: Based on patch "arm64: cacheflush: Fix KGDB trap detection", https://www.spinics.net/lists/arm-kernel/msg803741.html Wei Li (4): arm64: kgdb: Fix single-step exception handling oops arm64: Extract kprobes_save_local_irqflag() and kprobes_restore_local_irqflag() arm64: kgdb: Fix single-stepping into the irq handler wrongly arm64: kgdb: Set PSTATE.SS to 1 to reenable single-step arch/arm64/include/asm/debug-monitors.h | 6 ++++++ arch/arm64/kernel/debug-monitors.c | 28 ++++++++++++++++++++++++- arch/arm64/kernel/kgdb.c | 16 +++++++++++--- arch/arm64/kernel/probes/kprobes.c | 28 ++----------------------- 4 files changed, 48 insertions(+), 30 deletions(-) -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-05-09 13:49 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-09 21:41 Wei Li [this message] 2020-05-09 21:41 ` [PATCH 0/4] arm64: kgdb/kdb: Fix single-step debugging issues Wei Li 2020-05-09 21:41 ` [PATCH 1/4] arm64: kgdb: Fix single-step exception handling oops Wei Li 2020-05-09 21:41 ` Wei Li 2020-05-14 0:21 ` Doug Anderson 2020-05-14 0:21 ` Doug Anderson 2020-05-09 21:41 ` [PATCH 2/4] arm64: Extract kprobes_save_local_irqflag() and kprobes_restore_local_irqflag() Wei Li 2020-05-09 21:41 ` Wei Li 2020-05-10 8:59 ` Masami Hiramatsu 2020-05-10 8:59 ` Masami Hiramatsu 2020-05-14 0:21 ` Doug Anderson 2020-05-14 0:21 ` Doug Anderson 2020-05-16 8:47 ` liwei (GF) 2020-05-16 8:47 ` liwei (GF) 2020-05-16 16:17 ` Doug Anderson 2020-05-16 16:17 ` Doug Anderson 2020-05-18 15:14 ` Masami Hiramatsu 2020-05-18 15:14 ` Masami Hiramatsu 2020-05-09 21:41 ` [PATCH 3/4] arm64: kgdb: Fix single-stepping into the irq handler wrongly Wei Li 2020-05-09 21:41 ` Wei Li 2020-05-14 0:21 ` Doug Anderson 2020-05-14 0:21 ` Doug Anderson 2020-05-09 21:41 ` [PATCH 4/4] arm64: kgdb: Set PSTATE.SS to 1 to reenable single-step Wei Li 2020-05-09 21:41 ` Wei Li 2020-05-14 0:23 ` Doug Anderson 2020-05-14 0:23 ` Doug Anderson 2020-05-16 8:20 ` liwei (GF) 2020-05-16 8:20 ` liwei (GF) 2020-05-14 0:34 ` [PATCH 0/4] arm64: kgdb/kdb: Fix single-step debugging issues Doug Anderson 2020-05-14 0:34 ` Doug Anderson 2020-05-16 8:20 ` liwei (GF) 2020-05-16 8:20 ` liwei (GF) 2020-06-29 21:20 ` Doug Anderson 2020-06-29 21:20 ` Doug Anderson 2020-06-30 7:22 ` Will Deacon 2020-06-30 7:22 ` Will Deacon 2020-07-06 21:37 ` Doug Anderson 2020-07-06 21:37 ` Doug Anderson 2020-07-08 22:06 ` Will Deacon 2020-07-08 22:06 ` Will Deacon 2020-07-08 22:22 ` Doug Anderson 2020-07-08 22:22 ` Doug Anderson 2020-07-07 1:37 ` liwei (GF) 2020-07-07 1:37 ` liwei (GF) 2020-07-08 22:02 ` Will Deacon 2020-07-08 22:02 ` Will Deacon
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=20200509214159.19680-1-liwei391@huawei.com \ --to=liwei391@huawei.com \ --cc=catalin.marinas@arm.com \ --cc=daniel.thompson@linaro.org \ --cc=davem@davemloft.net \ --cc=dianders@chromium.org \ --cc=jason.wessel@windriver.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=liwei1412@163.com \ --cc=mark.rutland@arm.com \ --cc=maz@kernel.org \ --cc=mhiramat@kernel.org \ --cc=will@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: linkBe 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.