Tasks, in INTeLese, which is based on the 8086.

My current reading of things is that it may be possible to get away with
one Task State Segment with it's one address in TR for guest processes.
The reason that may be a minimum is you probably want to switch return
stacks, which seems to need hardware support to do tightly. I think. Not
sure. This is just for process switching. Devices can be callee-saves and
hit process offset memory and so on to thier hearts content. I think.
2003/06/16

There are two types of processes in Ha3sm; 0wner and guest. Maybe three,
to have an 0wner with stainless stacks. 0wner processes are kernel
threads, and can see everything, including all guest state. Guest
processes are more constrained than in unix, and sequestered by the
appropriate hardware protections. In particular, they are
segment-sequestered.

Until Ha3sm is true multi-user, and I mean like unix, not WinDoS, we can
fake processes, but Stubbing them out may be illustrative. Or not.

For the full Monty, we'll need at least one TSS and leave it's address in
TR. I think that's necessary to change rings on a surprise.
