Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt

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

切换分支/标签
  1. 28 8月, 2018 2 次提交
  3. 28 5月, 2018 2 次提交
  5. 16 10月, 2017 2 次提交
  7. 12 10月, 2017 1 次提交
  9. 13 6月, 2017 2 次提交
  11. 27 3月, 2017 2 次提交
  13. 14 3月, 2017 2 次提交
  15. 24 2月, 2017 1 次提交
  17. 25 11月, 2016 1 次提交
    • M
      virstring: Unify string list function names · c2a5a4e7
      由 Michal Privoznik 提交于 
      We have couple of functions that operate over NULL terminated
lits of strings. However, our naming sucks:

virStringJoin
virStringFreeList
virStringFreeListCount
virStringArrayHasString
virStringGetFirstWithPrefix

We can do better:

virStringListJoin
virStringListFree
virStringListFreeCount
virStringListHasString
virStringListGetFirstWithPrefix
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      c2a5a4e7
  19. 15 11月, 2016 4 次提交
  21. 22 9月, 2016 3 次提交
  23. 09 6月, 2016 1 次提交
  25. 02 6月, 2016 1 次提交
    • M
      ppc64Compute: Avoid possible NULL dereference · 09258c3c
      由 Michal Privoznik 提交于 
      cpu/cpu_ppc64.c: In function 'ppc64Compute':
cpu/cpu_ppc64.c:620:27: error: potential null pointer dereference [-Werror=null-dereference]
     if (STRNEQ(guest_model->name, host_model->name)) {
                ~~~~~~~~~~~^~~
cpu/cpu_ppc64.c:620:9: note: in expansion of macro 'STRNEQ'
     if (STRNEQ(guest_model->name, host_model->name)) {
         ^~~~~~
cc1: all warnings being treated as errors
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      09258c3c
  27. 20 5月, 2016 3 次提交
  29. 16 5月, 2016 1 次提交
  31. 22 8月, 2015 3 次提交
  33. 12 8月, 2015 1 次提交
  35. 11 8月, 2015 8 次提交
    • A
      cpu: Forbid model fallback in the ppc64 driver · 344d1675
      由 Andrea Bolognani 提交于 
      Unlike what happens on x86, on ppc64 you can't mix and match CPU
features to obtain the guest CPU you want regardless of the host
CPU, so the concept of model fallback doesn't apply.

Make sure CPU definitions emitted by the driver, eg. as output of
the cpuBaseline() and cpuUpdate() calls, reflect this fact.
      344d1675
    • A
      cpu: Implement backwards compatibility in the ppc64 driver · dee2247a
      由 Andrea Bolognani 提交于 
      All previously recognized CPU models (POWER7_v2.1, POWER7_v2.3,
POWER7+_v2.1 and POWER8_v1.0) are internally converted to the
corrisponding generation name so that existing guests don't stop
working.
      dee2247a
    • A
      cpu: Parse and use PVR masks in the ppc64 driver · 5d0aa93c
      由 Andrea Bolognani 提交于 
      Instead of relying on a hard-coded mask value, read it from the CPU
map XML and use it when looking up models by PVR.
      5d0aa93c
    • A
      cpu: Support multiple PVRs in the ppc64 driver · 59fcc961
      由 Andrea Bolognani 提交于 
      This will allow us to perform PVR matching more broadly, eg. consider
both POWER8 and POWER8E CPUs to be the same even though they have
different PVR values.
      59fcc961
    • A
      cpu: Align ppc64 CPU data with x86 · adb865df
      由 Andrea Bolognani 提交于 
      Use a typedef instead of the plain struct and heap allocation. This
will make it easier to extend the ppc64 specific CPU data later on.
      adb865df
    • A
      cpu: Use ppc64Compute() to implement ppc64DriverCompare() · d574094d
      由 Andrea Bolognani 提交于 
      This ensures comparison of two CPU definitions will be consistent
regardless of the fact that it is performed using cpuCompare() or
cpuGuestData(). The x86 driver uses the same exact code.
      d574094d
    • A
      cpu: CPU model names have to match on ppc64 · 96b2c745
      由 Andrea Bolognani 提交于 
      Limitations of the POWER architecture mean that you can't run
eg. a POWER7 guest on a POWER8 host when using KVM. This applies
to all guests, not just those using VIR_CPU_MATCH_STRICT in the
CPU definition; in fact, exact and strict CPU matching are
basically the same on ppc64.

This means, of course, that hosts using different CPUs have to be
considered incompatible as well.

Change ppc64Compute(), called by cpuGuestData(), to reflect this
fact and update test cases accordingly.

Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1250977
      96b2c745
    • A
      cpu: Never skip CPU model name check in ppc64 driver · 8382136d
      由 Andrea Bolognani 提交于 
      ppc64Compute(), called by cpuNodeData(), is used not only to retrieve
the driver-specific data associated to a guest CPU definition, but
also to check whether said guest CPU is compatible with the host CPU.

If the user is not interested in the CPU data, it's perfectly fine
to pass a NULL pointer instead of a return location, and the
compatibility data returned should not be affected by this. One of
the checks, specifically the one on CPU model name, was however
only performed if the return location was non-NULL.
      8382136d