[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <501756A0.4080405@windriver.com>
Date: Mon, 30 Jul 2012 22:53:04 -0500
From: Jason Wessel <jason.wessel@...driver.com>
To: Anton Vorontsov <anton.vorontsov@...aro.org>
CC: Russell King <linux@....linux.org.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Cox <alan@...ux.intel.com>,
Arve Hjønnevåg <arve@...roid.com>,
Colin Cross <ccross@...roid.com>,
John Stultz <john.stultz@...aro.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linaro-kernel@...ts.linaro.org>, <patches@...aro.org>,
<kernel-team@...roid.com>, <kgdb-bugreport@...ts.sourceforge.net>
Subject: Re: [PATCH 01/11] kernel/debug: Make use of KGDB_REASON_NMI
On 07/30/2012 06:58 AM, Anton Vorontsov wrote:
> Currently kernel never set KGDB_REASON_NMI. We do now, when we enter
> KGDB/KDB from an NMI.
>
> This is not to be confused with kgdb_nmicallback(), NMI callback is
> an entry for the slave CPUs during CPUs roundup, but REASON_NMI is the
> entry for the master CPU.
No need for confusion here :-)
I'll take this one for the kernel merge window if it passes regression tests, no reason not to be setting the stop codes properly.
Thanks,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists