You need to sign in or sign up before continuing.
  1. 06 9月, 2019 1 次提交
  2. 29 8月, 2019 1 次提交
  3. 25 7月, 2019 1 次提交
    • P
      qemu: driver: blockdevize qemuDomainGetBlockJobInfo · e6f38fdb
      Peter Krempa 提交于
      Use the stored job name rather than passing in the disk alias when
      referring to the job which allows the same code to work also when
      -blockdev will be used.
      
      Note that this API does not require the change to use 'query-job' as it
      will ever only work with blockjobs bound to disks due to the arguments
      which allow only referring to a disk. For the disk-less jobs we'll need
      to add a separate API later.
      
      The change to qemuMonitorGetBlockJobInfo is required as the API was
      stripping the 'drive-' prefix when returning the data which is not
      desired any more.
      Signed-off-by: NPeter Krempa <pkrempa@redhat.com>
      Reviewed-by: NJán Tomko <jtomko@redhat.com>
      e6f38fdb
  4. 18 7月, 2019 9 次提交
  5. 20 6月, 2019 8 次提交
  6. 12 6月, 2019 4 次提交
  7. 21 5月, 2019 2 次提交
  8. 25 4月, 2019 1 次提交
  9. 26 3月, 2019 2 次提交
  10. 15 3月, 2019 1 次提交
  11. 04 2月, 2019 3 次提交
  12. 09 1月, 2019 2 次提交
    • M
      qemu: Use ULL instead of uint64_t for RDMA GID event · f8862714
      Michal Privoznik 提交于
      In the previous commit we are using uint64_t for storing subnet
      prefix and interface id that qemu reports in
      RDMA_GID_STATUS_CHANGED event. We also report them in some debug
      messages. This poses a problem because uint64_t can be UL or ULL
      depending on the host architecture and hence we wouldn't know
      which format to use. Switch to ULL which is big enough and
      doesn't suffer from the issue.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      f8862714
    • Y
      qemu: Process RDMA GID state change event · ed357cef
      Yuval Shaia 提交于
      This event is emitted on the monitor when a GID table in pvrdma device
      is modified and the change needs to be propagate to the backend RDMA
      device's GID table.
      
      The control over the RDMA device's GID table is done by updating the
      device's Ethernet function addresses.
      Usually the first GID entry is determine by the MAC address, the second
      by the first IPv6 address and the third by the IPv4 address. Other
      entries can be added by adding more IP addresses. The opposite is the
      same, i.e. whenever an address is removed, the corresponding GID entry
      is removed.
      
      The process is done by the network and RDMA stacks. Whenever an address
      is added the ib_core driver is notified and calls the device driver's
      add_gid function which in turn update the device.
      
      To support this in pvrdma device we need to hook into the create_bind
      and destroy_bind HW commands triggered by pvrdma driver in guest.
      Whenever a changed is made to the pvrdma device's GID table a special
      QMP messages is sent to be processed by libvirt to update the address of
      the backend Ethernet device.
      Signed-off-by: NYuval Shaia <yuval.shaia@oracle.com>
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      ed357cef
  13. 14 12月, 2018 2 次提交
    • D
      Enforce a standard header file guard symbol name · 568a4172
      Daniel P. Berrangé 提交于
      Require that all headers are guarded by a symbol named
      
        LIBVIRT_$FILENAME
      
      where $FILENAME is the uppercased filename, with all characters
      outside a-z changed into '_'.
      
      Note we do not use a leading __ because that is technically a
      namespace reserved for the toolchain.
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      568a4172
    • D
      Remove all Author(s): lines from source file headers · 60046283
      Daniel P. Berrangé 提交于
      In many files there are header comments that contain an Author:
      statement, supposedly reflecting who originally wrote the code.
      In a large collaborative project like libvirt, any non-trivial
      file will have been modified by a large number of different
      contributors. IOW, the Author: comments are quickly out of date,
      omitting people who have made significant contribitions.
      
      In some places Author: lines have been added despite the person
      merely being responsible for creating the file by moving existing
      code out of another file. IOW, the Author: lines give an incorrect
      record of authorship.
      
      With this all in mind, the comments are useless as a means to identify
      who to talk to about code in a particular file. Contributors will always
      be better off using 'git log' and 'git blame' if they need to  find the
      author of a particular bit of code.
      
      This commit thus deletes all Author: comments from the source and adds
      a rule to prevent them reappearing.
      
      The Copyright headers are similarly misleading and inaccurate, however,
      we cannot delete these as they have legal meaning, despite being largely
      inaccurate. In addition only the copyright holder is permitted to change
      their respective copyright statement.
      Reviewed-by: NErik Skultety <eskultet@redhat.com>
      Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      60046283
  14. 05 12月, 2018 1 次提交
  15. 19 11月, 2018 1 次提交
    • J
      qemu: Add monitor functions to set IOThread params · 3083bf18
      John Ferlan 提交于
      Add functions to set the IOThreadInfo param data for the live guest.
      Modify the _qemuMonitorIOThreadInfo to have a flag to indicate when
      a value was set so that we don't set a value unless it was desired
      to be set.
      
      Based on code originally posted by Pavel Hrdina <phrdina@redhat.com>,
      but extracted into a separate patch. Note that qapi expects to receive
      integer parameters rather than unsigned long long or unsigned int's.
      QEMU does save the value in larger signed 64 bit values eventually.
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      ACKed-by: NMichal Privoznik <mprivozn@redhat.com>
      3083bf18
  16. 17 9月, 2018 1 次提交