>Ah, life on the bleeding edge. If we could #ifdef and if ()
>our way around this and it worked on Pentium+ and AMDs, it might
>make a good option.
Perhaps we shouldn't rely on things that aren't warranted? Yes,
yes, if it's only a nice gimmick we program using such things,
I have no problems with #ifdefs and if()s, but not the
basic architecture. Or do we want to overthrow our architecture
when Intel changes some undocumented features? We haven't
the power of Microsoft... ;)
Other things... page tables. We may want to write a pager that
pages for our guest os. This makes the guest os pager out of
work an we (host os and monitor) hold control over all pages.
Or we give a set of pages to our guest (must be done while
starting up, has anybody any idea, how to do?), then guest os
pager works for guest tasks and guest may easily do swapping
on hard disks. Don't know, what better, any comments?
There was a discussion about page tables - I found in mailing
list archiv. Were there determined some facts or is this
a collection of ideas?
And another question: why do you want to scan guest code?
May be we have to do this while emulating some instructions
to detect what guest really wants to do, but I see no need
to scan the whole code?
jens
