On Thu, Dec 28, 2000 at 10:52:06AM -0500, Kevin Lawton wrote:
[In dt-testbed/README]
> - I coded the DT sequences, to preserve guest state including the stack,
> even for boundary cases like when the stack is at its limit. Perhaps if
> we could make the assumption that we could safely use the guest stack
> (read...option), we could generate even more efficient code.
Perhaps we could use a double-fault handler to fix things up if we overrun
the guest stack from within the dt'd code? This should give us best-of-both
worlds behavor: it should be fairly rare that there isn't enough stack, and
this way we incur overhead of changing the SS back and forth, and going
outside our cache line only (more overhead, but the probablity should be low
enough that it's worth it) only if we need it.
I think if we get this in well, we can shave our shimms down pretty thin,
and get some decent performace out of this beast.
-=- James Mastros
--
midendian: She never sleeps.
mousetrout: But I do. I just regret it after I wake up.
AIM: theorbtwo homepage: http://www.rtweb.net/theorb/
ICBM: 40:04:15.100 N, 76:18:53.165 W
