From: gregkh@linuxfoundation.org (gregkh at linuxfoundation.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] drivers/char: kmem: disable on arm64
Date: Mon, 17 Jul 2017 16:18:40 +0200 [thread overview]
Message-ID: <20170717141840.GA16198@kroah.com> (raw)
In-Reply-To: <CAKv+Gu_nOo3VfjHistipR7vhaTnO89M8X1rrePgk3jhK0xnYVA@mail.gmail.com>
On Tue, Jun 20, 2017 at 01:20:49PM +0200, Ard Biesheuvel wrote:
> On 20 June 2017 at 08:59, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> > As it turns out, arm64 deviates from other architectures in the way it
> > maps the VMALLOC region: on most (all?) other architectures, it resides
> > strictly above the kernel's direct mapping of DRAM, but on arm64, this
> > is the other way around. For instance, for a 48-bit VA configuration,
> > we have
> >
> > modules : 0xffff000000000000 - 0xffff000008000000 ( 128 MB)
> > vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000 (129022 GB)
> > ...
> > vmemmap : 0xffff7e0000000000 - 0xffff800000000000 ( 2048 GB maximum)
> > 0xffff7e0000000000 - 0xffff7e0003ff0000 ( 63 MB actual)
> > memory : 0xffff800000000000 - 0xffff8000ffc00000 ( 4092 MB)
> >
> > This has mostly gone unnoticed until now, but it does appear that it
> > breaks an assumption in the kcore
>
> s/kcore/kmem/
v4? :)
next prev parent reply other threads:[~2017-07-17 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 6:59 [PATCH v3] drivers/char: kmem: disable on arm64 Ard Biesheuvel
2017-06-20 9:31 ` Mark Rutland
2017-06-20 11:20 ` Ard Biesheuvel
2017-07-17 14:18 ` gregkh at linuxfoundation.org [this message]
2017-07-17 17:04 ` 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=20170717141840.GA16198@kroah.com \
--to=gregkh@linuxfoundation.org \
--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