All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: Dave Martin <dave.martin@linaro.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] [ARM] Use AT() in the linker script to create correct program headers
Date: Fri, 5 Oct 2012 09:45:00 +0100	[thread overview]
Message-ID: <20121005084500.GI4625@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20121001160639.GA31620@obsidianresearch.com>

On Mon, Oct 01, 2012 at 10:06:39AM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 01, 2012 at 04:39:53PM +0100, Dave Martin wrote:
> > >   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
> > >   LOAD           0x008000 0xc0008000 0x00008000 0x372244 0x3a4310 RWE 0x8000
> > 
> > Not related directly to your patch, but I wonder why we don't we see
> > separate r-x and rw- segments?
> 
> I think this is because the sections are not aligned when the
> protections change, and the sections are not sorted by protection
> type.

They aren't sorted by protection type, they're ordered according to what's
required for the kernel - which is to have the init sections together as
one complete block so that it can be freed, and to place all of the kernel
text as close to the beginning of the image as possible.

WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [ARM] Use AT() in the linker script to create correct program headers
Date: Fri, 5 Oct 2012 09:45:00 +0100	[thread overview]
Message-ID: <20121005084500.GI4625@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20121001160639.GA31620@obsidianresearch.com>

On Mon, Oct 01, 2012 at 10:06:39AM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 01, 2012 at 04:39:53PM +0100, Dave Martin wrote:
> > >   Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
> > >   LOAD           0x008000 0xc0008000 0x00008000 0x372244 0x3a4310 RWE 0x8000
> > 
> > Not related directly to your patch, but I wonder why we don't we see
> > separate r-x and rw- segments?
> 
> I think this is because the sections are not aligned when the
> protections change, and the sections are not sorted by protection
> type.

They aren't sorted by protection type, they're ordered according to what's
required for the kernel - which is to have the init sections together as
one complete block so that it can be freed, and to place all of the kernel
text as close to the beginning of the image as possible.

  parent reply	other threads:[~2012-10-05  8:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-30 23:21 [PATCH] [ARM] Use AT() in the linker script to create correct program headers Jason Gunthorpe
2012-09-30 23:21 ` Jason Gunthorpe
2012-10-01 15:39 ` Dave Martin
2012-10-01 15:39   ` Dave Martin
2012-10-01 16:06   ` Jason Gunthorpe
2012-10-01 16:06     ` Jason Gunthorpe
2012-10-01 17:56     ` Dave Martin
2012-10-01 17:56       ` Dave Martin
2012-10-01 18:35       ` Jason Gunthorpe
2012-10-01 18:35         ` Jason Gunthorpe
2012-10-02 10:23         ` Dave Martin
2012-10-02 10:23           ` Dave Martin
2012-10-02 17:47           ` Jason Gunthorpe
2012-10-02 17:47             ` Jason Gunthorpe
2012-10-03 10:43             ` Dave Martin
2012-10-03 10:43               ` Dave Martin
2012-10-03 18:44               ` Jason Gunthorpe
2012-10-03 18:44                 ` Jason Gunthorpe
2012-10-04 11:36                 ` Dave Martin
2012-10-04 11:36                   ` Dave Martin
2012-10-04 17:59                   ` Jason Gunthorpe
2012-10-04 17:59                     ` Jason Gunthorpe
2012-10-08 10:46                     ` Dave Martin
2012-10-08 10:46                       ` Dave Martin
2012-10-09 18:25                       ` Jason Gunthorpe
2012-10-09 18:25                         ` Jason Gunthorpe
2012-10-10  9:55                         ` Dave Martin
2012-10-10  9:55                           ` Dave Martin
2012-10-12 21:24                           ` Jason Gunthorpe
2012-10-12 21:24                             ` Jason Gunthorpe
2012-10-05  8:45     ` Russell King - ARM Linux [this message]
2012-10-05  8:45       ` Russell King - ARM Linux
2012-10-08 10:24       ` Dave Martin
2012-10-08 10:24         ` Dave Martin
2012-10-09 17:37         ` Jason Gunthorpe
2012-10-09 17:37           ` Jason Gunthorpe
2012-10-10  9:18           ` Dave Martin
2012-10-10  9:18             ` Dave Martin

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=20121005084500.GI4625@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=dave.martin@linaro.org \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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.