From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv3 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping
Date: Wed, 18 Nov 2015 11:01:24 +0000 [thread overview]
Message-ID: <20151118110124.GF22731@arm.com> (raw)
In-Reply-To: <564B49B4.8000204@arm.com>
On Tue, Nov 17, 2015 at 09:37:24AM -0600, Jeremy Linton wrote:
> Hello,
Hi Jeremy,
> Just a heads up, but this patch is causing a boot problem on a m400. I
> should know more soon.
Any chance you could share a reproducer/panic log/debug info, please?
If we can't fix this soon, then we'll have to look at reverting the change,
so getting a few more eyes on the problem might help.
Will
next prev parent reply other threads:[~2015-11-18 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 17:00 [PATCHv3 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping Jeremy Linton
2015-10-07 17:00 ` [PATCH 1/7] arm64: Add contiguous page flag shifts and constants Jeremy Linton
2015-10-07 17:00 ` [PATCH 2/7] arm64: PTE/PMD contiguous bit definition Jeremy Linton
2015-10-07 17:00 ` [PATCH 3/7] arm64: Macros to check/set/unset the contiguous bit Jeremy Linton
2015-10-07 17:00 ` [PATCH 4/7] arm64: Default kernel pages should be contiguous Jeremy Linton
2015-10-07 17:00 ` [PATCH 5/7] arm64: Make the kernel page dump utility aware of the CONT bit Jeremy Linton
2015-10-07 17:00 ` [PATCH 6/7] arm64: Add a kernel Kconfig option to enable contiguous PTE marking Jeremy Linton
2015-10-07 17:00 ` [PATCH 7/7] arm64: Mark kernel page ranges contiguous Jeremy Linton
2015-10-09 12:50 ` [PATCHv3 0/7] arm64: Use contiguous PTE bit for the kernel linear mapping Catalin Marinas
2015-10-09 15:00 ` Jeremy Linton
2015-11-17 15:37 ` Jeremy Linton
2015-11-18 11:01 ` Will Deacon [this message]
2015-11-18 14:10 ` 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=20151118110124.GF22731@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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