From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wl@xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Tim Deegan" <tim@xen.org>, "Julien Grall" <julien.grall@arm.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [Xen-devel] [PATCH v4 0/5] enhance lock debugging
Date: Mon, 9 Sep 2019 16:31:29 +0200 [thread overview]
Message-ID: <20190909143134.15379-1-jgross@suse.com> (raw)
While hunting a locking problem in my core scheduling series I have
added some debugging aids to spinlock handling making it easier to
find the root cause for the problem.
Making use of the already existing lock profiling and enhancing it a
little bit produces some really valuable diagnostic data e.g. when a
NMI watchdog is triggering a crash.
Changes in V4:
- some comments by Jan Beulich addressed
- replaced patch 5 with another approach to make lock names unique
Changes in V3:
- rebase to current staging (after realizing that patch 4 still
applied, but resulting in patching a wrong function)
Changes in V2:
- multiple comments addressed
- added patch 5
Juergen Gross (5):
xen/spinlocks: in debug builds store cpu holding the lock
xen: add new CONFIG_DEBUG_LOCKS option
xen: print lock profile info in panic()
xen: modify lock profiling interface
xen: add function name to lock profiling data
tools/libxc/xc_misc.c | 1 +
tools/misc/xenlockprof.c | 17 +---
xen/Kconfig.debug | 10 ++-
xen/arch/arm/xen.lds.S | 13 ++--
xen/arch/x86/domain.c | 2 +-
xen/arch/x86/xen.lds.S | 13 ++--
xen/common/domain.c | 4 +-
xen/common/keyhandler.c | 2 +-
xen/common/spinlock.c | 185 ++++++++++++++++++++++++++++++++------------
xen/common/sysctl.c | 2 +-
xen/drivers/char/console.c | 4 +-
xen/include/public/sysctl.h | 11 +--
xen/include/xen/spinlock.h | 75 +++++++++++-------
13 files changed, 221 insertions(+), 118 deletions(-)
--
2.16.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-09-09 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 14:31 Juergen Gross [this message]
2019-09-09 14:31 ` [Xen-devel] [PATCH v4 1/5] xen/spinlocks: in debug builds store cpu holding the lock Juergen Gross
2019-09-09 14:50 ` Jan Beulich
2019-09-09 14:56 ` Juergen Gross
2019-09-09 14:31 ` [Xen-devel] [PATCH v4 2/5] xen: add new CONFIG_DEBUG_LOCKS option Juergen Gross
2019-09-09 14:31 ` [Xen-devel] [PATCH v4 3/5] xen: print lock profile info in panic() Juergen Gross
2019-09-09 14:31 ` [Xen-devel] [PATCH v4 4/5] xen: modify lock profiling interface Juergen Gross
2019-09-09 14:31 ` [Xen-devel] [PATCH v4 5/5] xen: add function name to lock profiling data Juergen Gross
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=20190909143134.15379-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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.