From: Pratyush Anand <panand@redhat.com>
To: Kristian Kielhofner <kris@kriskinc.com>
Cc: kexec@lists.infradead.org
Subject: Re: Kexec on ARM - memory detection
Date: Fri, 28 Apr 2017 22:50:43 +0530 [thread overview]
Message-ID: <b7361ec4-6f26-46f3-64db-b4ef511b283f@redhat.com> (raw)
In-Reply-To: <CAKDfjgeo_DNqi6=rDA6nPtjSsSOWGJXA7piQ_LL8yxqUOyg9Jg@mail.gmail.com>
On Wednesday 26 April 2017 10:45 PM, Kristian Kielhofner wrote:
> On Fri, Apr 21, 2017 at 6:27 AM, Pratyush Anand <panand@redhat.com> wrote:
>> Hi Kristian,
>>
>> Sorry, I missed this mail.
>> Are you still on it, or it is solved?
>
> No problem, I'm still experiencing the issue but I haven't
> investigated it further.
>
>>
>>
>> How does kexec-tools see above memory ranges?
>> As per your /proc/iomem, it should have been
>> 42000000-5fffffff (0)
>>
>> Can you put some extra debug print in your code and check why do you have
>> above behavior?
>>
>
> Can you point towards some examples or documentation for what you're
> looking for?
kexec-tools:kexec/arch/arm/kexec-arm.c:get_memory_ranges() is telling you that
you have
MEMORY RANGES
00012028b6d27010-bea6aee700000004 (0)
However, you /proc/iomem is telling you:
42000000-5fffffff : System RAM
get_memory_ranges() is reading /proc/iomem and finding out the available ram
locations. So, can you debug this kexec-tools function and see why you do not
get the range which is coming from /proc/iomem
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2017-04-28 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 16:17 Kexec on ARM - memory detection Kristian Kielhofner
2017-04-21 11:27 ` Pratyush Anand
2017-04-26 17:15 ` Kristian Kielhofner
2017-04-28 17:20 ` Pratyush Anand [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=b7361ec4-6f26-46f3-64db-b4ef511b283f@redhat.com \
--to=panand@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=kris@kriskinc.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