All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Weiner <jw@emlix.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Paul Mundt <lethal@linux-sh.org>,
	os@emlix.com, dhowells@redhat.com, rmk@arm.linux.org.uk,
	cooloney@kernel.org, geert@linux-m68k.org, vapier.adi@gmail.com,
	gerg@uclinux.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -v3] flat: fix data sections alignment
Date: Thu, 9 Apr 2009 16:25:53 +0200	[thread overview]
Message-ID: <20090409142553.GA3330@emlix.com> (raw)
In-Reply-To: <20090402135343.d18d17a5.akpm@linux-foundation.org>

On Thu, Apr 02, 2009 at 01:53:43PM -0700, Andrew Morton wrote:
> On Tue, 10 Mar 2009 16:33:50 +0900
> Paul Mundt <lethal@linux-sh.org> wrote:
> 
> > On Thu, Mar 05, 2009 at 06:00:59PM +0100, Oskar Schirmer wrote:
> > > The flat loader uses an architecture's flat_stack_align() to align the
> > > stack but assumes word-alignment is enough for the data sections.
> > > 
> > > However, on the Xtensa S6000 we have registers up to 128bit width
> > > which can be used from userspace and therefor need userspace stack and
> > > data-section alignment of at least this size.
> > > 
> > > This patch drops flat_stack_align() and uses the same alignment that
> > > is required for slab caches, ARCH_SLAB_MINALIGN, or wordsize if it's
> > > not defined by the architecture.
> > > 
> > > It also fixes m32r which was obviously kaput, aligning an
> > > uninitialized stack entry instead of the stack pointer.
> > > 
> > > Signed-off-by: Oskar Schirmer <os@emlix.com>
> > > Signed-off-by: Johannes Weiner <jw@emlix.com>
> > > Cc: David Howells <dhowells@redhat.com>
> > > Cc: Russell King <rmk@arm.linux.org.uk>
> > > Cc: Bryan Wu <cooloney@kernel.org>
> > > Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> > > Cc: Paul Mundt <lethal@linux-sh.org>
> > > Cc: Greg Ungerer <gerg@uclinux.org>
> > > Cc: Mike Frysinger <vapier.adi@gmail.com>
> > 
> > The updated version looks ok to me anyways, and it's certainly an
> > improvement over defining the same alignment requirements all over the
> > place.
> > 
> > Acked-by: Paul Mundt <lethal@linux-sh.org>
> 
> Quite a few people expressed quite a few reservations over v2.
> 
> Are we all OK with a v3 merge?

Paul and Mike had complaints.  Paul acked the last revision.  Mike?
We need this for upstream to compile on our configuration.

	Hannes

  reply	other threads:[~2009-04-09 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 17:00 [PATCH -v3] flat: fix data sections alignment Oskar Schirmer
2009-03-10  7:33 ` Paul Mundt
2009-04-02 20:53   ` Andrew Morton
2009-04-09 14:25     ` Johannes Weiner [this message]
2009-05-05 14:08       ` Johannes Weiner
2009-05-27 11:49         ` Johannes Weiner
2009-05-27 20:43           ` Andrew Morton
2009-05-28  0:08             ` Paul Mundt
2009-05-28  0:16               ` Andrew Morton
2009-06-01  7:44                 ` Michal Simek
2009-06-02 14:15                 ` Oskar Schirmer
2009-06-02 18:57                   ` Mike Frysinger
2009-06-10  4:34                     ` Greg Ungerer
2009-05-27 18:05       ` Mike Frysinger

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=20090409142553.GA3330@emlix.com \
    --to=jw@emlix.com \
    --cc=akpm@linux-foundation.org \
    --cc=cooloney@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=os@emlix.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=vapier.adi@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 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.