From: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
To: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>
Cc: V Srivatsa <vsrivatsa@in.ibm.com>,
Dave Anderson <anderson@redhat.com>,
kexec@lists.infradead.org,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Reinhard <BUENDGEN@de.ibm.com>
Subject: Re: [PATCH v1 0/6] makedumpfile: makedumpfile enhancement to filter out kernel data from vmcore
Date: Wed, 16 Mar 2011 11:07:40 +0530 [thread overview]
Message-ID: <20110316053740.GA6854@in.ibm.com> (raw)
In-Reply-To: <20110315151247.23fc84bc.oomichi@mxs.nes.nec.co.jp>
Hi Ken'inchi,
On Tue, Mar 15, 2011 at 03:12:47PM +0900, Ken'ichi Ohmichi wrote:
>
> Hi Mahesh,
>
> In my idea, offset_eraseinfo points the *file offset* of the erased
> information and size_eraseinfo is the information size.
>
> The erased information would contain *multiple* erased symbol names.
> For example, the following is based on your above example.
>
> struct S1 {
> int a;
> int b;
> int c;
> };
> struct S2 {
> struct S1 *mystruct1;
> struct S1 *mystruct2;
> };
>
> struct S2 mystruct2;
>
> #Filter command
> erase mystruct2.mystruct1.a
> erase mystruct2.mystruct1.c
> erase mystruct2.mystruct2.b
>
> #The erased information
> erase mystruct2.mystruct1.a 4
> erase mystruct2.mystruct1.c 4
> erase mystruct2.mystruct2.b 4
>
>
> The dumpfile image :
>
> header dump data the erased information
> +------------------+-----------------------+-------------------------------+
> | ................ | ..................... | erase mystruct2.mystruct1.a 4 |
> | offset_eraseinfo | ..................... | erase mystruct2.mystruct1.c 4 |
> | size_eraseinfo | ..................... | erase mystruct2.mystruct2.b 4 |
> +------------------+-------------------------------------------------------+
> : offset_eraseinfo (offset in dumpfile)
> <------ size_eraseinfo ------->
>
Will work on the cahnge.
Thanks,
-Mahesh.
> Thanks
> Ken'ichi Ohmichi
--
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-03-16 5:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 8:04 [PATCH v1 0/6] makedumpfile: makedumpfile enhancement to filter out kernel data from vmcore Mahesh J Salgaonkar
2011-03-11 14:07 ` Dave Anderson
2011-03-14 2:44 ` Ken'ichi Ohmichi
2011-03-15 5:29 ` Mahesh Jagannath Salgaonkar
2011-03-15 6:12 ` Ken'ichi Ohmichi
2011-03-16 5:37 ` Mahesh J Salgaonkar [this message]
2011-03-15 14:43 ` Dave Anderson
2011-03-14 6:18 ` Mahesh Jagannath Salgaonkar
2011-03-14 7:05 ` Ken'ichi Ohmichi
2011-03-14 8:51 ` Reinhard Buendgen
2011-03-14 1:55 ` Ken'ichi Ohmichi
2011-03-14 6:26 ` Mahesh Jagannath Salgaonkar
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=20110316053740.GA6854@in.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=BUENDGEN@de.ibm.com \
--cc=ananth@in.ibm.com \
--cc=anderson@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vsrivatsa@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