From: Catalin Marinas <catalin.marinas@arm.com>
To: Derrick McKee <derrick.mckee@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: Kernel logical memory map
Date: Fri, 7 Aug 2020 17:40:39 +0100 [thread overview]
Message-ID: <20200807164038.GN6750@gaia> (raw)
In-Reply-To: <CAJoBWHxa4uCp9VMGVtvNegbEs+BEJtmdUmj05sPSh+PLsW8G3Q@mail.gmail.com>
On Wed, Aug 05, 2020 at 11:05:30AM -0400, Derrick McKee wrote:
> In the documentation,
Do you mean Documentation/arm64/memory.rst?
> the first 128TB above user space is marked as
> the kernel logical memory map, and I cannot find an explanation for
> what that is. What is it used for?
First of all, its not first above the user space. There is a very large
gap between user and kernel (see the end/start values).
> Can anyone point me towards further explanation of what it is used
> for?
It's used by the kernel to map the entire RAM.
> I am looking to possibly repurpose some of that space for another use,
> and I want to know if that is even possible.
I wouldn't recommend it. If you need something in the kernel space
(addresses starting with 0xfff...) you can look at reserving some range
as we already do but you need to be a lot more specific. We have the
"vmalloc" space where the kernel does various mappings for itself (e.g.
ioremap).
If you want to repurpose it for user, it's not really possible. This
space is relies on being used in kernel space, it's not context switched
(page tables pointed at by TTBR1_EL1 rather than TTBR1_EL0). However,
you have enough user address space to add stuff in there.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-07 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 15:05 Kernel logical memory map Derrick McKee
2020-08-07 16:40 ` Catalin Marinas [this message]
2020-08-07 19:28 ` Derrick McKee
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=20200807164038.GN6750@gaia \
--to=catalin.marinas@arm.com \
--cc=derrick.mckee@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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