From: Daniel Thompson <daniel.thompson@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
linux-kernel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>
Subject: [GIT PULL] kgdb changes v5.5-rc1
Date: Tue, 26 Nov 2019 15:38:58 +0000 [thread overview]
Message-ID: <20191126153858.bclidzxinfjrtkl6@holly.lan> (raw)
The following changes since commit da0c9ea146cbe92b832f1b0f694840ea8eb33cce:
Linux 5.4-rc2 (2019-10-06 14:27:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/ tags/kgdb-5.5-rc1
for you to fetch changes up to c58ff643763c78bef12874ee39995c9f7f987bc2:
kdb: Tweak escape handling for vi users (2019-10-28 12:08:29 +0000)
----------------------------------------------------------------
kgdb patches for 5.5-rc1
The major change here is the work from Douglas Anderson that
reworks the way kdb stack traces are handled on SMP systems.
The effect is to allow all CPUs to issue their stack trace which
reduced the need for architecture specific code to support stack
tracing.
Also included are general of clean ups from Doug and myself:
* Remove some unused variables or arguments.
* Tidy up the kdb escape handling code and fix a couple of odd
corner cases.
- Better ignore escape characters that do not form part of an
escape sequence. This mostly benefits vi users since they are most
likely to press escape as a nervous habit but it won't harm anyone
else.
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
----------------------------------------------------------------
Daniel Thompson (6):
kdb: Avoid array subscript warnings on non-SMP builds
kdb: Tidy up code to handle escape sequences
kdb: Simplify code to fetch characters from console
kdb: Remove special case logic from kdb_read()
kdb: Improve handling of characters from different input sources
kdb: Tweak escape handling for vi users
Douglas Anderson (4):
kgdb: Remove unused DCPU_SSTEP definition
kdb: Remove unused "argcount" param from kdb_bt1(); make btaprompt bool
kdb: Fix "btc <cpu>" crash if the CPU didn't round up
kdb: Fix stack crawling on 'running' CPUs that aren't the master
kernel/debug/debug_core.c | 34 ++++++
kernel/debug/debug_core.h | 3 +-
kernel/debug/kdb/kdb_bt.c | 116 +++++++++++----------
kernel/debug/kdb/kdb_io.c | 231 ++++++++++++++++++++---------------------
kernel/debug/kdb/kdb_private.h | 1 +
5 files changed, 208 insertions(+), 177 deletions(-)
next reply other threads:[~2019-11-26 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 15:38 Daniel Thompson [this message]
2019-12-01 1:40 ` [GIT PULL] kgdb changes v5.5-rc1 pr-tracker-bot
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=20191126153858.bclidzxinfjrtkl6@holly.lan \
--to=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).