From: Anton Blanchard <anton@samba.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: what is ~1MB of memory allocated at fffea000-fffff000 on ppc64?
Date: Mon, 27 Aug 2007 18:19:56 -0500 [thread overview]
Message-ID: <20070827231956.GA5149@kryten> (raw)
In-Reply-To: <46D34A9E.7010501@nortel.com>
Hi,
> For some background, we're running an emulator that uses a null pointer
> value of 0xffff0000 and we want any accesses to that address to trap.
Weird :)
> Do you anticipate any issues with the following change?
>
> -#define TASK_SIZE_USER32 (0x0000000100000000UL - (1*PAGE_SIZE))
> +#define TASK_SIZE_USER32 (0x00000000FFFF0000UL - (1*PAGE_SIZE))
Should be OK, for a 64kB kernel we will put the stack top at 0xFFFF0000
anyway.
Anton
next prev parent reply other threads:[~2007-08-27 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 20:22 what is ~1MB of memory allocated at fffea000-fffff000 on ppc64? Chris Friesen
2007-08-27 20:31 ` Anton Blanchard
2007-08-27 22:05 ` Chris Friesen
2007-08-27 23:19 ` Anton Blanchard [this message]
2007-08-28 5:19 ` Paul Mackerras
2007-08-28 15:15 ` Chris Friesen
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=20070827231956.GA5149@kryten \
--to=anton@samba.org \
--cc=cfriesen@nortel.com \
--cc=linuxppc-dev@ozlabs.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 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).