[xen staging] x86/shadow: OOS doesn't track VAs anymore

[patchbot@xxxxxxx]

commit c5e70ef3094865bbfcb4699b4ac449bf73b75a53
Author:     Jan Beulich <jbeulich@xxxxxxxx>
AuthorDate: Thu Jan 15 11:48:28 2026 +0100
Commit:     Jan Beulich <jbeulich@xxxxxxxx>
CommitDate: Thu Jan 15 11:48:28 2026 +0100

    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: 50b74f55e0c0 ("OOS cleanup: Fixup arrays instead of fixup tables")
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
---
 xen/arch/x86/mm/shadow/oos.c | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/xen/arch/x86/mm/shadow/oos.c b/xen/arch/x86/mm/shadow/oos.c
index d4f167f73f..89e8a3b722 100644
--- a/xen/arch/x86/mm/shadow/oos.c
+++ b/xen/arch/x86/mm/shadow/oos.c
@@ -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
--
generated by git-patchbot for /home/xen/git/xen.git#staging