9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Stack initialisation
Date: Tue, 29 Aug 2000 18:58:39 +0200	[thread overview]
Message-ID: <20000829185838.N678@cackle.proxima.alt.za> (raw)
In-Reply-To: <200008291645.MAA28515@cse.psu.edu>; from rob pike on Tue, Aug 29, 2000 at 12:45:20PM -0400

On Tue, Aug 29, 2000 at 12:45:20PM -0400, rob pike wrote:
> 
> Are you referring to the local stack?  Each true process (proc) has a
> private stack, so it's possible to do things like place a pointer in high
> memory that points to memory unique to that process, a storage class
> that's hard to get in fully shared memory.
> 
The exact details I don't understand (for i386 - from
/sys/src/alef/lib/386/run.h):

enum
{
	Ptab    = 0xbfff5000,    /* Private stack */
	Execstk = 0xbf001000,    /* Exec stack linkage area */
};

what I would like explained is how these are allocated, or more
appropriately, where does the process get granted permission to use
what seem like two arbitrary areas of memory?

Please keep in mind that I am not up to date with "recent" OS and
architecture developments and memory allocation and virtual memory
are still black magic to me.  Finding the details by searching
through the kernel sources would be very tedious and probably I'd
miss the wood for the trees.

In this particular instance, it may suffice for me to find out whether
in 3rd edition Plan 9 these values are different and what they are,
but actually knowing how they are established would make me a lot
happier.  Of course, if they are arbitrary, then I'll never find out
why reusing code containing the above fails when assigning to an
entity in that area :-(

Thanks for any assistance.

++L


  reply	other threads:[~2000-08-29 16:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-29 16:45 rob pike
2000-08-29 16:58 ` Lucio De Re [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-31 10:25 lucio
2000-08-31  0:25 okamoto
2000-08-30 16:45 forsyth
2000-08-30 16:55 ` Boyd Roberts
2000-08-30 15:26 lucio
2000-08-30 14:35 forsyth
2000-08-30 14:17 lucio
2000-08-30 15:36 ` ozan s. yigit
2000-08-30 16:12   ` Lucio De Re
2000-08-30 16:32     ` Boyd Roberts
2000-08-30 16:44       ` Lucio De Re
2000-08-30 16:59         ` Boyd Roberts
2000-08-30 17:06           ` Lucio De Re
2000-08-31  9:26         ` Elliott Hughes
2000-08-30 13:45 rob pike
2000-08-30 13:44 rob pike
2000-08-30  6:14 okamoto
2000-08-30  6:23 ` Lucio De Re
2000-08-30  5:44 okamoto
2000-08-30  6:00 ` Lucio De Re
2000-08-29 22:08 forsyth
2000-08-30  5:19 ` Lucio De Re
2000-08-29 16:45 rob pike
2000-08-29 14:30 Lucio De Re

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=20000829185838.N678@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /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).