From: Olaf Hering <olh@suse.de>
To: Andrew Morton <akpm@osdl.org>, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PPC64] Remove another fixed address constraint
Date: Mon, 1 Aug 2005 08:29:29 +0200 [thread overview]
Message-ID: <20050801062929.GA22102@suse.de> (raw)
In-Reply-To: <20050725061635.GD19817@localhost.localdomain>
On Mon, Jul 25, David Gibson wrote:
> Presently the LparMap, one of the structures the kernel shares with
> the legacy iSeries hypervisor has a fixed offset address in head.S.
> This patch changes this so the LparMap is a normally initialized
> structure, without fixed address. This allows us to use macros to
> compute some of the values in the structure, which wasn't previously
> possible because the assembler always uses signed-% which gets the
> wrong answers for the computations in question.
>
> Unfortunately, a gcc bug means that doing this requires another
> structure (hvReleaseData) to be initialized in asm instead of C, but
> on the whole the result is cleaner than before.
I think this change caused this compile error in rc4:
{standard input}: Assembler messages:
{standard input}:254: Error: value of 4000000000002080 too large for field of 4 bytes at 0000000000002108
make[1]: *** [arch/ppc64/kernel/LparData.o] Error 1
binutils-2.16.91.0.2
gcc-4.0.2_20050727
next prev parent reply other threads:[~2005-08-01 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 6:16 [PPC64] Remove another fixed address constraint David Gibson
2005-08-01 6:29 ` Olaf Hering [this message]
2005-08-01 6:35 ` David Gibson
2005-08-01 6:45 ` Olaf Hering
2005-08-01 7:10 ` David Gibson
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=20050801062929.GA22102@suse.de \
--to=olh@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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