1. 07 Apr, 2020 1 commit
  2. 02 Apr, 2020 1 commit
  3. 01 Apr, 2020 4 commits
    • Mauro Carvalho Chehab's avatar
      MAINTAINERS: drop an old reference to stm32 pwm timers doc · 8967918e
      Mauro Carvalho Chehab authored
      The DT files for pwm were merged and converted to json.
      The new reference is already at the maintainers file, so
      just drop the obsoleted one.
      Fixes: 56fb34d8
       ("dt-bindings: mfd: Convert stm32 timers bindings to json-schema")
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+huawei@kernel.org>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
    • Mauro Carvalho Chehab's avatar
      MAINTAINERS: dt: update etnaviv file reference · a3cc3345
      Mauro Carvalho Chehab authored
      The etnaviv file was converted to json and renamed.
      Update its reference accordingly.
      Fixes: 90aeca87
       ("dt-bindings: display: Convert etnaviv to json-schema")
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+huawei@kernel.org>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
    • Jason Wang's avatar
      vDPA: introduce vDPA bus · 961e9c84
      Jason Wang authored
      vDPA device is a device that uses a datapath which complies with the
      virtio specifications with vendor specific control path. vDPA devices
      can be both physically located on the hardware or emulated by
      software. vDPA hardware devices are usually implemented through PCIE
      with the following types:
      - PF (Physical Function) - A single Physical Function
      - VF (Virtual Function) - Device that supports single root I/O
        virtualization (SR-IOV). Its Virtual Function (VF) represents a
        virtualized instance of the device that can be assigned to different
      - ADI (Assignable Device Interface) and its equivalents - With
        technologies such as Intel Scalable IOV, a virtual device (VDEV)
        composed by host OS utilizing one or more ADIs. Or its equivalent
        like SF (Sub function) from Mellanox.
      >From a driver's perspective, depends on how and where the DMA
      translation is done, vDPA devices are split into two types:
      - Platform specific DMA translation - From the driver's perspective,
        the device can be used on a platform where device access to data in
        memory is limited and/or translated. An example is a PCIE vDPA whose
        DMA request was tagged via a bus (e.g PCIE) specific way. DMA
        translation and protection are done at PCIE bus IOMMU level.
      - Device specific DMA translation - The device implements DMA
        isolation and protection through its own logic. An example is a vDPA
        device which uses on-chip IOMMU.
      To hide the differences and complexity of the above types for a vDPA
      device/IOMMU options and in order to present a generic virtio device
      to the upper layer, a device agnostic framework is required.
      This patch introduces a software vDPA bus which abstracts the
      common attributes of vDPA device, vDPA bus driver and the
      communication method (vdpa_config_ops) between the vDPA device
      abstraction and the vDPA bus driver. This allows multiple types of
      drivers to be used for vDPA device like the virtio_vdpa and vhost_vdpa
      driver to operate on the bus and allow vDPA device could be used by
      either kernel virtio driver or userspace vhost drivers as:
         virtio drivers  vhost drivers
                |             |
          [virtio bus]   [vhost uAPI]
                |             |
         virtio device   vhost device
         virtio_vdpa drv vhost_vdpa drv
                   \       /
                  [vDPA bus]
                  vDPA device
                  hardware drv
                  [hardware bus]
                  vDPA hardware
      With the abstraction of vDPA bus and vDPA bus operations, the
      difference and complexity of the under layer hardware is hidden from
      upper layer. The vDPA bus drivers on top can use a unified
      vdpa_config_ops to control different types of vDPA device.
      Signed-off-by: default avatarJason Wang <jasowang@redhat.com>
      Link: https://lore.kernel.org/r/20200326140125.19794-6-jasowang@redhat.com
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
    • Jason Wang's avatar
      vhost: factor out IOTLB · 0bbe3066
      Jason Wang authored
      This patch factors out IOTLB into a dedicated module in order to be
      reused by other modules like vringh. User may choose to enable the
      automatic retiring by specifying VHOST_IOTLB_FLAG_RETIRE flag to fit
      for the case of vhost device IOTLB implementation.
      Signed-off-by: default avatarJason Wang <jasowang@redhat.com>
      Link: https://lore.kernel.org/r/20200326140125.19794-4-jasowang@redhat.com
      Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
  4. 31 Mar, 2020 1 commit
  5. 30 Mar, 2020 2 commits
  6. 29 Mar, 2020 1 commit
  7. 28 Mar, 2020 1 commit
  8. 27 Mar, 2020 2 commits
  9. 26 Mar, 2020 11 commits
  10. 25 Mar, 2020 4 commits
  11. 24 Mar, 2020 4 commits
  12. 23 Mar, 2020 3 commits
  13. 21 Mar, 2020 2 commits
  14. 20 Mar, 2020 3 commits