You need to sign in or sign up before continuing.
  1. 12 9月, 2017 1 次提交
  2. 29 8月, 2017 1 次提交
  3. 02 8月, 2017 1 次提交
  4. 19 7月, 2017 1 次提交
    • J
      docs: schema: make disk driver name attribute optional · b494e09d
      Jim Fehlig 提交于
      /domain/devices/disk/driver/@name is not a required or mandatory
      attribute according to formatdomain, and indeed it was agreed on
      IRC that the attribute is "optional for input, recommended (but
      not required) for output". Currently the schema requires the
      attribute, causing virt-xml-validate to fail on disk config where
      the driver name is not explicitly specified. E.g.
      
      # cat test.xml | grep -A 5 cdrom
          <disk type='file' device='cdrom'>
            <driver type='raw'/>
            <target dev='hdb' bus='ide'/>
            <readonly/>
            <address type='drive' controller='0' bus='0' target='0' unit='1'/>
          </disk>
      
      # virt-xml-validate test.xml
      Relax-NG validity error : Extra element devices in interleave
      test.xml:21: element devices: Relax-NG validity error : Element domain failed to validate content
      test.xml fails to validate
      
      Relaxing the name attribute to be optional fixes the validation
      
      # virt-xml-validate test.xml
      test.xml validates
      b494e09d
  5. 15 7月, 2017 2 次提交
  6. 11 7月, 2017 3 次提交
  7. 27 6月, 2017 1 次提交
  8. 20 6月, 2017 1 次提交
  9. 16 6月, 2017 1 次提交
    • M
      Report more correct information for cache control · cc9f0521
      Martin Kletzander 提交于
      On some platforms the number of bits in the cbm_mask might not be
      divisible by 4 (and not even by 2), so we need to properly count the
      bits.  Similar file, min_cbm_bits, is properly parsed and used, but if
      the number is greater than one, we lose the information about
      granularity when reporting the data in capabilities.  For that matter
      always report granularity, but if it is not the same as the minimum,
      add that information in there as well.
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      cc9f0521
  10. 08 6月, 2017 9 次提交
  11. 07 6月, 2017 1 次提交
  12. 05 6月, 2017 1 次提交
    • E
      Expose resource control capabilities for caches · 0ab409cc
      Eli Qiao 提交于
      Add cache resource control into capabilities for CAT without CDP:
      
        <cache>
          <bank id='0' level='3' type='unified' size='15360' unit='KiB' cpus='0-5'>
            <control min='768' unit='KiB' scope='both' max_allocation='4'/>
          </bank>
        </cache>
      
      and with CDP:
      
        <cache>
          <bank id='0' level='3' type='unified' size='15360' unit='KiB' cpus='0-5'>
            <control min='768' unit='KiB' scope='code' max_allocation='4'/>
            <control min='768' unit='KiB' scope='data' max_allocation='4'/>
          </bank>
        </cache>
      
      Also add new test cases for vircaps2xmltest.
      Signed-off-by: NEli Qiao <liyong.qiao@intel.com>
      0ab409cc
  13. 26 5月, 2017 3 次提交
  14. 18 5月, 2017 2 次提交
    • E
      nodedev: Introduce mdev capability for mediated devices · 88ef73e1
      Erik Skultety 提交于
      Start discovering the mediated devices on the host system and format the
      attributes for the mediated device into the XML. Compared to the parent
      device which reports generic information about the abstract mediated
      devices types, a child device only reports the type name it has been
      instantiated from and the IOMMU group number, since that's device
      specific compared to the rest of the info that can be gathered about
      mediated devices at the moment.
      This patch introduces both the formatting and parsing routines, updates
      nodedev.rng schema, adding a testcase as well.
      
      The resulting mdev child device XML:
      <device>
        <name>mdev_4b20d080_1b54_4048_85b3_a6a62d165c01</name>
        <path>/sys/devices/.../4b20d080-1b54-4048-85b3-a6a62d165c01</path>
        <parent>pci_0000_06_00_0</parent>
        <driver>
          <name>vfio_mdev</name>
        </driver>
        <capability type='mdev'>
          <type id='vendor_supplied_type_id'/>
          <iommuGroup number='NUM'/>
        <capability/>
      <device/>
      
      https://bugzilla.redhat.com/show_bug.cgi?id=1452072Signed-off-by: NErik Skultety <eskultet@redhat.com>
      88ef73e1
    • E
      nodedev: Introduce the mdev capability to a PCI parent device · 500cbc06
      Erik Skultety 提交于
      The parent device needs to report the generic stuff about the supported
      mediated devices types, like device API, available instances, type name,
      etc. Therefore this patch introduces a new nested capability element of
      type 'mdev_types' with the resulting XML of the following format:
      
      <device>
        ...
        <capability type='pci'>
          ...
          <capability type='mdev_types'>
            <type id='vendor_supplied_id'>
              <name>optional_vendor_supplied_codename</name>
              <deviceAPI>vfio-pci</deviceAPI>
              <availableInstances>NUM</availableInstances>
            </type>
              ...
            <type>
              ...
            </type>
          </capability>
        </capability>
        ...
      </device>
      
      https://bugzilla.redhat.com/show_bug.cgi?id=1452072Signed-off-by: NErik Skultety <eskultet@redhat.com>
      500cbc06
  15. 15 5月, 2017 3 次提交
  16. 09 5月, 2017 1 次提交
    • M
      Add host cache information in capabilities · 4ad6a73b
      Martin Kletzander 提交于
      We're only adding only info about L3 caches, we can add more
      later (just by changing one line), but for now that's more than enough
      without overwhelming anyone.
      
      XML snippet of how this should look like (also seen as part of the commit):
      
        <cache>
          <bank id='0' level='3' type='both' size='8192' unit='KiB' cpus='0-7'/>
        </cache>
      Signed-off-by: NMartin Kletzander <mkletzan@redhat.com>
      4ad6a73b
  17. 28 4月, 2017 8 次提交