From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping
Date: Mon, 5 Oct 2015 18:03:11 +0100 [thread overview]
Message-ID: <20151005170310.GC5557@MBP.local> (raw)
In-Reply-To: <1443818865-19846-1-git-send-email-jeremy.linton@arm.com>
On Fri, Oct 02, 2015 at 03:47:38PM -0500, Jeremy Linton wrote:
> Also, continuing thanks to Steve Capper who has been religiously
> testing these patch sets, and found a bug in the previous
> implementation.
Quick question: has this series been tested with CONFIG_DEBUG_RODATA
enabled?
--
Catalin
next prev parent reply other threads:[~2015-10-05 17:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 20:47 [PATCHv2 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping Jeremy Linton
2015-10-02 20:47 ` [PATCH 1/7] arm64: Add contiguous page flag shifts and constants Jeremy Linton
2015-10-02 20:47 ` [PATCH 2/7] arm64: PTE/PMD contiguous bit definition Jeremy Linton
2015-10-06 11:10 ` Catalin Marinas
2015-10-02 20:47 ` [PATCH 3/7] arm64: Macros to check/set/unset the contiguous bit Jeremy Linton
2015-10-02 20:47 ` [PATCH 4/7] arm64: Default kernel pages should be contiguous Jeremy Linton
2015-10-02 20:47 ` [PATCH 5/7] arm64: Make the kernel page dump utility aware of the CONT bit Jeremy Linton
2015-10-02 20:47 ` [PATCH 6/7] arm64: Mark kernel page ranges contiguous Jeremy Linton
2015-10-06 11:15 ` Catalin Marinas
2015-10-02 20:47 ` [PATCH 7/7] Document the use of the arm64 contpte/nonconpte flags Jeremy Linton
2015-10-05 16:49 ` Catalin Marinas
2015-10-05 18:29 ` Jeremy Linton
2015-10-06 9:42 ` Catalin Marinas
2015-10-05 17:03 ` Catalin Marinas [this message]
2015-10-05 18:22 ` [PATCHv2 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping Jeremy Linton
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=20151005170310.GC5557@MBP.local \
--to=catalin.marinas@arm.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 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.