ee720ee004
agc_driver_dcc_keys_first_write only exercises the import window when the device's own host import resolves the write protection of the imported pages, as the NVIDIA driver does on Linux. CI's devices do not, so the comparison that #2984 adds for BlockMaybeWritten units is not run there. RunImportWindow opens an import window itself over a pending storage image with GuestMemory::ImportWatched and stores the byte already there, which leaves the same stamp without depending on the driver: the image must stay pending and unchanged. A store of a new byte inside a window must still be seen. Devices whose imports are compared print that the window is not tested, as the recorder's (w) test does. Linux only: the Windows path compares imports. TechnicalDebt records that an identical-byte CPU store inside a window cannot be told apart from the import, and that images tracked by layer still upload again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| dev | ||
| user | ||