From: Daniel Walker <danielwa@cisco.com>
To: Maxim Uvarov <muvarov@gmail.com>
Cc: "xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: IO memory read from /proc/vmcore leads to hang.
Date: Mon, 25 Jul 2016 10:06:35 -0700 [thread overview]
Message-ID: <5796471B.2000900@cisco.com> (raw)
In-Reply-To: <CAJGZr0LzrwM0qbLJJnfyFoJ2y_TYqzYw+=C-_w-vbeioQU09dA@mail.gmail.com>
This doesn't appear to be the case. As of 2.0.6 ppc32 is still used. I
don't see any changesets in the git tree that would change that for
later versions.
On 07/22/2016 04:11 AM, Maxim Uvarov wrote:
> I might be wrong but as I remember powerpc32 is deprecated in
> kexec-tools and all code use ppc64 directory even for 32 bit code...
>
> 2016-07-21 23:04 GMT+03:00 Daniel Walker <danielwa@cisco.com>:
>> On 07/21/2016 12:33 PM, Maxim Uvarov wrote:
>>> 2016-07-21 18:19 GMT+03:00 Daniel Walker <danielwa@cisco.com>:
>>>> There appears to be no code which checks what is or is not System ram,
>>>> there is nothing that checks the device tree to see what is IO memory,
>>>> and
>>>> nothing reads /proc/iomem .. So AFAIK nothing cares if it's IO memory, or
>>>> system ram, and there's no method to config things to skip any memory in
>>>> the
>>>> system, except in makedumpfile which can skip symbols not IO memory.
>>>>
>>>>
>>> Daniel, unfortunately it's long time for me when I looked to powerpc
>>> code. But I just
>>> checked that here:
>>>
>>> kexec-tools-2.0.6/kexec/arch/ppc64/kexec-ppc64.c
>>>
>>> is probably what you need.
>>
>> I have a powerpc32 .. In the powerpc64 file I only see something called
>> "reserved-ranges" which may do what I want, however, that doesn't exist in
>> the 32bit version. It appers the reserved-ranges is used by OPAL firmware ,
>> which I don't have. There doesn't appear to be anything generic in ppc64 to
>> exclude device IO memory.
>>
>> Daniel
>
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2016-07-25 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 21:46 IO memory read from /proc/vmcore leads to hang Daniel Walker
2016-07-15 7:23 ` Mahesh Jagannath Salgaonkar
2016-07-20 19:18 ` Daniel Walker
2016-07-21 7:34 ` Maxim Uvarov
2016-07-21 15:19 ` Daniel Walker
2016-07-21 19:33 ` Maxim Uvarov
2016-07-21 20:04 ` Daniel Walker
2016-07-22 11:11 ` Maxim Uvarov
2016-07-25 17:06 ` Daniel Walker [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=5796471B.2000900@cisco.com \
--to=danielwa@cisco.com \
--cc=kexec@lists.infradead.org \
--cc=muvarov@gmail.com \
--cc=xe-kernel@external.cisco.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.