From: Olaf Hering <olh@suse.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] force stackpointer alignment in 64bit kernel
Date: Sat, 4 Mar 2006 00:23:34 +0100 [thread overview]
Message-ID: <20060303232334.GA9577@suse.de> (raw)
In-Reply-To: <3E10742C-61F9-417C-A191-C0C8C46A4529@kernel.crashing.org>
On Fri, Mar 03, Segher Boessenkool wrote:
> > The stackpointer came from 32bit code, which appearently has different
> > alignment rules than 64bit code. The chain was yaboot -> zImage ->
> > vmlinux
> > Force the stackpointer to be 16 byte aligned.
>
> The stack pointer is required to be 16-byte aligned when the
> client program is started, on 32-bit as well.
See http://ozlabs.org/pipermail/linuxppc-dev/2006-March/021342.html
Either yaboot and/or zImage need to force a stack alignment, or we apply
the 2 liner.
next prev parent reply other threads:[~2006-03-03 23:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 13:57 alignment bugs in prom_init Olaf Hering
2006-03-03 14:39 ` Andreas Schwab
2006-03-03 15:27 ` Olaf Hering
2006-03-03 15:50 ` Jerry Van Baren
2006-03-03 16:14 ` Jerry Van Baren
2006-03-03 17:24 ` Olaf Hering
2006-03-03 16:52 ` [PATCH] Workaround gcc bug #26549 which causes pointers to be truncated Olaf Hering
2006-03-03 19:16 ` [PATCH] force stackpointer alignment in 64bit kernel Olaf Hering
2006-03-03 19:23 ` Olaf Hering
2006-03-03 19:29 ` Segher Boessenkool
2006-03-03 19:32 ` Segher Boessenkool
2006-03-03 20:09 ` Olaf Hering
2006-03-03 20:40 ` Olaf Hering
2006-03-03 23:23 ` Olaf Hering [this message]
2006-03-03 23:45 ` Paul Nasrat
2006-03-04 0:09 ` Segher Boessenkool
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=20060303232334.GA9577@suse.de \
--to=olh@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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.