2
0

pci-testdev.rst 1.6 KB

123456789101112131415161718192021222324252627282930313233343536373839
  1. ====================
  2. QEMU PCI test device
  3. ====================
  4. ``pci-testdev`` is a device used for testing low level IO.
  5. The device implements up to three BARs: BAR0, BAR1 and BAR2.
  6. Each of BAR 0+1 can be memory or IO. Guests must detect
  7. BAR types and act accordingly.
  8. BAR 0+1 size is up to 4K bytes each.
  9. BAR 0+1 starts with the following header:
  10. .. code-block:: c
  11. typedef struct PCITestDevHdr {
  12. uint8_t test; /* write-only, starts a given test number */
  13. uint8_t width_type; /*
  14. * read-only, type and width of access for a given test.
  15. * 1,2,4 for byte,word or long write.
  16. * any other value if test not supported on this BAR
  17. */
  18. uint8_t pad0[2];
  19. uint32_t offset; /* read-only, offset in this BAR for a given test */
  20. uint32_t data; /* read-only, data to use for a given test */
  21. uint32_t count; /* for debugging. number of writes detected. */
  22. uint8_t name[]; /* for debugging. 0-terminated ASCII string. */
  23. } PCITestDevHdr;
  24. All registers are little endian.
  25. The device is expected to always implement tests 0 to N on each BAR, and to add new
  26. tests with higher numbers. In this way a guest can scan test numbers until it
  27. detects an access type that it does not support on this BAR, then stop.
  28. BAR2 is a 64bit memory BAR, without backing storage. It is disabled
  29. by default and can be enabled using the ``membar=<size>`` property. This
  30. can be used to test whether guests handle PCI BARs of a specific
  31. (possibly quite large) size correctly.