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>,
Nicholas Mc Guire <hofrat@osadl.org>,
Christophe Leroy <christophe.leroy@c-s.fr>
Subject: [GIT PULL] kgdb changes v4.21-rc1
Date: Sun, 30 Dec 2018 10:51:31 +0000 [thread overview]
Message-ID: <20181230105131.GA30811@wychelm.lan> (raw)
Hi Linus
Happy new year!
The following changes since commit 2595646791c319cadfdbf271563aac97d0843dc7:
Linux 4.20-rc5 (2018-12-02 15:07:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/ tags/kgdb-4.21-rc1
for you to fetch changes up to cc0282975b3f887005c380adcf0af95915f0c1bb:
kgdb/treewide: constify struct kgdb_arch arch_kgdb_ops (2018-12-30 08:33:06 +0000)
----------------------------------------------------------------
kgdb patches for 4.20-rc1
Mostly clean ups although whilst Doug's was chasing down a odd
lockdep warning he also did some work to improved debugger resilience
when some CPUs fail to respond to the round up request.
The main changes are:
* Fixing a lockdep warning on architectures that cannot use an NMI for
the round up plus related changes to make CPU round up and all CPU
backtrace more resilient.
* Constify the arch ops tables
* A couple of other small clean ups
Two of the three patchsets here include changes that spill over into
arch/. Changes in the arch space are relatively narrow in scope
(and directly related to kgdb). Didn't get comprehensive acks but
all impacted maintainers were Cc:ed in good time.
Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
----------------------------------------------------------------
Christophe Leroy (2):
mips/kgdb: prepare arch_kgdb_ops for constness
kgdb/treewide: constify struct kgdb_arch arch_kgdb_ops
Douglas Anderson (4):
kgdb: Remove irq flags from roundup
kgdb: Fix kgdb_roundup_cpus() for arches who used smp_call_function()
kgdb: Don't round up a CPU that failed rounding up before
kdb: Don't back trace on a cpu that didn't round up
Nicholas Mc Guire (1):
kdb: use bool for binary state indicators
arch/arc/kernel/kgdb.c | 12 ++------
arch/arm/kernel/kgdb.c | 14 +--------
arch/arm64/kernel/kgdb.c | 14 +--------
arch/h8300/kernel/kgdb.c | 2 +-
arch/hexagon/kernel/kgdb.c | 34 +--------------------
arch/microblaze/kernel/kgdb.c | 2 +-
arch/mips/kernel/kgdb.c | 25 +++++-----------
arch/nios2/kernel/kgdb.c | 2 +-
arch/powerpc/kernel/kgdb.c | 8 ++---
arch/sh/kernel/kgdb.c | 14 +--------
arch/sparc/kernel/kgdb_32.c | 2 +-
arch/sparc/kernel/kgdb_64.c | 2 +-
arch/sparc/kernel/smp_64.c | 2 +-
arch/x86/kernel/kgdb.c | 11 ++-----
include/linux/kgdb.h | 24 +++++++++------
kernel/debug/debug_core.c | 65 ++++++++++++++++++++++++++++++++++++++++-
kernel/debug/debug_core.h | 1 +
kernel/debug/kdb/kdb_bt.c | 11 ++++++-
kernel/debug/kdb/kdb_debugger.c | 7 -----
kernel/debug/kdb/kdb_main.c | 14 ++++-----
20 files changed, 125 insertions(+), 141 deletions(-)
next reply other threads:[~2018-12-30 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 10:51 Daniel Thompson [this message]
2019-01-02 0:35 ` [GIT PULL] kgdb changes v4.21-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=20181230105131.GA30811@wychelm.lan \
--to=daniel.thompson@linaro.org \
--cc=christophe.leroy@c-s.fr \
--cc=dianders@chromium.org \
--cc=hofrat@osadl.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