1. 16 11月, 2010 2 次提交
  2. 28 10月, 2010 1 次提交
    • M
      pci: improve w1c mask handling · f9aebe2e
      Michael S. Tsirkin 提交于
      - save/restore must not check w1c bits
        since they are in fact guest controlled
      - clear w1c bits on reset
      
      Note: for express there are different kinds of
      reset, some leave part of config space alone.
      We will likely need a sticky bit mask to implement this.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      f9aebe2e
  3. 19 10月, 2010 2 次提交
  4. 18 10月, 2010 1 次提交
  5. 06 10月, 2010 1 次提交
  6. 21 9月, 2010 1 次提交
  7. 18 9月, 2010 1 次提交
  8. 14 9月, 2010 3 次提交
  9. 08 9月, 2010 3 次提交
  10. 22 7月, 2010 1 次提交
  11. 19 7月, 2010 1 次提交
  12. 12 7月, 2010 8 次提交
  13. 06 7月, 2010 4 次提交
  14. 15 6月, 2010 2 次提交
    • M
      qdev: Revert the hack to let -net nic and pci_add set qdev ID · 1bb65042
      Markus Armbruster 提交于
      Setting the ID in pci_nic_init() is a blatant violation of the
      DeviceState abstraction.  Which even carries a comment advising
      against this:
      
      /* This structure should not be accessed directly.  We declare it here
         so that it can be embedded in individual device state structures.  */
      
      What's worse, it bypasses the code ensuring unique qdev IDs: "-device
      virtio-net-pci,id=foo -net nic,id=foo -net nic,name=foo" happily
      creates three qdevs with ID "foo".  That's because qdev relies on
      qemu_opts_create() to ensure unique IDs, but -net nic uses a different
      QemuOptsList, which means id is in a different namespace.  And its
      name is not checked for uniqueness at all.
      
      -net nic and pci_add are legacy.  Use -device and device_add if you
      want a NIC with a qdev ID.
      
      This reverts what's still left of commit eb54b6dc "qdev: add id=
      support for pci nics."
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      1bb65042
    • D
      Clarify error message when a PCI slot is already in use (v2) · 3709c1b7
      Daniel P. Berrange 提交于
      When mistakenly configuring two devices in the same PCI slot,
      QEMU gives a not entirely obvious message about a 'devfn' being
      in use:
      
      $ qemu -device rtl8139 -device virtio-balloon-pci,bus=pci.0,addr=0x3
      qemu-kvm: -device virtio-balloon-pci,bus=pci.0,addr=0x3: PCI: devfn 24 not available for virtio-balloon-pci, in use by rtl8139
      
      The user does not configure 'devfn' numbers, they use slot+function.
      Thus the error messages should be reported back to the user with that
      same terminology rather than the internal QEMU terminology. This
      patch makes it report:
      
      $ qemu -device rtl8139 -device virtio-balloon-pci,bus=pci.0,addr=0x3
      qemu: -device virtio-balloon-pci,bus=pci.0,addr=0x3.7: PCI: slot 3 function 0 not available for virtio-balloon-pci, in use by rtl8139
      Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3709c1b7
  15. 02 6月, 2010 1 次提交
  16. 31 5月, 2010 2 次提交
  17. 16 5月, 2010 1 次提交
  18. 12 5月, 2010 2 次提交
  19. 21 4月, 2010 1 次提交
  20. 12 4月, 2010 1 次提交
  21. 16 3月, 2010 1 次提交
    • M
      error: Replace qemu_error() by error_report() · 1ecda02b
      Markus Armbruster 提交于
      error_report() terminates the message with a newline.  Strip it it
      from its arguments.
      
      This fixes a few error messages lacking a newline:
      net_handle_fd_param()'s "No file descriptor named %s found", and
      tap_open()'s "vnet_hdr=1 requested, but no kernel support for
      IFF_VNET_HDR available" (all three versions).
      
      There's one place that passes arguments without newlines
      intentionally: load_vmstate().  Fix it up.
      1ecda02b