x86/shadow: OOS doesn't track VAs anymore

The tracking lasted only for about two weeks, but the related comment
parts were never purged.

Amends: 50b74f55e0 ("OOS cleanup: Fixup arrays instead of fixup tables")
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
This commit is contained in:
Jan Beulich committed 2026-01-15 11:48:28 +01:00
1 parent adcac96dff
commit c5e70ef309
1 file changed
+2 -5
+2 -5
View File
@@ -51,13 +51,10 @@
*
* Currently out-of-sync pages are listed in a simple open-addressed
* hash table with a second chance (must resist temptation to radically
* over-engineer hash tables...) The virtual address of the access
* which caused us to unsync the page is also kept in the hash table, as
* a hint for finding the writable mappings later.
* over-engineer hash tables...).
*
* We keep a hash per vcpu, because we want as much as possible to do
* the re-sync on the save vcpu we did the unsync on, so the VA hint
* will be valid.
* the re-sync on the same vcpu we did the unsync on.
*/
#if SHADOW_AUDIT & SHADOW_AUDIT_ENTRIES_FULL
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.