On 3/22/21 2:22 PM, Doug Anderson wrote:
Hi,
On Mon, Mar 22, 2021 at 11:19 AM Arnd Bergmann wrote:
On Mon, Mar 22, 2021 at 6:07 PM Doug Anderson wrote:
On Mon, Mar 22, 2021 at 9:43 AM Arnd Bergmann wrote:
-#define v1printk(a...) do { \
- if (verbose) \
- printk(KER
stage it looks better to stop carrying this code in
the kernel and integrate the code into the out-of-tree driver
instead.
Because it has no in tree users, it absolutely makes the most
sense to purge this function.
Acked-by: Jason Wessel
The long term trajectory for the kernel looks likely to in
We'll have to fix them at some point.
Acked-by: Jason Wessel
Cheers,
Jason.
On 2/26/19 1:16 PM, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warnings:
kernel/
On 09/28/2018 07:57 AM, Michael Ellerman wrote:
Christophe LEROY writes:
Le 27/09/2018 à 13:09, Michael Ellerman a écrit :
Christophe LEROY writes:
Le 26/09/2018 à 13:11, Daniel Thompson a écrit :
The Fixes: and now your Reviewed-by: appear automatically in patchwork
(https://patchwork.ozla
Linus,
Please pull the kgdb tree.
Summary of changes:
* Fix 2032 time access issues and new compiler warnings
* minor regression test cleanup
* formatting fixes for end user use of kdb
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git
tags/for_linus-4.16
Thanks,
Jason.
-
_name_table+i, kdb_name_table+i+1,
+ memmove(kdb_name_table+i, kdb_name_table+i+1,
sizeof(kdb_name_table[0]) *
(ARRAY_SIZE(kdb_name_table)-i-1));
}
That is good by me. Many thanks! Added to queue.
Reviewed-by: Jason Wessel
Jason.
On 01/30/2018 07:35 AM, Arnd Bergmann wrote:
On Mon, Jan 29, 2018 at 3:22 AM, Baolin Wang wrote:
The kdb code will print the monotonic time by ktime_get_ts(), but
the ktime_get_ts() will be protected by a sequence lock, that will
introduce one deadlock risk if the lock was already held in the
c
is only interested in the second field, we can use the
ktime_get_seconds() to get the monotonic time without a lock,
moreover we can remove the 'struct timespec', which is not y2038
safe.
Signed-off-by: Baolin Wang
Acked-by: Jason Wessel
Thanks. Added to the kgdb-next branch fo
On 01/25/2018 05:38 AM, Daniel Thompson wrote:
On Thu, Jan 25, 2018 at 05:18:54PM +0800, Baolin Wang wrote:
On 25 January 2018 at 16:55, Arnd Bergmann wrote:
On Thu, Jan 25, 2018 at 9:05 AM, Baolin Wang wrote:
@@ -2554,7 +2554,7 @@ static int kdb_summary(int argc, const char **argv)
On 12/12/2017 06:10 AM, Daniel Thompson wrote:
kgdbts includes a couple of different "thrashing" style tests that
may have long runtimes (especially on simulated platforms) and which
run asynchronously. This is uncomfortable for interactive use and
makes setting timeouts tricky for automatic use.
, including the newline character. This
causes the ending single-quote mark to be printed on the next line
by itself, so just change the ending newline character to a null
character (end of string) so that it won't be "printed."
Signed-off-by: Randy Dunlap
Cc: Daniel Thompson
Cc:
On 12/06/2017 06:52 PM, Randy Dunlap wrote:
On 12/06/2017 02:33 PM, Jason Wessel wrote:
L:kgdb-bugrep...@lists.sourceforge.net
T:git git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git
I would urge you to move to a different mailing list server.
No argument here
On 12/05/2017 10:42 AM, Randy Dunlap wrote:
On 12/05/2017 06:55 AM, Daniel Thompson wrote:
On 05/12/17 14:37, Jason Wessel wrote:
I have a series of 50+ patches for kgdb/kdb/usb which have never been
published. I am not saying that we actually need any of those patches, but it
would be nice
Daniel Thompson (1):
kdb: Fix handling of kallsyms_symbol_next() return value
Jason Wessel (1):
kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson
MAINTAINERS | 1 +
kernel/debug/kdb/kdb_io.c | 2 +-
2 files changed
a WARN_ON().
Reported-by: Dan Carpenter
Signed-off-by: Daniel Thompson
Cc: linux-stable
Signed-off-by: Jason Wessel
---
kernel/debug/kdb/kdb_io.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/debug/kdb/kdb_io.c b/kernel/debug/kdb/kdb_io.c
index e74be38..ed5d349
Signed-off-by: Jason Wessel
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2811a21..74be63b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7659,6 +7659,7 @@ F:security/keys/
KGDB / KDB /debug_core
M: Jason Wessel
+M
ifference was that I added a comment
about the __ktime_get_real_seconds() not taking the lock because it was done
that way in other places in the header file.
===
extern time64_t ktime_get_real_seconds(void);
+/* does not take xtime_lock */
+extern time64_t __ktime_get_real_seconds(void);
On 10/13/2017 03:26 AM, Daniel Thompson wrote:
On 12/10/17 23:40, Andrew Morton wrote:
On Thu, 12 Oct 2017 16:06:11 +0200 Arnd Bergmann wrote:
kdb is the only user of the __current_kernel_time() interface, which is
not y2038 safe and should be removed at some point.
The kdb code also goes to
On 12/05/2017 08:09 AM, Lee Jones wrote:
On Tue, 05 Dec 2017, Daniel Thompson wrote:
... with many, many thanks for Jason for all his hard work.
Cc: Jason Wessel
Signed-off-by: Daniel Thompson
---
Notes:
Over the years Jason has become increasingly hard to get hold off
and I
On 11/17/2016 01:16 PM, Brian Norris wrote:
Hi,
I've been poking around KGDB, and I noticed that the KDB 'ftdump'
command (to dump ftrace logs) produces warnings like this:
(gdb) monitor ftdump
Dumping ftrace buffer:
BUG: sleeping function called from invalid context at mm/slab.h:359
in_atomic(
On 09/15/2016 11:32 PM, AKASHI Takahiro wrote:
@@ -176,18 +183,14 @@ int kgdb_arch_handle_exception(int exception_vector, int
signo,
* over and over again.
*/
kgdb_arch_update_addr(linux_regs, remcom_in_buffer);
- atomic_set(&kgdb_
On 09/16/2016 02:45 AM, Will Deacon wrote:
On Fri, Sep 16, 2016 at 01:32:19PM +0900, AKASHI Takahiro wrote:
On Thu, Sep 15, 2016 at 08:04:57AM -0500, Jason Wessel wrote:
I added the patch to kgdb-next after fixing up the context since it no
longer applied to the mainline (
https
On 04/20/2015 08:13 PM, AKASHI Takahiro wrote:
Jason,
Could you please review my patch below?
See also arm64 maintainer's comment:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313712.html
Thanks,
-Takahiro AKASHI
I tried to verify kgdb in vanilla kernel on fast model, but
On 09/15/2016 05:41 AM, Daniel Thompson wrote:
On 15/09/16 08:56, AKASHI Takahiro wrote:
On Wed, Sep 14, 2016 at 03:58:51PM +0100, Will Deacon wrote:
Hi Akashi,
On Tue, Apr 21, 2015 at 02:13:13AM +0100, AKASHI Takahiro wrote:
Could you please review my patch below?
See also arm64 maintainer's
On 03/08/2016 11:16 PM, Stephen Rothwell wrote:
Hi Jason,
I noticed that the kgdb tree
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git branch
kgdb-next
has not been updated since March 2015. I am going to remove it from
linux-next tomorrow unless I hear that it may be useful
5d5): undefined reference to `vc_cons'
kgdboc.o is built when KGDB_SERIAL_CONSOLE is set. So make
KGDB_SERIAL_CONSOLE depend on HW_CONSOLE which includes those symbols.
Acked-by: Jason Wessel
I'll put this in the kgdb-next branch and submit it to the upstream, unless it
gets merged
worked to show there is a problem. :-)
Acked-by: Jason Wessel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 03/02/2015 08:13 AM, Daniel Thompson wrote:
> kallsyms_symbol_next() returns a boolean (true on success). Currently
> kdb_read() tests the return value with an inequality that
> unconditionally evaluates to true.
>
> This is fixed in the obvious way and, since the conditional branch is
> suppos
kdb_getstr's prompt argument
Jason Wessel (1):
kdb: Fix off by one error in kdb_cpu()
Jay Lan (1):
kdb: fix incorrect counts in KDB summary command output
Rajaneesh Acharya (1):
kgdb, docs: Fix pdfdocs build errors
Documentation/DocBook/kgdb.tmpl | 6 +++---
include/linux/
Linus,
Please pull the kgdb tree bug fixes.
These have been around since 3.17 and in kgdb-next for the last 9
weeks and some will go back to -stable.
Summary of changes:
KGDB/KDB fixes and cleanups
Cleanups
kdb: Remove unused command flags, repeat flags and KDB_REPEAT_NONE
Fixes
kgdb/k
On 01/06/2015 03:21 PM, Andrew Morton wrote:
> On Tue, 06 Jan 2015 10:57:42 -0800 Joe Perches wrote:
>
>> On Tue, 2015-01-06 at 18:54 +, Daniel Thompson wrote:
>>> Hi Jason
>>>
>>> I'm trying to figure out what to do with my long-outstanding kgdb/kdb
>>> patches in preparation for the 3.20 mer
On 07/11/2014 06:33 AM, Daniel Thompson wrote:
> This patchset implements restricted modes for the KDB debugger. It is a
> continuation of previous work of Anton Vorontsov. There are no
> outstanding review comments for this patchset.
>
> It provides a means for the root user to choose the set of k
On 07/01/2014 09:16 AM, Daniel Thompson wrote:
> Currently if an active CPU fails to respond to a roundup request the
> CPU that requested the roundup will become stuck. This needlessly
> reduces the robustness of the debugger.
>
> This patch introduces a timeout allowing the system state to be exa
On 06/12/2014 01:48 PM, Fabian Frederick wrote:
> -Convert printk( to pr_foo()
> -Add pr_fmt
> -Coalesce formats
>
> Cc: Jason Wessel
> Cc: Andrew Morton
> Signed-off-by: Fabian Frederick
Thanks.
I looked through all the bits to make sure there were no cases were we
reli
On 05/14/2014 09:55 AM, Daniel Thompson wrote:
> The behaviour of the UART poll_put_char infrastructure is inconsistent
> with respect to linefeed conversions. This in turn leads to difficulty
> using kdb on serial ports that are not also consoles
> (e.g. console=ttyAMA0,115200 kgdboc=ttyAMA1,11520
gt; Reviewed-by: Dimitri Sivanich
> Reviewed-by: Hedi Berriche
One problem that I pointed out before and then you can add
Acked-by: Jason Wessel
> ---
> include/linux/kdb.h |1 +
> include/linux/kgdb.h|1 +
> kernel/debug/debug_core.c | 30
On 09/05/2013 05:50 PM, Mike Travis wrote:
> This patch adds a new "KDB_REASON" code (KDB_REASON_SYSTEM_NMI). This
> is purely cosmetic to distinguish it from the other various reasons that
> NMI may occur and are usually after an error occurred. Also the dumping
> of registers is not done to mor
On 09/05/2013 05:50 PM, Mike Travis wrote:
> This patch adds a kgdb_nmicallin() interface that can be used by
> external NMI handlers to call the KGDB/KDB handler. The primary need
> for this is for those types of NMI interrupts where all the CPUs
> have already received the NMI signal. Therefore
Commit-ID: 8f76fcd902e3b3a7d6f6c695cc8bc053579eb179
Gitweb: http://git.kernel.org/tip/8f76fcd902e3b3a7d6f6c695cc8bc053579eb179
Author: Jason Wessel
AuthorDate: Mon, 15 Jul 2013 15:27:53 -0500
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 7 Aug 2013 17:35:41 -0300
perf machine
kvm report that has no guest symbols
resolved.
This patch changes the failure to locate kernel modules to be
non-fatal.
Signed-off-by: Jason Wessel
---
tools/perf/util/machine.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tools/perf/util/machine.c b/tools/perf/util
On 04/09/2013 08:06 AM, Sedat Dilek wrote:
> config DEBUG_RODATA
> bool "Write protect kernel read-only data structures"
> - default y
> depends on DEBUG_KERNEL
> + default n if KGDB
> + default y
> ---help---
> Mark the kernel read-only data as write-protect
On 03/25/2013 01:50 PM, Mike Travis wrote:
> Currently the default for the # of lines displayed by the KDB pager
> is 24. This does not allow all of the lines for the entry messages,
> reg dump and process trace. Increase it to something more reasonable.
>
Unfortunately this is something that
On 03/25/2013 01:50 PM, Mike Travis wrote:
> The KDB 'btc' (backtrace cpus) command ignores the 'quit' reply
> to the 'more>' prompt. This is quite annoying when you have a
> large number of processors and thousands of lines are being
> printed. This fixes that problem.
>
Merged to kgdb-next an
On 03/11/2013 09:09 AM, Steven Rostedt wrote:
> This is Jason's code.
>
> Jason, please give an Ack or Nack.
>
> Thanks,
>
> -- Steve
>
>
> On Mon, 2013-03-11 at 15:13 +0800, zhangwei(Jovi) wrote:
>> trace_empty is checking in while-loop, so the previous checking
>> is totally redundant, and more w
ES_LIB and CROSS_CURSES_INC solves the issue and allowing
compiling and linking against the right headers and libraries.
Signed-off-by: Jason Wessel
cc: Michal Marek
cc: linux-kbu...@vger.kernel.org
---
scripts/kconfig/lxdialog/check-lxdialog.sh |8
1 file changed, 8 insertions(+)
diff --git
lp command truncated text
ppc64 support for kgdbts
Add missing kconfig option from original kdb port for dealing with
catastrophic kernel crashes such that you can reboot automatically
on continue from kdb
----
Jason W
On 01/14/2013 11:26 AM, Cong Ding wrote:
> the variable backup_current_thread_info isn't freed before existing the
> function.
>
> Signed-off-by: Cong Ding
> ---
> arch/powerpc/kernel/kgdb.c |5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kernel/kgd
On 01/18/2013 07:31 AM, Vineet Gupta wrote:
> On Friday 18 January 2013 06:45 PM, Jason Wessel wrote:
>> On 01/18/2013 06:25 AM, Vineet Gupta wrote:
>>> From: Mischa Jonker
>>>
>>> Signed-off-by: Mischa Jonker
>>> Signed-off-by: Vineet Gupta
&g
On 01/18/2013 06:25 AM, Vineet Gupta wrote:
> From: Mischa Jonker
>
> Signed-off-by: Mischa Jonker
> Signed-off-by: Vineet Gupta
> Cc: Jason Wessel
Acked-by: Jason Wessel
> ---
> arch/arc/Kconfig|3 +-
> arch/arc/include/asm/kgdb.h | 61
On 10/23/2012 03:01 PM, Kees Cook wrote:
> This config item has not carried much meaning for a while now and is
> almost always enabled by default. As agreed during the Linux kernel
> summit, remove it.
>
Works for me.
Acked-by: Jason Wessel
Cheers,
Jason.
--
To unsubscribe fr
a kernel module
Allow kgdboc=kdb to setup kdb on the vga console
Arnd Bergmann (1):
tty/console: fix warnings in drivers/tty/serial/kgdboc.c
Jason Wessel (6):
kgdb: Add module event hooks
mips,kgdb: fix recursive
r':
> drivers/tty/serial/kgdboc.c:293:3: warning: statement with no effect
> [-Wunused-value]
Thanks Arnd!
I'll put this in kgdb-next for the upcoming merge window, unless Greg pulls it
into his queue first.
Acked-by: Jason Wessel
Cheers,
Jason.
--
To unsubscribe from this list: s
On 09/20/2012 08:40 AM, Jason Wessel wrote:
> On 09/19/2012 06:40 PM, Anton Vorontsov wrote:
>> Hi all,
>>
>> In v8, addressed Jason's comments:
>>
>> - Changed kgdb_enable_nmi() weak function to kgdb_arch callbck;
>> - We no longer register disable_nmi
Greg,
In 3.4.5, a regression was introduced from commit: ee92389156 "SUNRPC:
move per-net operations from svc_destroy()".
This regression was actually fixed in a later upstream patch in
v3.5-rc1, specifically 4db77695bf5 "LockD: pass service to per-net up
and down functions", which means there
efined.
>
This is already pending along with other fixes in kgdb-next / linux next for
the 3.7 merge window.
Jason.
--
commit 9a15c35d16cf76482be076125f631f1193e29413
Author: Jason Wessel
Date: Wed Aug 8 21:12:19 2012 -0500
kgdb,x86: fix warning about unused variable
When compili
On 09/19/2012 06:41 PM, Anton Vorontsov wrote:
> This special driver makes it possible to temporary use NMI debugger port
> as a normal console by issuing 'nmi_console' command (assuming that the
> port is attached to KGDB).
>
The kgdb regression compiler also does checkpatch, so the "check patc
On 09/19/2012 06:40 PM, Anton Vorontsov wrote:
> Hi all,
>
> In v8, addressed Jason's comments:
>
> - Changed kgdb_enable_nmi() weak function to kgdb_arch callbck;
> - We no longer register disable_nmi command if arch does not register
> KGDB NMI handling (i.e. not filling kgdb_arch.enable_nmi ca
series, and it depends on
>> amba-pl1011 and tty_port work, which is in tty-next.
>>
>> So, the series have to go via tty-next; I believe Jason won't able
>> to take it via his tree.
> Ok, I'll wait for Jason to review them. Jason, let me know how it
> goes..
On 09/13/2012 10:03 AM, Anton Vorontsov wrote:
> This special driver makes it possible to temporary use NMI debugger port
> as a normal console by issuing 'nmi_console' command (assuming that the
> port is attached to KGDB).
>
> Unlike KDB's disable_nmi command, with this driver you are always abl
On 09/13/2012 10:03 AM, Anton Vorontsov wrote:
> This command disables NMI-entry. If NMI source has been previously shared
> with a serial console ("debug port"), this effectively releases the port
> from KDB exclusive use, and makes the console available for normal use.
>
> Of course, NMI can be
On 09/13/2012 10:03 AM, Anton Vorontsov wrote:
> The new arch callback should manage NMIs that usually cause KGDB to
> enter. That is, not all NMIs should be enabled/disabled, but only
> those that issue kgdb_handle_exception().
>
> We must mask it as serial-line interrupt can be used as an NMI, s
On 09/17/2012 06:37 AM, Greg Kroah-Hartman wrote:
> On Thu, Sep 13, 2012 at 08:01:33AM -0700, Anton Vorontsov wrote:
>> Hi all,
>>
>> Here comes the lucky v7:
>>
>> - Per Alan Cox's suggestion added hangup method and removed a small
>> leftover;
>> - Per Colin Cross' suggestion moved IRQ quiescin
Because I had not done any size profiling since the original RFC
posting, I took 20 min and ported the patch set up to the 3.6-rc3 and
booted the kernel in each configuration. There are still probably a
few use cases where this patch set might be useful but the general
sentiment seemed that this
: Greg Kroah-Hartman
Signed-off-by: Jason Wessel
---
drivers/tty/serial/pmac_zilog.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/serial/pmac_zilog.c b/drivers/tty/serial/pmac_zilog.c
index 654755a..333c8d0 100644
--- a/drivers/tty/serial/pmac_z
kbd was the original abbreviation for keyboard).
With this change kgdboc will now accept either to mean the same thing:
kgdboc=kbd
kgdboc=kdb
Signed-off-by: Jason Wessel
---
drivers/tty/serial/kgdboc.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/t
igned-off-by: Jason Wessel
---
arch/mips/kernel/kgdb.c |9 +
1 file changed, 9 insertions(+)
diff --git a/arch/mips/kernel/kgdb.c b/arch/mips/kernel/kgdb.c
index f4546e9..23817a6 100644
--- a/arch/mips/kernel/kgdb.c
+++ b/arch/mips/kernel/kgdb.c
@@ -283,6 +283,15 @@ static int kgdb_mips_n
the warning go away.
Reported-by: Thiago Rafael Becker
Signed-off-by: Jason Wessel
---
arch/x86/kernel/kgdb.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kernel/kgdb.c b/arch/x86/kernel/kgdb.c
index 3f61904..836f832 100644
--- a/arch/x86/kernel/kgdb.c
+++ b/arch/x86/ker
Anton Vorontsov (1):
kernel/debug: Make use of KGDB_REASON_NMI
Colin Ian King (1):
USB: echi-dbgp: increase the controller wait time to come out of halt.
Jason Wessel (2):
kdb: Remove unused KDB_FLAG_ONLY_DO_DUMP
kdb: Remove cpu from the more prompt
On 07/30/2012 10:06 AM, Colin Ian King wrote:
> The default 10 microsecond delay for the controller to come out of
> halt in dbgp_ehci_startup is too short, so increase it to 1 millisecond.
>
> This is based on emperical testing on various USB debug ports on
> modern machines such as a Lenovo X220i
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
Ingo Molnar wrote:
>
> I think we should also try to do some self-tests, so that when one boots
> a bzImage with the self-tests activated it can be said that all the
> basic functionality works. Simulated via some loopback method, from
> within the kernel - not via a real serial line - but it s
to setup the traps earlier allow for early debugging with
a uart based KGDB I/O driver. The do_undefinstr() routine also needed
to allow the lookup of kernel address space in order for the debugger
to plant undefined instructions in kernel memory space and receive the
correct notification.
Signed-of
not allow access to the kernel
memory space. As an example, it is required to allow the full kernel
address space is when you the kernel debugger to inspect a system
call.
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
kernel/kgdb.c | 11 +++
mm/maccess.c |6 ++
2
Implement the serial polling hooks for the pl011 uart for use with
kgdboc.
This patch was specifically tested on the ARM Versatile AB reference
platform.
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Thomas Glei
series.
Jason.
The following changes since commit 4ce04a959ef2ba9338217966013b832ff0ff9003:
Jason Wessel (1):
kgdb-light-v10: x86 HW breakpoints
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git
for_ingo
Jason Wessel (3
gpl-exported all of them. The result is
a fully modular kgdb that may help to reduce concerns regarding its
intrusiveness.
Signed-off-by: Jan Kiszka <[EMAIL PROTECTED]>
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
arch/x86/kernel/kgdb-x86.c | 11 ++-
arch/x86/kernel/r
NMI sync vs the normal NMI apic interrupt so
kgdb needs to catch the unknown NMI if it the debugger was previously
active on one of the cpus.
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
arch/x86/kernel/kgdb.c | 18 +++---
arch/x86/kernel/traps_32.c |2 ++
ar
are interested in, in the first place.
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
arch/x86/kernel/kgdb.c| 138 +
arch/x86/kernel/setup64.c | 14 +
kernel/kgdb.c |4 +-
3 files changed, 154 insertions(+), 2 del
In order to not trip the clocksource watchdog, kgdb must touch the
clocksource watchdog on the return to normal system run state.
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
include/linux/clocksource.h |1 +
kernel/kgdb.c |4
kernel/time/clocksource.c
If kgdb does remove a breakpoint that had a problem on the recursion
check, it should also print the address of the breakpoint.
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
kernel/kgdb.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/kernel/kgdb.c b/
Fix the run time configuration of kgdboc such that it does not default
to 9600 baud if you use the "echo" command to configure the sysfs
module paramater.
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
drivers/serial/kgdboc.c |7 ++-
1 files changed, 6 insertions
because the kernel.org community
may or may not object to exposing too many low level exports.
The following changes since commit 2680c15446821264fa3c2278e584974f2feb97b4:
Jason Wessel (1):
Merge branch 'master' of git://git.kernel.org/.../mingo/linux-2.6-kgdb
are available
Linus Torvalds wrote:
> [ The exception being that I think hw breakpoint support should be added
> back in - never mind that it won't work if the "native kernel" also uses
> them. Tough.
>
> If the debugger screws up the hw breakpoint state, that's a debugger
> error. I'd hope that the remote debug
Andi Kleen wrote:
> On Fri, Feb 15, 2008 at 01:35:36PM +0100, Jan Kiszka wrote:
>
>> o machine_emergency_restart - for implementing "R0" gdb packet
>>
>
> Hmm, might be a bit dangerous to call this directly -- there are various
> quirks with e.g. not rebooting on CPU #0 and not resetting A
Andi Kleen wrote:
>> It is more than a simple recursion check (which is already in the code)
>> because there are some conditions we can recover from. I'd rather not
>> crash the system out if it can be recovered.
>>
>
> Ok I'm trying to understand the code as you describe it. As far
> as I
Andi Kleen wrote:
>> Basically when you reach this chunk of code it is before the hand off
>> to the source debugger. We cannot continue because there was a
>> breakpoint in a part of the system kgdb was using while doing its
>> normal work. The reality is that KGDB is not self contained. It
>>
Andi Kleen wrote:
>> We might be best served to add a comment to explain the purpose of
>> kgdb_arch_pc() and put it in the optional implementation function
>> headers in include/linux/kgdb.h
>>
>> On some archs certain exceptions do not report the address that the
>> exception occurred at when you
Domenico Andreoli wrote:
> Hi,
>
> On Tue, Feb 12, 2008 at 12:27:47PM +0100, Ingo Molnar wrote:
>
>> this is kgdb-light, version -v10 (against Linus-latest), and can be
>> pulled from:
>>
>>git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-kgdb.git
>>
>> shortlog, diffstat and f
Ingo Molnar wrote:
> * Andi Kleen <[EMAIL PROTECTED]> wrote:
>
>
>>> i went for correctness and simplicity first. If a system is hung,
>>> the debugging CPU might hang too at any time. A timeout on the other
>>> hand introduces the possibility of a 'dead' CPU just coming back to
>>> life afte
Jan Kiszka wrote:
> There are a few things I missed in my last cleanup round, please fold
> them in, they reduce the changes outside kgdb. (I bet that membase
> dumping was related to mmio vs. mmap configuration, right?)
>
>
That is correct, the right thing to do is remove the code.
I folded y
Jan Kiszka wrote:
> [EMAIL PROTECTED] wrote:
>
>> @@ -2175,9 +2187,9 @@ uart_configure_port(struct uart_driver *drv, struct
>> uart_state *state,
>>
>> /*
>> * Power down all ports by default, except the
>> - * console if we have one.
>> + *
From: Jason Wessel <[EMAIL PROTECTED]>
Add a SERIAL_POLL API to the serial core for use with kgdboc (KGDB
over the console), the gdb serial adapter which can multiplex with a
console port.
The kgdboc module can be extended later to support all sorts of
different console types provided that
From: Jason Wessel <[EMAIL PROTECTED]>
This patch some small hooks into the normal serial core so that a uart
can be unregistered to be exclusively used for KGDB. These changes
allow for registering and unregistering a port with a struct
uart_port. From that point on KGDB does raw acces
From: Jason Wessel <[EMAIL PROTECTED]>
This patch adds in the ability to unoptimize a single kernel module to
make source stepping more linear and not optimize out variables that
the developer might like to inspect. It used with adding
COPTIMIZE=-O0 to the build line when doing something
From: Ingo Molnar <[EMAIL PROTECTED]>
add pid_max prototype - now used by sysctl and kgdb as well.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Signed-off-by: Thomas Gleixner <[EMAIL PROTECTED]>
Signed-off-by: Jason Wessel <[EMAIL PROTECTED]>
---
include/linux/pid.h
From: Jason Wessel <[EMAIL PROTECTED]>
It is possible that when SysRq-G is triggered via the keyboard that we
will miss the "up" event and once KGDB lets the kernel go another
SysRq will be required to clear this, without this change.
Signed-off-by: Tom Rini <[EMAIL PROTEC
From: Jason Wessel <[EMAIL PROTECTED]>
With more information in the kernel, gdb can be modified in such a way
as to automatically read the kernel module section information and
allow for easy kernel module debugging.
In gdb the solib-search-path must contain the location of any module
From: Jason Wessel <[EMAIL PROTECTED]>
On the i386 arch, in order to support early debugginer with kgdb when
used with kgdb via rs232 some traps must be initialized sooner rather
than later, but it is safe to always do this. The arch i386 now calls
parse_early_param() to explicitly l
Per reqest on lkml, here are the individual kgdb patches
targeted at 2.6.25.
The kgdb tree has been collapsed review. It includes
the kgdb core, the x86 arch, the kgdb8250 uart driver
and the kgdb console sharing driver.
Since the last time the kgdb patches were posted to LKML
several months ago
/linux-2.6-kgdb.git
for_linus
Ingo Molnar (1):
pid, kgdb: add pid_max prototype
Jason Wessel (7):
kgdb: core API and gdb protocol handler
kgdb, modules: Always allow module sect info for KGDB
kgdb: COPTIMIZE flag
kgdb, x86: Add arch specfic kgdb support
kgdb
1 - 100 of 161 matches
Mail list logo
