1. 10 1月, 2015 3 次提交
  2. 10 11月, 2014 1 次提交
  3. 17 7月, 2014 6 次提交
    • A
      amdkfd: Add interrupt handling module · b3f5e6b4
      Andrew Lewycky 提交于
      This patch adds the interrupt handling module, in kfd_interrupt.c, and its
      related members in different data structures to the amdkfd driver.
      
      The amdkfd interrupt module maintains an internal interrupt ring per amdkfd
      device. The internal interrupt ring contains interrupts that needs further
      handling. The extra handling is deferred to a later time through a workqueue.
      
      There's no acknowledgment for the interrupts we use. The hardware simply queues
      a new interrupt each time without waiting.
      
      The fixed-size internal queue means that it's possible for us to lose
      interrupts because we have no back-pressure to the hardware.
      
      v3:
      
      Move amdkfd from drm/radeon/ to drm/amd/
      Change device init
      Made sure spin lock is taken only if init is complete
      Moved bool field to the end of the structure
      Signed-off-by: NAndrew Lewycky <Andrew.Lewycky@amd.com>
      Signed-off-by: NOded Gabbay <oded.gabbay@amd.com>
      b3f5e6b4
    • B
      amdkfd: Add device queue manager module · 64c7f8cf
      Ben Goz 提交于
      The queue scheduler divides into two sections, one section is process bounded
      and the other section is device bounded.
      The device bounded section is handled by this module.
      The DQM module handles queue setup, update and tear-down from the device side.
      It also supports suspend/resume operation.
      
      v3: Changed device_init, added the use of the new gart allocation functions an
      Added documentation.
      
      v4:
      
      Fixed a race in DQM queue scheduler where dqm->lock must be held when accessing
      dqm->queue_count and dqm->processes_count. This fixes runlist IB allocation
      failures when DQM is under load.
      
      Fixed race in DQM queue destruction where queues being destroyed must be
      removed from qpd->queues_list prior to preemption, or concurrent queue
      creation activity may reschedule them while their MQD is destroyed.
      
      Fixed EOP queue size setting in CP_HPD_EOP_CONTROL, because the size is
      specified as (log2(size_dwords)-1). The previous calculation assumed the
      size was specified in bytes, which caused interference between EOP queues
      when multiple MEC pipelines were active.
      
      v5:
      
      Move amdkfd from drm/radeon/ to drm/amd/
      Change format of mqd structure to match latest KV firmware
      Add support for AQL queues creation to enable working with open-source HSA
      runtime
      Remove unused unmap_queue function
      Various fixes (Style, typos)
      Signed-off-by: NBen Goz <ben.goz@amd.com>
      Signed-off-by: NJay Cornwall <jay.cornwall@amd.com>
      Signed-off-by: NOded Gabbay <oded.gabbay@amd.com>
      64c7f8cf
    • O
      amdkfd: Add binding/unbinding calls to amd_iommu driver · b17f068a
      Oded Gabbay 提交于
      This patch adds the functions to bind and unbind pasid
      from a device through the amd_iommu driver.
      
      The unbind function is called when the mm_struct of the
      process is released.
      
      The bind function is not called here because it is called
      only in the IOCTLs which are not yet implemented at this
      stage of the patchset.
      Signed-off-by: NOded Gabbay <oded.gabbay@amd.com>
      b17f068a
    • O
      amdkfd: Add basic modules to amdkfd · 19f6d2a6
      Oded Gabbay 提交于
      This patch adds the process module and three helper modules:
      
      - kfd_process, which handles process which open /dev/kfd
      
      - kfd_doorbell, which provides helper functions for doorbell allocation,
        release and mapping to userspace
      
      - kfd_pasid, which provides helper functions for pasid allocation and release
      
      - kfd_aperture, which provides helper functions for managing the LDS, Local GPU
        memory and Scratch memory apertures of the process
      
      This patch only contains the basic kfd_process module, which doesn't contain
      the reference to the queue scheduler. This was done to allow easier code review.
      
      Also, this patch doesn't contain the calls to the IOMMU driver for binding the
      pasid to the device. Again, this was done to allow easier code review
      
      The kfd_process object is created when a process opens /dev/kfd and is closed
      when the mm_struct of that process is teared-down.
      
      v3:
      
      Removed kfd_vidmem.c file
      Replaced direct mmput call to mmu_notifier release
      Removed typedefs
      Moved bool field to end of the structure
      Added new kernel params for gart usage limitation
      Added initialization of sa manager
      Fixed debug messages
      Remove support for LDS in 32 bit
      Changed code to support mmap of doorbell pages from userspace
      Added documentation for apertures
      
      v4: Replaced RCU by SRCU for kfd_process list management
      
      v5:
      
      Move amdkfd from drm/radeon/ to drm/amd/
      Rename kfd_aperture.c to kfd_flat_memory.c
      Protect against multiple init calls
      MQD size is H/W dependent so moved it to device info structure
      Rename kfd_mem_obj structure's members
      Use delayed function for process tear-down
      Signed-off-by: NOded Gabbay <oded.gabbay@amd.com>
      19f6d2a6
    • E
      amdkfd: Add topology module to amdkfd · 5b5c4e40
      Evgeny Pinchuk 提交于
      This patch adds the topology module to the driver. The topology is exposed to
      userspace through the sysfs.
      
      The calls to add and remove a device to/from topology are done by the radeon
      driver.
      
      v3:
      
      The CPU information, that is provided in the topology section of the amdkfd
      driver, is extracted from the CRAT table. Unlike the CPU information located
      in /sys/devices/system/cpu/cpu*, which is extracted from the SRAT table.
      
      While the CPU information provided by the CRAT and the SRAT tables might be
      identical, the node topology might be different. The SRAT table contains the
      topology of CPU nodes only. The CRAT table contains the topology of CPU and GPU
      nodes together (and can be interleaved). For example CPU node 1 in SRAT can be
      CPU node 3 in CRAT. Furthermore it's worth to mention that the CRAT table
      contains only HSA compatible nodes (nodes which are compliant with the HSA
      spec).
      
      To recap, amdkfd exposes a different kind of topology than the one exposed by
      /sys/devices/system/cpu/cpu even though it may contain similar information.
      
      v4:
      
      The topology module doesn't support uevent handling and doesn't notify the
      userspace about runtime modifications. It is up to the userspace to acquire
      snapshots of the topology information created by the amdkfd and exposed
      in sysfs.
      
      The following is an example of how the topology looks on a Kaveri A10-7850K
      system with amdkfd installed:
      
      /sys/devices/virtual/kfd/kfd/
      |
      --- topology/
            |
            |--- generation_id
            |--- system_properties
            |--- nodes/
                  |
                  |--- 0/
                       |
                       |--- gpu_id
                       |--- name
                       |--- properties
                       |--- caches/
                            |
                            |--- 0/
                                 |
                                 |--- properties
                            |--- 1/
                                 |
                                 |--- properties
                            |--- 2/
                                 |
                                 |--- properties
                       |--- io_links/
                            |
                       |--- mem_banks/
                            |
                            |--- 0/
                                 |
                                 |--- properties
                            |--- 1/
                                 |
                                 |--- properties
                            |--- 2/
                                 |
                                 |--- properties
                            |--- 3/
                                 |
                                 |--- properties
      
      v5:
      
      Move amdkfd from drm/radeon/ to drm/amd/
      
      Add a check if dev->gpu pointer is null before accessing it in the
      node_show function in kfd_topology.c
      This situation may occur when amdkfd is loaded and there is a GPU with a CRAT
      table, but that GPU isn't supported by amdkfd
      Signed-off-by: NEvgeny Pinchuk <evgeny.pinchuk@amd.com>
      Signed-off-by: NOded Gabbay <oded.gabbay@amd.com>
      5b5c4e40
    • O
      amdkfd: Add amdkfd skeleton driver · 4a488a7a
      Oded Gabbay 提交于
      This patch adds the amdkfd skeleton driver. The driver does nothing except
      define a /dev/kfd device.
      
      It returns -ENODEV on all amdkfd IOCTLs.
      
      v3: Move bool field to the end of structure, removed the pmc ioctls and added
      a meaningful error message for ioctl error.
      
      v5:
      
      Create a new folder drm/amd and move amdkfd from drm/radeon/ to drm/amd/
      Remove scheduler_class from kfd_priv.h as it was never used
      Add skeleton implementation of the Get Version IOCTL
      
      v6:
      Update module version to the correct number and remove the "default m" from the
      Kconfig file
      Signed-off-by: NOded Gabbay <oded.gabbay@amd.com>
      4a488a7a