public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Mike Travis <travis@sgi.com>
Cc: 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>,
	Hedi Berriche <hedi@sgi.com>, Russ Anderson <rja@sgi.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] KGDB/KDB/UV: Fixups for UV to KGDB interface
Date: Tue, 14 Jan 2014 17:28:43 +0100	[thread overview]
Message-ID: <20140114162843.GB31734@gmail.com> (raw)
In-Reply-To: <20140114162551.093907830@asylum.americas.sgi.com>


* Mike Travis <travis@sgi.com> wrote:

> 
> v2: Update patch 2/3 to include which problems fixed.  Other minor
>   changes detailed in the patches.
> 
> * 1/3: Change the fix for 'KDB not defined' build problem by changing
>   the kgdb_nmicallin() interface to include the KDB specific reason code.
>   This removes the dependency on KDB in the debug core.  It also requires
>   a change to the kgdb call in from UV NMI handler to avoid a compile
>   error.
> 
> * 2/3: Fix problems found by the kbuild test robot tip-bot:
>   Make uv_register_nmi_notifier() and uv_handle_nmi_ping() static to
>   address sparse warnings.  Fix problem where uv_nmi_kexec_failed is
>   unused when CONFIG_KEXEC is not defined.
> 
> * 3/3: 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 the kernel to wait for
>   gdb to be connected.  If it's set to 'kdb' then an error message is
>   displayed if KDB is not configured.
> 
>   Also note that if both KGDB and KDB are enabled, then the action
>   of 'kgdb' or 'kdb' has no affect on which is used.  See the KGDB
>   documentation for further information.

So unless Jason objects I plan to merge these bits in a day or two, 
for a v3.14 merge (if they pass all review and testing).

Thanks,

	Ingo

      parent reply	other threads:[~2014-01-14 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 16:25 [PATCH 0/3] KGDB/KDB/UV: Fixups for UV to KGDB interface Mike Travis
2014-01-14 16:25 ` [PATCH 1/3] KGDB/KDB: Fix no KDB config problem v2 Mike Travis
2014-01-25 14:24   ` [tip:core/urgent] kgdb/kdb: Fix no KDB config problem tip-bot for Mike Travis
2014-01-14 16:25 ` [PATCH 2/3] UV/NMI: Fix tip/bot/kbuild test robot problems v2 Mike Travis
2014-01-25 14:24   ` [tip:core/urgent] x86/uv/nmi: Fix Sparse warnings tip-bot for Mike Travis
2014-01-14 16:25 ` [PATCH 3/3] UV/NMI/KGDB/KDB: Fix UV NMI handler when KDB not configured v2 Mike Travis
2014-01-25 14:24   ` [tip:core/urgent] x86/uv/nmi, kgdb/kdb: Fix UV NMI handler when KDB not configured tip-bot for Mike Travis
2014-01-14 16:28 ` Ingo Molnar [this message]

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=20140114162843.GB31734@gmail.com \
    --to=mingo@kernel.org \
    --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=rja@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=travis@sgi.com \
    --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