From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] process: Add display of memory around registers when displaying regs.
Date: Tue, 14 Dec 2010 09:34:50 +0000 [thread overview]
Message-ID: <20101214093450.GC18425@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1292302659-1863-4-git-send-email-john.stultz@linaro.org>
On Mon, Dec 13, 2010 at 08:57:38PM -0800, John Stultz wrote:
> From: San Mehat <san@google.com>
>
> This is extremely useful in diagnosing remote crashes, and is based heavily
> on original work by <md@google.com>.
Why reinvent dump_mem() ?
If we dump out two lines of data per register, that's 32 additional
lines in the oops dump. That might make it difficult to get the
register information which may have been lost off the scrollback.
Or worse still, it might wrap the kernel buffers before syslog gets
it.
next prev parent reply other threads:[~2010-12-14 9:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 4:57 [PATCH 0/4][RFC] Trivial ARM related Android patches John Stultz
2010-12-14 4:57 ` [PATCH 1/4] avoid mis-detecting some V7 cores in the decompressor John Stultz
2010-12-14 4:57 ` [PATCH 2/4] Optionally flush entire dcache from v6_dma_flush_range John Stultz
2010-12-14 9:30 ` Russell King - ARM Linux
2010-12-14 10:58 ` Catalin Marinas
2010-12-14 4:57 ` [PATCH 3/4] process: Add display of memory around registers when displaying regs John Stultz
2010-12-14 9:34 ` Russell King - ARM Linux [this message]
2010-12-14 4:57 ` [PATCH 4/4] Do not call flush_cache_user_range with mmap_sem held John Stultz
2010-12-14 9:30 ` Russell King - ARM Linux
2010-12-14 17:51 ` Catalin Marinas
2010-12-14 19:05 ` Russell King - ARM Linux
2010-12-14 21:08 ` Catalin Marinas
2011-04-04 13:27 ` Catalin Marinas
2011-04-04 13:37 ` Russell King - ARM Linux
2011-04-04 13:43 ` Catalin Marinas
2011-08-26 7:32 ` Jiejing.Zhang
2011-09-05 11:21 ` Catalin Marinas
2010-12-14 18:18 ` Catalin Marinas
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=20101214093450.GC18425@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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.