1. 25 1月, 2019 9 次提交
  2. 22 1月, 2019 3 次提交
  3. 02 1月, 2019 3 次提交
  4. 14 12月, 2018 1 次提交
    • 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
  5. 13 12月, 2018 2 次提交
    • M
      qemu: Don't use -mem-prealloc among with .prealloc=yes · c658764d
      Michal Privoznik 提交于
      https://bugzilla.redhat.com/show_bug.cgi?id=1624223
      
      There are two ways to request memory preallocation on cmd line:
      -mem-prealloc and .prealloc attribute for a memory-backend-file.
      However, as it turns out it's not safe to use both at the same
      time. If -mem-prealloc is used then qemu will fully allocate the
      memory (this is done by actually touching every page that has
      been allocated). Then, if .prealloc=yes is specified,
      mbind(flags = MPOL_MF_STRICT | MPOL_MF_MOVE) is called which:
      
      a) has to (possibly) move the memory to a different NUMA node,
      b) can have no effect when hugepages are in play (thus ignoring user
      request to place memory on desired NUMA nodes).
      
      Prefer -mem-prealloc as it is more backward compatible
      compared to switching to "-numa node,memdev=  + -object
      memory-backend-file".
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      c658764d
    • M
      qemuBuildMemoryBackendProps: Pass @priv instead of its individual members · 9923584c
      Michal Privoznik 提交于
      So far we have two arguments that we are passing to
      qemuBuildMemoryBackendProps() and that are taken from domain
      private data: @qemuCaps and @autoNodeset. In the next commit I
      will use one more item from there. Therefore, instead of having
      it as yet another argument to the function, pass pointer to the
      private data object.
      
      There is one change in qemuDomainAttachMemory() where previously
      @autoNodeset was NULL but now is priv->autoNodeset (which may be
      set). This is safe to do as @autoNodeset is advisory only.
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      9923584c
  6. 04 12月, 2018 1 次提交
  7. 03 12月, 2018 3 次提交
  8. 28 11月, 2018 1 次提交
  9. 16 11月, 2018 1 次提交
    • M
      qemu: add memfd source type · 24b74d18
      Marc-André Lureau 提交于
      Add a new memoryBacking source type "memfd", supported by QEMU (when
      the capability is available).
      
      A memfd is a specialized anonymous memory kind. As such, an anonymous
      source type could be automatically using a memfd. However, there are
      some complications when migrating from different memory backends in
      qemu (mainly due to the internal object naming at this point, but
      there could be more). For now, it is simpler and safer to simply
      introduce a new source type "memfd". Eventually, the "anonymous" type
      could learn to use memfd transparently in a separate change.
      
      The main benefits are that it doesn't need to create filesystem files,
      and it also enforces sealing, providing a bit more safety.
      Signed-off-by: NMarc-André Lureau <marcandre.lureau@redhat.com>
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      24b74d18
  10. 15 11月, 2018 5 次提交
  11. 07 11月, 2018 1 次提交
    • J
      qemu: Restore lost shutdown reason · 296e05b5
      John Ferlan 提交于
      When qemuProcessReconnectHelper was introduced (commit d38897a5)
      reconnection failure used VIR_DOMAIN_SHUTOFF_FAILED; however, that
      was changed in commit bda2f17d to either VIR_DOMAIN_SHUTOFF_CRASHED
      or VIR_DOMAIN_SHUTOFF_UNKNOWN.
      
      When QEMU_CAPS_NO_SHUTDOWN checking was removed in commit fe35b1ad
      the conditional state was just left at VIR_DOMAIN_SHUTOFF_CRASHED.
      
      So introduce qemuDomainIsUsingNoShutdown which will manage the
      condition when the domain was started with -no-shutdown so that
      when/if reconnection failure occurs we can restore the decision
      point used to determine whether CRASHED or UNKNOWN is provided.
      Signed-off-by: NJohn Ferlan <jferlan@redhat.com>
      ACKed-by: NMichal Privoznik <mprivozn@redhat.com>
      296e05b5
  12. 06 11月, 2018 2 次提交
  13. 05 11月, 2018 2 次提交
  14. 30 10月, 2018 1 次提交
  15. 17 10月, 2018 1 次提交
  16. 09 10月, 2018 1 次提交
  17. 03 10月, 2018 1 次提交
  18. 21 9月, 2018 1 次提交
  19. 12 9月, 2018 1 次提交