From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Suzuki K. Poulose" <suzuki@in.ibm.com>
Cc: linux ppc dev <linuxppc-dev@lists.ozlabs.org>,
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
kexec@lists.infradead.org
Subject: Re: [PATCH v1 0/4][makedumpfile] vmalloc translation support for PPC32
Date: Fri, 17 Feb 2012 19:39:29 +1100 [thread overview]
Message-ID: <1329467969.2892.58.camel@pasglop> (raw)
In-Reply-To: <4F3DEBCF.8000201@in.ibm.com>
On Fri, 2012-02-17 at 11:25 +0530, Suzuki K. Poulose wrote:
> > Could you tell me what kind of data is stored in vmalloc region in
> PPC ?
> > I want to estimate importance of your patches for makedumpfile.
> I know at least the modules are loaded in the vmalloc'd region. I have
> Cc'ed linux-ppc dev. We should be able to get enough info from the
> experts here.
>
> Josh / Kumar / Others,
>
> Could you please let us know your thoughts ?
Modules, driver IO mappings, etc... I can see that being useful for
crashdumps.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Suzuki K. Poulose" <suzuki@in.ibm.com>
Cc: linux ppc dev <linuxppc-dev@lists.ozlabs.org>,
Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
kexec@lists.infradead.org
Subject: Re: [PATCH v1 0/4][makedumpfile] vmalloc translation support for PPC32
Date: Fri, 17 Feb 2012 19:39:29 +1100 [thread overview]
Message-ID: <1329467969.2892.58.camel@pasglop> (raw)
In-Reply-To: <4F3DEBCF.8000201@in.ibm.com>
On Fri, 2012-02-17 at 11:25 +0530, Suzuki K. Poulose wrote:
> > Could you tell me what kind of data is stored in vmalloc region in
> PPC ?
> > I want to estimate importance of your patches for makedumpfile.
> I know at least the modules are loaded in the vmalloc'd region. I have
> Cc'ed linux-ppc dev. We should be able to get enough info from the
> experts here.
>
> Josh / Kumar / Others,
>
> Could you please let us know your thoughts ?
Modules, driver IO mappings, etc... I can see that being useful for
crashdumps.
Cheers,
Ben.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-02-17 8:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 3:35 [PATCH v1 0/4][makedumpfile] vmalloc translation support for PPC32 Suzuki K. Poulose
2012-02-16 3:35 ` [PATCH v1 1/4] [makedumpfile] Add read_string routine Suzuki K. Poulose
2012-04-20 1:47 ` Atsushi Kumagai
2012-02-16 3:36 ` [PATCH v1 2/4] [makedumpfile][ppc] Generic vmalloc translation support Suzuki K. Poulose
2012-02-16 3:36 ` [PATCH v1 3/4] [makedumpfile][ppc] Define platform descriptors for page translation Suzuki K. Poulose
2012-02-16 3:37 ` [PATCH v1 4/4] [makedumpfile][ppc] PPC44x page translation definitions Suzuki K. Poulose
2012-02-17 0:32 ` [PATCH v1 0/4][makedumpfile] vmalloc translation support for PPC32 Atsushi Kumagai
2012-02-17 5:55 ` Suzuki K. Poulose
2012-02-17 5:55 ` Suzuki K. Poulose
2012-02-17 8:39 ` Benjamin Herrenschmidt [this message]
2012-02-17 8:39 ` Benjamin Herrenschmidt
2012-02-20 9:56 ` Atsushi Kumagai
2012-02-20 9:56 ` Atsushi Kumagai
2012-02-20 10:31 ` Suzuki K. Poulose
2012-02-20 10:31 ` Suzuki K. Poulose
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=1329467969.2892.58.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=suzuki@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 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.