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 <wei.liu2@citrix.com>,
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>
Subject: [PATCH 0/2] xen: some debug trace enhancements
Date: Thu, 14 Mar 2019 10:37:31 +0100 [thread overview]
Message-ID: <20190314093733.18175-1-jgross@suse.com> (raw)
While doing some scheduler work I used debug trace for diagnosis of
problems during dom0 boot. This small series is the result of adapting
debug trace to my needs.
Juergen Gross (2):
xen/debug: make debugtrace configurable via Kconfig
xen/debug: make debugtrace more clever regarding repeating entries
xen/Kconfig.debug | 7 +++++++
xen/drivers/char/console.c | 46 ++++++++++++++++++++++++++++++++++------------
xen/include/xen/lib.h | 3 +--
3 files changed, 42 insertions(+), 14 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-03-14 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 9:37 Juergen Gross [this message]
2019-03-14 9:37 ` [PATCH 1/2] xen/debug: make debugtrace configurable via Kconfig Juergen Gross
2019-03-14 13:26 ` Jan Beulich
2019-03-14 9:37 ` [PATCH 2/2] xen/debug: make debugtrace more clever regarding repeating entries Juergen Gross
2019-03-14 13:33 ` Jan Beulich
[not found] ` <5C8A5842020000780021EA3E@suse.com>
2019-03-14 13:38 ` Juergen Gross
2019-03-14 13:40 ` Andrew Cooper
2019-03-14 14:14 ` Jan Beulich
[not found] ` <5C8A61CB020000780021EB19@suse.com>
2019-03-14 14:28 ` Juergen Gross
2019-03-14 14:31 ` Jan Beulich
[not found] <20190314093733.18175*1*jgross@suse.com>
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=20190314093733.18175-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.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=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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.