1. 27 6月, 2020 1 次提交
    • S
      conf: fix zPCI address auto-generation on s390 · 07659100
      Shalini Chellathurai Saroja 提交于
      Let us fix the issues with zPCI address validation and auto-generation
      on s390.
      
      Currently, there are two issues with handling the ZPCI address
      extension. Firstly, when the uid is to be auto-generated with a
      specified fid, .i.e.:
      
          ...
          <address type='pci'>
              <zpci fid='0x0000001f'/>
          </address>
          ...
      
      we expect uid='0x0001' (or the next available uid for the domain).
      However, we get a parsing error:
      
          $ virsh define zpci.xml
          error: XML error: Invalid PCI address uid='0x0000', must be > 0x0000
          and <= 0xffff
      
      Secondly, when the uid is specified explicitly with the invalid
      numerical value '0x0000', we actually expect the parsing error above.
      However, the domain is being defined and the uid value is silently
      changed to a valid value.
      
      The first issue is a bug and the second one is undesired behaviour, and
      both issues are related to how we (in-band) signal invalid values for
      uid and fid. So let's fix the XML parsing to do validation based on what
      is actually specified in the XML.
      
      The first issue is also related to the current code behaviour, which
      is, if either uid or fid is specified by the user, it is incorrectly
      assumed that both uid and fid are specified. This bug is fixed by
      identifying when the user specified ZPCI address is incomplete and
      auto-generating the missing ZPCI address.
      Signed-off-by: NBjoern Walk <bwalk@linux.ibm.com>
      Signed-off-by: NBoris Fiuczynski <fiuczy@linux.ibm.com>
      Signed-off-by: NShalini Chellathurai Saroja <shalini@linux.ibm.com>
      Reviewed-by: NAndrea Bolognani <abologna@redhat.com>
      07659100
  2. 26 6月, 2020 1 次提交
  3. 23 6月, 2020 1 次提交
  4. 16 6月, 2020 1 次提交
  5. 14 3月, 2020 1 次提交
  6. 25 2月, 2020 1 次提交
  7. 07 1月, 2020 1 次提交
  8. 03 1月, 2020 1 次提交
  9. 17 12月, 2019 2 次提交
  10. 15 11月, 2019 1 次提交
  11. 13 11月, 2019 1 次提交
  12. 12 11月, 2019 1 次提交
  13. 11 11月, 2019 1 次提交
    • P
      util: pci: Remove always-false condition · e39d3424
      Peter Krempa 提交于
      Commit d19c2142 modified the condition so that it checks whether the
      value is more than 0xFFFFFFFF. Since addr->domain is an unsigned int, it
      will never be more than that.
      
      Remove the whole check
      
      src/util/virpci.c:1291:22: error: result of comparison 'unsigned int' > 4294967295 is always false [-Werror,-Wtautological-type-limit-compare]
          if (addr->domain > 0xFFFFFFFF) {
              ~~~~~~~~~~~~ ^ ~~~~~~~~~~
      Signed-off-by: NPeter Krempa <pkrempa@redhat.com>
      e39d3424
  14. 21 10月, 2019 2 次提交
  15. 16 10月, 2019 4 次提交
  16. 15 10月, 2019 1 次提交
  17. 14 10月, 2019 1 次提交
  18. 23 8月, 2019 4 次提交
  19. 16 8月, 2019 1 次提交
  20. 14 8月, 2019 5 次提交
  21. 06 8月, 2019 7 次提交
  22. 19 7月, 2019 1 次提交