From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@redhat.com>,
Jason Wessel <jason.wessel@windriver.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Hedi Berriche <hedi@sgi.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] : KGDB/KDB/UV updates.
Date: Fri, 18 Oct 2013 13:53:34 -0500 [thread overview]
Message-ID: <20131018185334.272062791@asylum.americas.sgi.com> (raw)
* Change the fix for KDB not defined build problem by changing
the kgdb_nmicallin() interface to include the KDB specific
reason code. This removes a dependency on KDB in the debug
core. Also requires a change the call in from UV NMI handler.
* Fix some problems found by the kbuild test robot.
* Fix UV call into kgdb to depend only on whether KGDB is defined
and not both KGDB and KDB. This allows the power nmi command
to use the gdb remote connection if enabled. Note new action
of 'kgdb' needs to be set as well to indicate user wants to
wait for gdb to be connected. If it's set to 'kdb' then an
error message is displayed if KDB is not configured.
--
--
next reply other threads:[~2013-10-18 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 18:53 Mike Travis [this message]
2013-10-18 18:53 ` [PATCH 1/3] PATCH: KGDB/KDB Fix no KDB config problem Mike Travis
2013-10-18 18:53 ` [PATCH 2/3] PATCH: UV/NMI Fix tip/bot/kbuild test robot problems Mike Travis
2013-10-18 18:53 ` [PATCH 3/3] PATCH: UV/NMI/KGDB/KDB Fix UV NMI handler when KDB not configed Mike Travis
2013-10-19 8:56 ` [PATCH 0/3] : KGDB/KDB/UV updates Ingo Molnar
2014-01-13 18:12 ` Mike Travis
2014-01-13 19:02 ` Ingo Molnar
2014-01-14 4:24 Mike Travis
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=20131018185334.272062791@asylum.americas.sgi.com \
--to=travis@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=hedi@sgi.com \
--cc=hpa@zytor.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=x86@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: 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
all inboxes | Powered by JetHome®