From: Segher Boessenkool <segher@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] force stackpointer alignment in 64bit kernel
Date: Fri, 3 Mar 2006 20:29:40 +0100 [thread overview]
Message-ID: <3E10742C-61F9-417C-A191-C0C8C46A4529@kernel.crashing.org> (raw)
In-Reply-To: <20060303191633.GA7792@suse.de>
> 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.
> /* Make sure we are running in 64 bits mode */
> + addi r1,r1,16
> + rlwinm r1,r1,0,0,28
> bl .enable_64b_mode
Not addi +16, not -16, just no addi at all...
Segher
next prev parent reply other threads:[~2006-03-03 19:29 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 [this message]
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
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=3E10742C-61F9-417C-A191-C0C8C46A4529@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olh@suse.de \
/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).