linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sachin P. Sant" <sachinp@in.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@ozlabs.org, Fastboot mailing list <fastboot@lists.osdl.org>
Subject: Re: [PATCH] kdump: don't call __ioremap() for pfn = 0
Date: Fri, 22 Sep 2006 09:52:06 +0530	[thread overview]
Message-ID: <451364EE.8070004@in.ibm.com> (raw)
In-Reply-To: <1158836557.7062.52.camel@localhost.localdomain>

Michael Ellerman wrote:
>> Attached is a patch to fix this problem. During such rare cases don't call
>> __ioremap() to do the address translation, instead use __va() .
>>     
>
> It's not really rare, it's just when we're reading /dev/oldmem directly.
>   
That's true. Since we don't try to copy raw dump from /dev/oldmem very
often, we haven't come across this problem. Hence rare .. but as
michael said always recreatable while using dd command with /dev/oldmem.

> We can actually use the __va() trick for the whole linear mapping rather
> than just pfn 0, which saves the ioremap. We also shouldn't really be
> trying to iounmap(__va(0)).
>   
Yes. Makes sense. Agreed.

> So perhaps something more like this? Although it's a bit ugly because of
> the need to conditionally call iounmap().
>   
< snip > 

Thanks
-Sachin

      parent reply	other threads:[~2006-09-22  4:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  4:37 [PATCH] kdump: don't call __ioremap() for pfn = 0 Sachin P. Sant
2006-09-21 11:02 ` Michael Ellerman
2006-09-21 14:10   ` [Fastboot] " Vivek Goyal
2006-09-22  6:55     ` Michael Ellerman
2006-09-22  4:22   ` Sachin P. Sant [this message]

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=451364EE.8070004@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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;
as well as URLs for NNTP newsgroup(s).