AbortedChanges

Summary

  1. QEMU test suite: list memory blocks copied from ROM during bootloader tests (both EOS and PowerShot firmwares)
  2. QEMU logging: allow ROM block copying in arbitrary increments, up to 128-bit mixing memory access sizes is allowed too the block must be copied sequentially, from left to right or from right to left or mixed, with no gaps at any moment during the copy operation copying e.g. 16 bytes from/to offset 0, 16 bytes f/t 0x10, 4 bytes f/t 0x20 and 1 byte f/t 0x24 will be considered a 0x25-byte block but copying 16 bytes f/t offset 0, 4 bytes f/t 0x14 and then 4 bytes f/t 0x10 will be treated as 2 adjacent blocks (16 bytes and 8 bytes); that's because of the gap during the copy operation only blocks larger than 0x40 bytes are printed
  3. QEMU logging: experimental option for finding memory blocks copied from ROM to RAM (only 32-bit sequential copies for now)
  4. QEMU logging: fix memory logging selection in complex cases e.g. romr,ramw should only log ROM reads and RAM writes in simple cases (such as just romr or just ramw), hooks are installed only for the selected operation (read or write) in these cases, additional checks will be redundant however, with complex cases such as romr,ramw, hooks are installed for all reads and and all writes so we can no longer rely on the hooks (being installed or not) for filtering the results
  5. QEMU logging: fix task info on Eeko
  6. QEMU logging: quiet some jumps that are not function calls (frequently used on Thumb-2)
  7. QEMU: fix CSS in HTML logs from subdirectories
Changeset 13446:c8351c42cf06 by alex@thinkpad:
QEMU test suite: list memory blocks copied from ROM during bootloader tests<br>(both EOS and PowerShot firmwares)
The file was modifiedcontrib/qemu/tests/run_tests.sh (diff)
Changeset 13445:932f22453de9 by alex@thinkpad:
QEMU logging: allow ROM block copying in arbitrary increments, up to 128-bit<br>mixing memory access sizes is allowed too<br>the block must be copied sequentially, from left to right or from right to left or mixed, with no gaps at any moment during the copy operation<br>copying e.g. 16 bytes from/to offset 0, 16 bytes f/t 0x10, 4 bytes f/t 0x20 and 1 byte f/t 0x24 will be considered a 0x25-byte block<br>but copying 16 bytes f/t offset 0, 4 bytes f/t 0x14 and then 4 bytes f/t 0x10 will be treated as 2 adjacent blocks (16 bytes and 8 bytes); that&#039;s because of the gap during the copy operation<br>only blocks larger than 0x40 bytes are printed
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)
Changeset 13444:1b8c321d30ae by alex@thinkpad:
QEMU logging: experimental option for finding memory blocks copied from ROM to RAM<br>(only 32-bit sequential copies for now)
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)
The file was modifiedcontrib/qemu/qemu-2.5.0.patch (diff)
Changeset 13443:d1af24b7503b by alex@thinkpad:
QEMU logging: fix memory logging selection in complex cases<br>e.g. romr,ramw should only log ROM reads and RAM writes<br>in simple cases (such as just romr or just ramw), hooks are installed only for the selected operation (read or write)<br>in these cases, additional checks will be redundant<br>however, with complex cases such as romr,ramw, hooks are installed for all reads and and all writes<br>so we can no longer rely on the hooks (being installed or not) for filtering the results
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)
Changeset 13442:33ea5e4c6fbc by alex@thinkpad:
QEMU logging: fix task info on Eeko
The file was modifiedcontrib/qemu/eos/eos.c (diff)
The file was modifiedcontrib/qemu/eos/model_list.c (diff)
Changeset 13441:cf0f2eabefff by alex@thinkpad:
QEMU logging: quiet some jumps that are not function calls (frequently used on Thumb-2)
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)
Changeset 13440:51af2a72f23e by alex@thinkpad:
QEMU: fix CSS in HTML logs from subdirectories
The file was modifiedcontrib/qemu/scripts/html_logs.sh (diff)