From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, msb@chromium.org,
linux-kernel@vger.kernel.org, sergiu@chromium.org,
Bryan Freed <bfreed@chromium.org>,
akpm@linux-foundation.org, seiji.aguchi@hds.com
Subject: Re: [PATCH] ramoops appears geared to not support ARM
Date: Sat, 29 Oct 2011 13:53:42 +0100 [thread overview]
Message-ID: <20111029125342.GB19187@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4EABF4C2.7000104@gmail.com>
On Sat, Oct 29, 2011 at 02:42:42PM +0200, Marco Stornelli wrote:
> Ok, I understand, but other question: isn't there any way to reserve
> normal memory? Or at least, hasn't the mem kernel option any effect from
> that point of view?
mem= can be used to redefine the available memory to the kernel, but
then you have to have some way to define a region of the memory you've
excluded to the kernel to use for ramoops.
A platform can also use the memblock stuff to extract some memory
dynamically from the information passed from the firmware - by using
memblock_alloc + memblock_remove + memblock_free. The memblock_remove
call will take the memory out of the available memory to the kernel,
and thus will prevent it being mapped.
This must be done via the ->reserve callback in the ARM board/SoC
record (it can't be done later because the memory will have already
been mapped.)
next prev parent reply other threads:[~2011-10-29 12:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 23:21 Bryan Freed
2011-10-28 23:21 ` [PATCH] ramoops: Add support for ARM systems Bryan Freed
2011-10-29 8:39 ` [PATCH] ramoops appears geared to not support ARM Marco Stornelli
2011-10-29 9:34 ` Russell King - ARM Linux
2011-10-29 11:04 ` Marco Stornelli
2011-10-29 11:55 ` Russell King - ARM Linux
2011-10-29 12:42 ` Marco Stornelli
2011-10-29 12:53 ` Russell King - ARM Linux [this message]
2011-10-29 14:22 ` Marco Stornelli
[not found] ` <CAEYUcX1PUgniJLqYXKM5pf_9T06OPFg4q0ZUCFc8Deu1J_R9-A@mail.gmail.com>
2011-10-30 11:33 ` Marco Stornelli
2011-10-31 6:03 ` Bryan Freed
2011-10-31 8:57 ` Marco Stornelli
2011-10-31 23:03 ` Bryan Freed
2011-11-01 8:52 ` Marco Stornelli
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=20111029125342.GB19187@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bfreed@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=msb@chromium.org \
--cc=seiji.aguchi@hds.com \
--cc=sergiu@chromium.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
all inboxes | Powered by JetHome®