From: Steve Capper <Steve.Capper@arm.com>
To: Mark Rutland <Mark.Rutland@arm.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>, nd <nd@arm.com>,
"will@kernel.org" <will@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] arm64: memory: VA_START fixups
Date: Wed, 14 Aug 2019 14:51:47 +0000 [thread overview]
Message-ID: <20190814145145.GC3646@capper-ampere.manchester.arm.com> (raw)
In-Reply-To: <20190814132848.24295-1-mark.rutland@arm.com>
On Wed, Aug 14, 2019 at 02:28:46PM +0100, Mark Rutland wrote:
> Hi all,
Hi Mark,
>
> These patches address my concerns with the new VA_START semantic as I
> spotted while reviewing Will's 52-bit VA cleanup. The first patch
> corrects the newly broken usage of VA_START, and the second renames
> VA_START to PAGE_END to make the new semantic clearer.
>
> Both patches are based on the arm64 for-next/52-bit-kva branch, and I've
> given a 52-bit VA configuration a build+boot test (on HW without 52-bit
> VA support).
>
A big thank you for this!
I have applied this series and tested it with CONFIG_DEBUG_VIRTUAL,
CONFIG_DEBUG_VM and KASAN SW TAGS.
I've tested this with 52-bit and have given the kernel page table dumper
a go too.
FWIW:
Tested-by: Steve Capper <steve.capper@arm.com>
Cheers,
--
Steve
_______________________________________________
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:[~2019-08-14 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 13:28 [PATCH 0/2] arm64: memory: VA_START fixups Mark Rutland
2019-08-14 13:28 ` [PATCH 1/2] arm64: memory: fix flipped VA space fallout Mark Rutland
2019-08-14 14:51 ` Steve Capper
2019-08-14 13:28 ` [PATCH 2/2] arm64: memory: rename VA_START to PAGE_END Mark Rutland
2019-08-14 14:51 ` Steve Capper
2019-08-14 14:51 ` Steve Capper [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=20190814145145.GC3646@capper-ampere.manchester.arm.com \
--to=steve.capper@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nd@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