Re: Question about inter-thread stack references

glen herrmannsfeldt <gah@ugcs.caltech.edu>
Sun, 18 Jan 2015 23:24:29 +0000 (UTC)

          From comp.compilers

Related articles
[3 earlier articles]
Re: Question about inter-thread stack references gah@ugcs.caltech.edu (glen herrmannsfeldt) (2015-01-17)
Re: Question about inter-thread stack references gneuner2@comcast.net (George Neuner) (2015-01-18)
Re: Question about inter-thread stack references monnier@iro.umontreal.ca (Stefan Monnier) (2015-01-18)
Re: Question about inter-thread stack references kaz@kylheku.com (Kaz Kylheku) (2015-01-18)
Re: Question about inter-thread stack references ivan@ootbcomp.com (Ivan Godard) (2015-01-18)
Re: Question about inter-thread stack references gah@ugcs.caltech.edu (glen herrmannsfeldt) (2015-01-18)
Re: Question about inter-thread stack references gah@ugcs.caltech.edu (glen herrmannsfeldt) (2015-01-18)
Re: Question about inter-thread stack references jgk@panix.com (2015-01-25)
Re: Question about inter-thread stack references kaz@kylheku.com (Kaz Kylheku) (2015-01-25)
Re: Question about inter-thread stack references jgk@panix.com (2015-01-27)
| List of all articles for this month |

From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.compilers
Date: Sun, 18 Jan 2015 23:24:29 +0000 (UTC)
Organization: Aioe.org NNTP Server
References: 15-01-015 15-01-027 15-01-033
Keywords: architecture, storage, history, comment
Posted-Date: 20 Jan 2015 13:24:12 EST

glen herrmannsfeldt <gah@ugcs.caltech.edu> wrote:


(snip, I wrote)
> Yes. OS/360 and successors use a doubly-linked list for linkage and
> register saving, and for reentrant routines usually local variables,
> too.


(snip)


> I believe that OS/360 MVT subtasks run in the same protection key
> as the parent. With MVS, ordinary user tasks all run with the same
> protection key, with segment and page tables updated as needed.


(snip)


> [Yes, OS subtasks started with ATTACH all run in the same address
> space. -John]


Well, all of OS/360, OS/VS1 and OS/VS2 runs in one address space.
For OS/360 all real addresses, for OS/VS1 and OS/VS2 a single 16MB
virtual address space. (MVS is where they started using separate
address spaces.)


Much of the OS is key zero, and readable by everyone.


But I think you are agreeing that subtasks run with the same key
as the parent.


-- glen
[Yes. Now back to compilers. -John]


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.