From: ebiederm@xmission.com (Eric W. Biederman)
To: vgoyal@in.ibm.com
Cc: Morton Andrew Morton <akpm@osdl.org>,
Anderson Dave Anderson <anderson@redhat.com>,
Fastboot mailing list <fastboot@lists.osdl.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFO to kernel core dumps
Date: Wed, 21 Sep 2005 08:28:32 -0600 [thread overview]
Message-ID: <m1mzm6ebqn.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20050921065633.GC3780@in.ibm.com> (Vivek Goyal's message of "Wed, 21 Sep 2005 12:26:33 +0530")
Vivek Goyal <vgoyal@in.ibm.com> writes:
> o This patch adds a new note type NT_KDUMPINFO. This note is added with
> kernel core dumps generated by kdump.
>
> o This note mainly communicates the information required by kernel dump
> analysis tool "crash" to analyze the kernel core dump. As of now it contains
> the pointer to task struct of panicing task and page size. Page size is
> irrelevant for i386 but is required for architectures like ia64 and ppc64.
>
> o gdb is not affected by this change as gdb need not to parse this note.
A couple of things.
- The name of your note is terribly generic, so it seems a poor choice.
- Why do we need to capture the page size at the time of the
crash? Isn't the page size a compile time option? Won't
sys_getpagesize() get you this information before the crash?
Why do we need the kernels page size at all?
- Why do you avoid storing the current task on the other cpus?
- Can't we derive the current task from the existing register information
already captured. If not would a little extra debug information
captured at compile time be better?
- You don't address the issue of architectural control registers.
So you are going to need another note at some point. (Not
necessarily a bad thing).
> +/*
> + * NT_KDUMPINFO can be used to communicate additional information required for
> + * kernel core dumps. Additional information includes kernel configuration
> + * variables like page size and any other relevant data required by
> + * debugger (crash in this case).
> +*/
> +struct elf_kdumpinfo
> +{
> + char page_shift; /* Page size */
> + struct task_struct *panic_tsk; /* Pointer to panic task_struct */
> +};
> +
> #define NT_TASKSTRUCT 4
> #define NT_AUXV 6
> #define NT_PRXFPREG 0x46e62b7f /* copied from gdb5.1/include/elf/common.h */
> -
> +#define NT_KDUMPINFO 7 /* Used for kernel core dumps */
>
next prev parent reply other threads:[~2005-09-21 14:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 6:56 Vivek Goyal
2005-09-21 14:28 ` Eric W. Biederman [this message]
2005-09-21 15:17 ` [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFO tokernel " Dave Anderson
2005-09-22 9:01 ` Eric W. Biederman
2005-09-22 14:08 ` Vivek Goyal
2005-09-22 15:06 ` Dave Anderson
2005-09-22 16:31 ` Eric W. Biederman
2005-09-22 20:33 ` Haren Myneni
2005-09-23 5:09 ` Vivek Goyal
2005-09-23 7:22 ` Eric W. Biederman
2005-09-23 15:17 ` Subject: [PATCH] Don't uselessly export task_struct to user space in " Eric W. Biederman
[not found] ` <OF0A1E6B6F.F00DC760-ON87257084.005F99D6-88257084.00634A38@us.ibm.com>
2005-09-23 5:19 ` [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFO tokernel " Vivek Goyal
[not found] ` <4332FD56.2F5256F5@redhat.com>
2005-09-23 7:12 ` [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFO tokernelcore dumps Eric W. Biederman
2005-09-23 12:01 ` Vivek Goyal
2005-09-26 6:29 ` Vivek Goyal
2005-09-22 16:38 ` [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFO tokernel core dumps Eric W. Biederman
2005-09-22 17:00 ` [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFOtokernel " Dave Anderson
2005-09-22 7:39 ` [Fastboot] [PATCH] Kdump(x86): add note type NT_KDUMPINFO to kernel " Vivek Goyal
2005-09-22 7:46 ` Andrew Morton
2005-09-22 8:32 ` Vivek Goyal
2005-09-22 9:11 ` Eric W. Biederman
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=m1mzm6ebqn.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=anderson@redhat.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
/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®