linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Linux ARM <linux-arm-kernel@lists.infradead.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Will Deacon <will@kernel.org>,
	Steve Capper <steve.capper@arm.com>
Subject: Re: [PATCH v2 0/4] arm64: mm: optimize VA space organization for 52-bit
Date: Fri, 9 Oct 2020 16:16:11 +0200	[thread overview]
Message-ID: <CAMj1kXF0S6L5rTAuwV+WUZabGoDi2mqZCFS2GejoSx2f+rtzhg@mail.gmail.com> (raw)
In-Reply-To: <20201008153602.9467-1-ardb@kernel.org>

On Thu, 8 Oct 2020 at 17:36, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> This series reorganizes the kernel VA space slightly so that 52-bit VA
> configurations can use more virtual address space, i.e., the usable
> linear address space almost doubles, from 2^51 to 2^52-2^47.
>
> Patch #1 merges the physvirt_offset and memstart_addr variables, both of
> which represent translations between the physical address space and the
> linear region, and there is no need for having both. This fixes a bug too,
> as the two values were not properly kept in sync when booting with KASLR
> enabled.
>
> Patch #2 updates the definitions for the boundaries of the linear space,
> so that 52-bit VA builds use all available space for the linear region.
>
> Patches #3 and #4 simplify the way the vmemmap region is configured, and
> unify the 48-bit/4k and 52-bit/64k layouts.
>
> Changes since v1:
> - drop incorrect use of untagged_addr() from #2
> - add patches #3 and #4
>
> Not boot tested yet on a 52-bit VA capable system.
>

Boot tested now on FVP Base with and without LVA support enabled.

> Cc: Steve Capper <steve.capper@arm.com>
> Cc: Anshuman Khandual <anshuman.khandual@arm.com>
>
> Ard Biesheuvel (4):
>   arm64: mm: use single quantity to represent the PA to VA translation
>   arm64: mm: extend linear region for 52-bit VA configurations
>   arm64: mm: make vmemmap region a projection of the linear region
>   arm64: mm: tidy up top of kernel VA space
>
>  Documentation/arm64/kasan-offsets.sh |  3 +-
>  Documentation/arm64/memory.rst       | 45 +++++++++-----------
>  arch/arm64/Kconfig                   | 20 ++++-----
>  arch/arm64/include/asm/memory.h      | 35 +++++++--------
>  arch/arm64/include/asm/pgtable.h     |  6 +--
>  arch/arm64/mm/init.c                 | 34 ++++++---------
>  6 files changed, 63 insertions(+), 80 deletions(-)
>
> --
> 2.17.1
>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-10-09 14:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 15:35 [PATCH v2 0/4] arm64: mm: optimize VA space organization for 52-bit Ard Biesheuvel
2020-10-08 15:35 ` [PATCH v2 1/4] arm64: mm: use single quantity to represent the PA to VA translation Ard Biesheuvel
2020-10-13 16:14   ` Steve Capper
2020-10-13 16:47   ` Steve Capper
2020-10-15 10:47   ` Will Deacon
2020-10-08 15:36 ` [PATCH v2 2/4] arm64: mm: extend linear region for 52-bit VA configurations Ard Biesheuvel
2020-10-13 16:51   ` Steve Capper
2020-10-13 16:57     ` Ard Biesheuvel
2020-10-13 17:38       ` Steve Capper
2020-10-14  3:44   ` Anshuman Khandual
2020-10-14  7:18     ` Ard Biesheuvel
2020-10-08 15:36 ` [PATCH v2 3/4] arm64: mm: make vmemmap region a projection of the linear region Ard Biesheuvel
2020-10-13 16:52   ` Steve Capper
2020-11-10 12:55   ` Geert Uytterhoeven
2020-11-10 13:10     ` Ard Biesheuvel
2020-11-10 14:08       ` Ard Biesheuvel
2020-11-10 14:56         ` Geert Uytterhoeven
2020-11-10 15:39         ` Catalin Marinas
2020-11-10 15:42           ` Ard Biesheuvel
2020-11-10 16:14             ` Catalin Marinas
2020-11-10 16:18               ` Ard Biesheuvel
2020-10-08 15:36 ` [PATCH v2 4/4] arm64: mm: tidy up top of kernel VA space Ard Biesheuvel
2020-10-13 16:52   ` Steve Capper
2020-10-09 14:16 ` Ard Biesheuvel [this message]
2020-10-15 20:40 ` [PATCH v2 0/4] arm64: mm: optimize VA space organization for 52-bit Will Deacon
2020-11-09 18:51 ` Catalin Marinas

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=CAMj1kXF0S6L5rTAuwV+WUZabGoDi2mqZCFS2GejoSx2f+rtzhg@mail.gmail.com \
    --to=ardb@kernel.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=steve.capper@arm.com \
    --cc=will@kernel.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).