From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: Mark kernel page ranges contiguous
Date: Fri, 12 Feb 2016 18:11:02 +0000 [thread overview]
Message-ID: <20160212181102.GF20262@leverpostej> (raw)
In-Reply-To: <56BE1FE5.8080002@arm.com>
On Fri, Feb 12, 2016 at 12:09:41PM -0600, Jeremy Linton wrote:
> On 02/12/2016 11:58 AM, Mark Rutland wrote:
>
> (trimming)
>
> >All create_mapping_late() calls should be performed with the same
> >physical/virtual start/end as earlier "chunk" mappings, and thus should
> >never result in a fuse/split or translation change -- only permission
> >changes (which we believe do not result in TLB conflicts, or we'd need
> >to do far more work to fix those up).
> >
> >If we split/fuse in any case other than EFI runtime table creation, that
> >is a bug that we need to fix. If you're seeing a case we do that, then
> >please let me know!
>
> We are saying the same thing, and right now the biggest violator is
> probably the .rodata patch I just posted!
Ok, phew!
The simple fix is to make .text and .rodata separate "chunks", then it
all falls out in the wash.
Mark.
next prev parent reply other threads:[~2016-02-12 18:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 16:06 [PATCH 0/2] flag contiguous PTEs in linear mapping Jeremy Linton
2016-02-12 16:06 ` [PATCH 1/2] arm64: mm: Enable CONT_SIZE aligned sections for 64k page kernels Jeremy Linton
2016-02-12 16:11 ` Ard Biesheuvel
2016-02-12 16:21 ` Jeremy Linton
2016-02-12 16:28 ` Ard Biesheuvel
2016-02-12 16:43 ` Jeremy Linton
2016-02-12 16:46 ` Ard Biesheuvel
2016-02-12 17:32 ` Ard Biesheuvel
2016-02-12 16:06 ` [PATCH 2/2] arm64: Mark kernel page ranges contiguous Jeremy Linton
2016-02-12 16:57 ` Mark Rutland
2016-02-12 17:35 ` Jeremy Linton
2016-02-12 17:58 ` Mark Rutland
2016-02-12 18:09 ` Jeremy Linton
2016-02-12 18:11 ` Mark Rutland [this message]
2016-02-13 16:43 ` Ard Biesheuvel
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=20160212181102.GF20262@leverpostej \
--to=mark.rutland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox