From: "Chris Friesen" <cfriesen@nortel.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, Anton Blanchard <anton@samba.org>
Subject: Re: what is ~1MB of memory allocated at fffea000-fffff000 on ppc64?
Date: Tue, 28 Aug 2007 09:15:29 -0600 [thread overview]
Message-ID: <46D43C11.2070105@nortel.com> (raw)
In-Reply-To: <18131.45155.16087.714489@cargo.ozlabs.ibm.com>
Paul Mackerras wrote:
> Chris Friesen writes:
>>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.
> Can you fix this in userspace instead by moving the stack down below
> 0xffff0000 and then doing munmap(0xffff0000, 0x1000) ?
It sounds like it would work. I'm not entirely clear on how to move the
starting point of the stack though--could you elaborate or point me to a
reference?
Chris
prev parent reply other threads:[~2007-08-28 15:34 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
2007-08-28 5:19 ` Paul Mackerras
2007-08-28 15:15 ` Chris Friesen [this message]
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=46D43C11.2070105@nortel.com \
--to=cfriesen@nortel.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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.