From: Nicholas Piggin <npiggin@gmail.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Laura Abbott <labbott@redhat.com>,
Rashmica Gupta <rashmica.g@gmail.com>
Subject: Re: [PATCH v2 5/9] powerpc/vmlinux.lds: Align __init_begin to 16M
Date: Mon, 5 Jun 2017 16:51:49 +1000 [thread overview]
Message-ID: <20170605165149.1390a26d@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <CAKTCnz=CNqcCVP7pL++dy-i2CRHs4heo9fYBFWX0X884DfkrgA@mail.gmail.com>
On Mon, 5 Jun 2017 08:42:40 +1000
Balbir Singh <bsingharora@gmail.com> wrote:
> On Sun, Jun 4, 2017 at 2:22 PM, Nicholas Piggin <npiggin@gmail.com> wrote:
> > On Sat, 3 Jun 2017 17:18:39 +1000
> > Balbir Singh <bsingharora@gmail.com> wrote:
> >
> >> For CONFIG_STRICT_KERNEL_RWX align __init_begin to 16M.
> >> We use 16M since its the larger of 2M on radix and 16M
> >> on hash for our linear mapping. The plan is to have
> >> .text, .rodata and everything upto __init_begin marked
> >> as RX. Note we still have executable read only data.
> >> We could further align read only data to another 16M
> >> boundary, but then the linker starts using stubs and
> >> that breaks our assembler code in head_64.S
> >
> > Is this still the case with powerpc next?
> >
>
> Sorry, no, I was on linux-next for testing, but I think your linker
> stub patches went in very recently. I'll rebase on top and test,
That would be good. I'd like to make sure the linker stub workaround
does work for your case.
> but I am not sure if I want two 16M alignments and bloat the size
> of vmlinux. But I'll double check what happens
Maybe it could be an option.
Thanks,
Nick
next prev parent reply other threads:[~2017-06-05 6:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 7:18 [PATCH v2 0/9] Enable STRICT_KERNEL_RWX Balbir Singh
2017-06-03 7:18 ` [PATCH v2 1/9] powerpc/lib/code-patching: Enhance code patching Balbir Singh
2017-06-03 23:45 ` kbuild test robot
2017-06-07 10:25 ` Christophe LEROY
2017-06-07 11:04 ` Balbir Singh
2017-06-07 11:52 ` Michael Ellerman
2017-06-03 7:18 ` [PATCH v2 2/9] powerpc/kprobes: Move kprobes over to patch_instruction Balbir Singh
2017-06-03 7:18 ` [PATCH v2 3/9] powerpc/kprobes/optprobes: Move " Balbir Singh
2017-06-03 7:18 ` [PATCH v2 4/9] powerpc/xmon: Add patch_instruction supporf for xmon Balbir Singh
2017-06-03 7:18 ` [PATCH v2 5/9] powerpc/vmlinux.lds: Align __init_begin to 16M Balbir Singh
2017-06-04 4:22 ` Nicholas Piggin
2017-06-04 22:42 ` Balbir Singh
2017-06-05 6:51 ` Nicholas Piggin [this message]
2017-06-03 7:18 ` [PATCH v2 6/9] powerpc/platform/pseries/lpar: Fix updatepp and updateboltedpp Balbir Singh
2017-06-03 7:18 ` [PATCH v2 7/9] powerpc/mm/hash: Implement mark_rodata_ro() for hash Balbir Singh
2017-06-03 7:18 ` [PATCH v2 8/9] powerpc/Kconfig: Enable STRICT_KERNEL_RWX Balbir Singh
2017-06-03 7:18 ` [PATCH v2 9/9] powerpc/mm/ptdump: Dump the first entry of the linear mapping as well Balbir Singh
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=20170605165149.1390a26d@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=bsingharora@gmail.com \
--cc=labbott@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=rashmica.g@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).