From: Robin Murphy <robin.murphy@arm.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
devicetree@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>
Subject: Re: [Question] Memory attribute reserved by Device Tree?
Date: Thu, 30 Jun 2016 12:39:03 +0100 [thread overview]
Message-ID: <577504D7.7080106@arm.com> (raw)
In-Reply-To: <CAK7LNATGoP-Wn-wiK_CgD_v=rQXyt937qRvr8LkUQ06jHB7FAA@mail.gmail.com>
On 30/06/16 12:10, Masahiro Yamada wrote:
> Hello.
>
> Which memory attribute will ARM/ARM64 Linux
> set to the memory region reserved by
> /memreserve/ of Device Tree?
>
>
> Normal memory non-cacheable?
> Or, cacheable?
> Or, not defined?
>
> Perhaps actual behavior depends on whether the reserved area is
> located in the low-memory region?
Isn't the point of memreserve that the kernel avoids mapping it at all?
If a reserved region is later mapped in by a driver using
dma_declare_coherent_memory(), ioremap(), memremap() or whatever else,
then the attributes will vary depending on the exact method used.
Robin.
>
>
> Thanks,
>
>
next prev parent reply other threads:[~2016-06-30 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 11:10 [Question] Memory attribute reserved by Device Tree? Masahiro Yamada
2016-06-30 11:39 ` Robin Murphy [this message]
[not found] ` <577504D7.7080106-5wv7dgnIgG8@public.gmane.org>
2016-06-30 12:26 ` Mark Rutland
2016-07-06 4:10 ` Masahiro Yamada
[not found] ` <CAK7LNAQJNYVFjZyMH=kU+VJLfUCr2EwKc51HB4knZ=XM7s+MQg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-06 5:34 ` Ard Biesheuvel
[not found] ` <CAKv+Gu_iF31mBbg1pMawq+7fPDo4iXdGWJT_nWV4Oy+AqDpFOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-06 9:34 ` Mark Rutland
2016-07-06 9:48 ` Ard Biesheuvel
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=577504D7.7080106@arm.com \
--to=robin.murphy@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=yamada.masahiro@socionext.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;
as well as URLs for NNTP newsgroup(s).