From: jeremy.linton@arm.com (Jeremy Linton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: mm: Enable CONT_SIZE aligned sections for 64k page kernels.
Date: Fri, 12 Feb 2016 10:21:44 -0600 [thread overview]
Message-ID: <56BE0698.10506@arm.com> (raw)
In-Reply-To: <CAKv+Gu_ViEAVN1GEDMWpJ5OYjg6BVSLTEtdus6vCCXchQ1BOjw@mail.gmail.com>
On 02/12/2016 10:11 AM, Ard Biesheuvel wrote:
> On 12 February 2016 at 17:06, Jeremy Linton <jeremy.linton@arm.com> wrote:
(trimming)
>> #if defined(CONFIG_DEBUG_ALIGN_RODATA)
>> -#define ALIGN_DEBUG_RO . = ALIGN(1<<SECTION_SHIFT);
>> -#define ALIGN_DEBUG_RO_MIN(min) ALIGN_DEBUG_RO
>> +#if defined(CONFIG_ARM64_64K_PAGES)
>> +#define ALIGN_DEBUG_RO_MIN(min) . = ALIGN(CONT_SIZE);
>> +#else
>> +#define ALIGN_DEBUG_RO_MIN(min) . = ALIGN(SECTION_SIZE);
>
> Doesn't this align to 32 MB on 16k pages kernels?
Yes, I considered whether it was more appropriate to use CONT_SIZE for
16k as well.
Opinions?
>
>> +#endif
>> #elif defined(CONFIG_DEBUG_RODATA)
>> -#define ALIGN_DEBUG_RO . = ALIGN(1<<PAGE_SHIFT);
>> -#define ALIGN_DEBUG_RO_MIN(min) ALIGN_DEBUG_RO
>> +#define ALIGN_DEBUG_RO_MIN(min) . = ALIGN(PAGE_SIZE);
>> #else
>> -#define ALIGN_DEBUG_RO
>> #define ALIGN_DEBUG_RO_MIN(min) . = ALIGN(min);
>> #endif
>>
>> --
>> 2.4.3
>>
>
next prev parent reply other threads:[~2016-02-12 16:21 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 [this message]
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
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=56BE0698.10506@arm.com \
--to=jeremy.linton@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.