public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: "Suzuki K. Poulose" <suzuki@in.ibm.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: linux ppc dev <linuxppc-dev@lists.ozlabs.org>,
	Josh Boyer <jwboyer@gmail.com>,
	kexec@lists.infradead.org, Kumar Gala <galak@kernel.crashing.org>
Subject: Re: [PATCH v1 0/4][makedumpfile] vmalloc translation support for PPC32
Date: Fri, 17 Feb 2012 11:25:27 +0530	[thread overview]
Message-ID: <4F3DEBCF.8000201@in.ibm.com> (raw)
In-Reply-To: <20120217093220.0c2993a1.kumagai-atsushi@mxc.nes.nec.co.jp>

On 02/17/2012 06:02 AM, Atsushi Kumagai wrote:
> Hi, Suzuki
>
> On Thu, 16 Feb 2012 09:05:17 +0530
> "Suzuki K. Poulose"<suzuki@in.ibm.com>  wrote:
>
>> The series introduces an infrastructure to define platform specific
>> bits for page translation for PPC and PPC44x support for vmalloc
>> translation.
>>
>> This is similar to what we have implemented for Crash-utility.
>>
>> The patches are based makedumpfile-1.4.2 + PPC32 support patches
>> which is queued in for 1.4.3.
>>
>> ---
>>
>> Suzuki K. Poulose (4):
>>        [makedumpfile][ppc] PPC44x page translation definitions
>>        [makedumpfile][ppc] Define platform descriptors for page translation
>>        [makedumpfile][ppc] Generic vmalloc translation support
>>        [makedumpfile] Add read_string routine
>>
>>
>>   arch/ppc.c     |  108 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
>>   makedumpfile.c |   14 +++++++
>>   makedumpfile.h |   21 +++++++++++
>>   3 files changed, 139 insertions(+), 4 deletions(-)
>>
>> --
>> Suzuki Poulose
>
> 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 ?

Thanks

Suzuki


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2012-02-17  5:55 UTC|newest]

Thread overview: 11+ 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 [this message]
2012-02-17  8:39     ` Benjamin Herrenschmidt
2012-02-20  9:56       ` Atsushi Kumagai
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=4F3DEBCF.8000201@in.ibm.com \
    --to=suzuki@in.ibm.com \
    --cc=galak@kernel.crashing.org \
    --cc=jwboyer@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox