From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org, Ard Biesheuvel <ardb@kernel.org>
Cc: Steve Capper <steve.capper@arm.com>,
will@kernel.org, Anshuman Khandual <anshuman.khandual@arm.com>
Subject: Re: [PATCH v2 0/4] arm64: mm: optimize VA space organization for 52-bit
Date: Mon, 9 Nov 2020 18:51:26 +0000 [thread overview]
Message-ID: <160494717005.570346.14244079343431331886.b4-ty@arm.com> (raw)
In-Reply-To: <20201008153602.9467-1-ardb@kernel.org>
On Thu, 8 Oct 2020 17:35:58 +0200, Ard Biesheuvel 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.
>
> [...]
Applied to arm64 (for-next/va-refactor), thanks!
[2/4] arm64: mm: extend linear region for 52-bit VA configurations
https://git.kernel.org/arm64/c/f4693c2716b3
[3/4] arm64: mm: make vmemmap region a projection of the linear region
https://git.kernel.org/arm64/c/8c96400d6a39
[4/4] arm64: mm: tidy up top of kernel VA space
https://git.kernel.org/arm64/c/9ad7c6d5e75b
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-11-09 21:21 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 ` [PATCH v2 0/4] arm64: mm: optimize VA space organization for 52-bit Ard Biesheuvel
2020-10-15 20:40 ` Will Deacon
2020-11-09 18:51 ` Catalin Marinas [this message]
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=160494717005.570346.14244079343431331886.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.