From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Taniya Das <tdas@codeaurora.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, tsoni@codeaurora.org
Subject: Re: arm_memblock_steal() API usage
Date: Tue, 3 Apr 2012 08:30:54 +0100 [thread overview]
Message-ID: <20120403073053.GO24211@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4F7A76B3.3070405@codeaurora.org>
On Tue, Apr 03, 2012 at 09:34:03AM +0530, Taniya Das wrote:
> I have a requirement where I need around ~100 bytes of memory to save
> contents of
> registers to a non-cached area before going into low power mode.
>
> I did do some analysis on a 1GB RAM device of allocating 8 bytes using
> the API and the below was the result
> was showing allocating only 8 bytes.
>
> API used : - arm_memblock_steal(SZ_8, SZ_64K);--> physical address
> returned is 0x3b1f0000
It's silly to use this for the above purpose. Why not just use kmalloc
and cache flushing to ensure that the data is pushed out to RAM?
> Also is this API advisable for devices with low system RAM?
No.
next prev parent reply other threads:[~2012-04-03 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 4:04 arm_memblock_steal() API usage Taniya Das
2012-04-03 7:30 ` Russell King - ARM Linux [this message]
2012-04-04 5:06 ` Taniya Das
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=20120403073053.GO24211@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=tdas@codeaurora.org \
--cc=tsoni@codeaurora.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;
as well as URLs for NNTP newsgroup(s).