Skip to content

L
libvirt

openeuler / libvirt

通知 3
Star 0
Fork 0
L
libvirt

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

切换分支/标签
  1. 09 6月, 2016 29 次提交
  3. 08 6月, 2016 3 次提交
  5. 22 8月, 2015 1 次提交
  7. 11 8月, 2015 5 次提交
    • A
      tests: Add a bunch of cpu test case for ppc64 · 818e68c5
      由 Andrea Bolognani 提交于 
      The test cases cover the cpuCompare(), cpuBaseline() and
cpuNodeData() implementation.
      818e68c5
    • A
      tests: Re-enable ppc64 cpu tests · 049df975
      由 Andrea Bolognani 提交于 
      Now that all the changes have been implemented we can run the
test cases once again, after updating them to reflect the new
behaviour.
      049df975
    • A
      tests: Temporarily disable ppc64 cpu tests · 04f5a60d
      由 Andrea Bolognani 提交于 
      The upcoming commits will make heavy modifications to the ppc64
driver, split so that it's easier to review the changes.

Instead of updating the test cases so that they pass, possibly
only to update them again with the following commit, disable them
for the time being.

Another commit will update them all in one go once all required
changes are in place.
      04f5a60d
    • 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
      tests: Improve result handling in cpuTestGuestData() · e5ef51a4
      由 Andrea Bolognani 提交于 
      A test is considered successful if the obtained result matches
the expected result: if that's not the case, whether because a
test that was expected to succeed failed or because a test that
was supposed to fail succeeded, then something's not right and
we want the user to know about this.

On the other hand, if a failure that's unrelated to the bits
we're testing occurs, then the user should be notified even if
the test was expected to fail.

Use different values to tell these two situations apart.

Fix a test case that was wrongly expected to fail as well.
      e5ef51a4
  9. 24 4月, 2015 2 次提交