> > > > > > I was thinking about this part. Why is this a violation of physics? A > > > perfect emulator can run itself like the Russian dolls, over and over > > > and over and over again in a nested nested nested fashion > > > > The emulator would be a separate process, loading itself, with the nested > > instance having its own resources. In an arbitrary-context instrumentation > > framework, you've got one instance of this thing in the one kernel, with > > finite resources and you can't arbitrarily allocate more as you go. > You can allocate from the stack and say 'no stack left for probing' if > you are out of stack. What's the stupid problem with that?
It doesn't address the issue of the other state that must be saved/restored as I mentioned (e.g. arbitrary variable state within the subsystem, and variable state within other subsystems like per-CPU flags etc.) -Mike -- Mike Shapiro, Solaris Kernel Development. blogs.sun.com/mws/ _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
