1. 30 6月, 2017 1 次提交
  2. 28 6月, 2017 1 次提交
  3. 02 6月, 2017 2 次提交
  4. 19 5月, 2017 2 次提交
  5. 18 5月, 2017 1 次提交
    • P
      ramblock: add new hmp command "info ramblock" · be9b23c4
      Peter Xu 提交于
      To dump information about ramblocks. It looks like:
      
      (qemu) info ramblock
                    Block Name    PSize              Offset               Used              Total
                  /objects/mem    2 MiB  0x0000000000000000 0x0000000080000000 0x0000000080000000
                      vga.vram    4 KiB  0x0000000080060000 0x0000000001000000 0x0000000001000000
          /rom@etc/acpi/tables    4 KiB  0x00000000810b0000 0x0000000000020000 0x0000000000200000
                       pc.bios    4 KiB  0x0000000080000000 0x0000000000040000 0x0000000000040000
        0000:00:03.0/e1000.rom    4 KiB  0x0000000081070000 0x0000000000040000 0x0000000000040000
                        pc.rom    4 KiB  0x0000000080040000 0x0000000000020000 0x0000000000020000
          0000:00:02.0/vga.rom    4 KiB  0x0000000081060000 0x0000000000010000 0x0000000000010000
         /rom@etc/table-loader    4 KiB  0x00000000812b0000 0x0000000000001000 0x0000000000001000
            /rom@etc/acpi/rsdp    4 KiB  0x00000000812b1000 0x0000000000001000 0x0000000000001000
      
      Ramblock is something hidden internally in QEMU implementation, and this
      command should only be used by mostly QEMU developers on RAM stuff. It
      is not a command suitable for QMP interface. So only HMP interface is
      provided for it.
      Reviewed-by: NDr. David Alan Gilbert <dgilbert@redhat.com>
      Signed-off-by: NPeter Xu <peterx@redhat.com>
      Message-Id: <1494562661-9063-4-git-send-email-peterx@redhat.com>
      Signed-off-by: NDr. David Alan Gilbert <dgilbert@redhat.com>
      be9b23c4
  6. 17 5月, 2017 1 次提交
  7. 09 5月, 2017 2 次提交
  8. 04 5月, 2017 4 次提交
  9. 21 4月, 2017 3 次提交
  10. 16 3月, 2017 1 次提交
  11. 02 3月, 2017 1 次提交
  12. 01 3月, 2017 3 次提交
  13. 24 2月, 2017 4 次提交
  14. 22 2月, 2017 3 次提交
  15. 01 2月, 2017 1 次提交
  16. 13 1月, 2017 2 次提交
  17. 14 11月, 2016 1 次提交
  18. 11 11月, 2016 1 次提交
    • A
      hmp: Make block_stream set an explicit job ID · 11d6fbe0
      Alberto Garcia 提交于
      A job ID is always required in order to create a block job on a
      non-root node. The default ID (obtained with bdrv_get_device_name())
      is otherwise empty in this scenario and the job cannot be created.
      
      The HMP block_stream command doesn't set a job ID and therefore it
      doesn't allow streaming to intermediate nodes. One solution is to add
      an extra parameter to set a job ID. The other solution is to simply
      use the node name passed to block_stream as job ID. This won't work
      if it's automatically generated (because it contains a '#') but is
      otherwise simple enough for all other cases.
      
      This way 'block_stream node3' will create a job with the ID 'node3'
      and the good old 'block_stream virtio0' will keep the previous
      behaviour and use 'virtio0' for the job ID.
      Signed-off-by: NAlberto Garcia <berto@igalia.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      11d6fbe0
  19. 31 10月, 2016 1 次提交
  20. 30 10月, 2016 2 次提交
  21. 24 10月, 2016 1 次提交
  22. 13 10月, 2016 2 次提交