Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 21 11月, 2019 7 次提交
  3. 13 11月, 2019 1 次提交
  5. 07 11月, 2019 1 次提交
  7. 14 10月, 2019 1 次提交
  9. 10 10月, 2019 2 次提交
    • D
      qemu: Add capability for the ccf-assist pSeries feature · 86a8e5a8
      由 Daniel Henrique Barboza 提交于 
      Linux kernel 5.1 added a new PPC KVM capability named
KVM_PPC_CPU_CHAR_BCCTR_FLUSH_ASSIST, which is exposed to the QEMU guest
since QEMU commit 8ff43ee404d under a new sPAPR capability called
SPAPR_CAP_CCF_ASSIST. This cap indicates whether the processor supports
hardware acceleration for the count cache flush workaround, which
is a software workaround that flushes the count cache on context
switch. If the processor has this hardware acceleration, the software
flush can be shortened, resulting in performance gain.

This hardware acceleration is defaulted to 'off' in QEMU. The reason
is that earlier versions of the Power 9 processor didn't support
it (it is available on Power 9 DD2.3 and newer), and defaulting this
option to 'on' would break migration compatibility between the Power 9
processor class.

However, the user running a P9 DD2.3+ hypervisor might want to create
guests with ccf-assist=on, accepting the downside of only being able
to migrate them only between other P9 DD2.3+ hosts running upstream
kernel 5.1+, to get a performance boost.

This patch adds this new capability to Libvirt, with the name of
QEMU_CAPS_MACHINE_PSERIES_CAP_CCF_ASSIST.
Reviewed-by: NCole Robinson <crobinso@redhat.com>
Signed-off-by: NDaniel Henrique Barboza <danielhb413@gmail.com>
      86a8e5a8
    • J
      qemu: add ramfb capability · 9bfcf0f6
      由 Jonathon Jongsma 提交于 
      Add a qemu capbility to see if the standalone ramfb device is available.
Reviewed-by: NCole Robinson <crobinso@redhat.com>
Signed-off-by: NJonathon Jongsma <jjongsma@redhat.com>
      9bfcf0f6
  11. 09 10月, 2019 1 次提交
  13. 07 10月, 2019 2 次提交
  15. 30 9月, 2019 1 次提交
  17. 25 9月, 2019 1 次提交
  19. 19 9月, 2019 1 次提交
  21. 06 9月, 2019 2 次提交
  23. 14 8月, 2019 1 次提交
  25. 07 8月, 2019 1 次提交
    • C
      qemu: conf: Cache domCaps in qemuCaps · 270583ed
      由 Cole Robinson 提交于 
      qemuCaps is tied to a binary on disk. domCaps is tied to a combo
of binary+machine+arch+virttype values. For the qemu driver this almost
entirely translates to a permutation of qemuCaps though

Upcoming patches want to use the domCaps data store at XML validate
time, but we need to cache the data so we aren't repeatedly
regenerating it.

Add a domCapsCache hash table to qemuCaps. This ensures that the domCaps
cache is blown away whenever qemuCaps needs to be regenerated. Similarly
when qemuCaps is invalidated, the next call to virQEMUCapsCacheLookup
will unref qemuCaps and free our cache as well.

Adjust virQEMUDriverGetDomainCapabilities to search the cache and add
to it if we don't find a hit.
Signed-off-by: NCole Robinson <crobinso@redhat.com>
Reviewed-by: NReviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
      270583ed
  27. 15 7月, 2019 1 次提交
  29. 20 6月, 2019 4 次提交
  31. 19 6月, 2019 1 次提交
  33. 12 6月, 2019 1 次提交
    • E
      backup: Add two new qemu capabilities · 6abda7a4
      由 Eric Blake 提交于 
      Add two capabilities for testing features required for the upcoming
virDomainBackupBegin: use block-dirty-bitmap-merge as the generic
witness of bitmap support needed for checkpoints (since all of the
bitmap management functionalities were finalized in the same qemu 4.0
release), and the bitmap parameter to nbd-server-add for pull-mode
backup support.  Even though both capabilities are likely to be
present or absent together (that is, it is unlikely to encounter a
qemu that backports only one of the two), it still makes sense to keep
two capabilities as the two uses are orthogonal (full backups don't
require checkpoints, push mode backups don't require NBD bitmap
support, and checkpoints can be used for more than just incremental
backups).

Existing code is not affected by the new capabilities.
Signed-off-by: NEric Blake <eblake@redhat.com>
Acked-by: NPeter Krempa <pkrempa@redhat.com>
      6abda7a4
  35. 03 6月, 2019 1 次提交
  37. 25 4月, 2019 1 次提交
  39. 15 4月, 2019 2 次提交
  41. 12 4月, 2019 2 次提交
  43. 10 4月, 2019 2 次提交
    • M
      domain capabilities: Expose firmware auto selection feature · 5b9819ee
      由 Michal Privoznik 提交于 
      If a management application wants to use firmware auto selection
feature it can't currently know if the libvirtd it's talking to
support is or not. Moreover, it doesn't know which values that
are accepted for the @firmware attribute of <os/> when parsing
will allow successful start of the domain later, i.e. if the mgmt
application wants to use 'bios' whether there exists a FW
descriptor in the system that describes bios.

This commit then adds 'firmware' enum to <os/> element in
<domainCapabilities/> XML like this:

  <enum name='firmware'>
    <value>bios</value>
    <value>efi</value>
  </enum>

We can see both 'bios' and 'efi' listed which means that there
are descriptors for both found in the system (matched with the
machine type and architecture reported in the domain capabilities
earlier and not shown here).
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
Acked-by: NLaszlo Ersek <lersek@redhat.com>
      5b9819ee
    • P
      util: Move enum convertors into virenum.(c|h) · 285c5f28
      由 Peter Krempa 提交于 
      virutil.(c|h) is a very gross collection of random code. Remove the enum
handlers from there so we can limit the scope where virtutil.h is used.
Signed-off-by: NPeter Krempa <pkrempa@redhat.com>
Reviewed-by: NJán Tomko <jtomko@redhat.com>
      285c5f28
  45. 03 4月, 2019 3 次提交