Jens Nerche wrote: > point of view). Hope I understood and explained it correctly. > But the point about I'm pondering is: how to detect the point of time a > rescan is necessary? Test the D-bit after every instruction is too costly, > but larger time windows may be too large!?? The only time we care is before transferring execution to the guest, which is a good time to check and possibly dump the vcode cache and rescan. Speaking of D and A-bits, when a (virtualized) guest read or write hits a page directory or page table, and when the guest reloads CR3; that's a good time to update guest D & A bits in the PDE/PTE's. > P.S. I'm planning to write some doc about our SBE next days. Have to scan > Kevins virtualization paper and mailing list archiv for that - or has somebody > a summary of all ideas? Kevin? That paper is the closest thing I have to a summary. Isn't the source code self-documenting? :^)
- Another plex86 technical thing Kevin P. Lawton
- Re: Another plex86 technical thing Ramon van Handel
- Re: Another plex86 technical thing Kevin P. Lawton
- RE: Another plex86 technical thing Drew Northup
- Re: Another plex86 technical thing Kevin P. Lawton
- Re: Another plex86 technical thing Jens Nerche
- Re: Another plex86 technical thing Ulrich Weigand
- Re: Another plex86 technical thing Kevin P. Lawton
- Re: Another plex86 technical thing Ramon van Handel
- Re: Another plex86 technical thing Jens Nerche
- Re: Another plex86 technical thing Kevin P. Lawton
- Re: Another plex86 technical thing Jens Nerche
- Re: Another plex86 technical thing Kevin P. Lawton
- RE: Another plex86 technical thing Drew Northup
- Re: Another plex86 technical thing Kevin P. Lawton
- RE: Another plex86 technical thing Ramon van Handel
- Re: Another plex86 technical thing Nick Behnken
- Re: Another plex86 technical thing Ramon van Handel
- Re: Another plex86 technical thing Kevin P. Lawton
- Re: Another plex86 technical thing Jens Nerche
