mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-15 23:25:07 +00:00
48811c4434
The minimum per-IOMMU PRQ queue size is one 4K page, this is more entries than the hardcoded limit of 32 in the current VT-d code. Some devices can support up to 512 outstanding PRQs but underutilized by this limit of 32. Although, 32 gives some rough fairness when multiple devices share the same IOMMU PRQ queue, but far from optimal for customized use case. This extends the per-IOMMU PRQ queue size to four 4K pages and let the devices have as many outstanding page requests as they can. Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Link: https://lore.kernel.org/r/20210720013856.4143880-1-baolu.lu@linux.intel.com Link: https://lore.kernel.org/r/20210818134852.1847070-7-baolu.lu@linux.intel.com Signed-off-by: Joerg Roedel <jroedel@suse.de>
47 lines
1.5 KiB
C
47 lines
1.5 KiB
C
/* SPDX-License-Identifier: GPL-2.0-only */
|
|
/*
|
|
* Copyright © 2015 Intel Corporation.
|
|
*
|
|
* Authors: David Woodhouse <David.Woodhouse@intel.com>
|
|
*/
|
|
|
|
#ifndef __INTEL_SVM_H__
|
|
#define __INTEL_SVM_H__
|
|
|
|
/* Values for rxwp in fault_cb callback */
|
|
#define SVM_REQ_READ (1<<3)
|
|
#define SVM_REQ_WRITE (1<<2)
|
|
#define SVM_REQ_EXEC (1<<1)
|
|
#define SVM_REQ_PRIV (1<<0)
|
|
|
|
/* Page Request Queue depth */
|
|
#define PRQ_ORDER 2
|
|
#define PRQ_RING_MASK ((0x1000 << PRQ_ORDER) - 0x20)
|
|
#define PRQ_DEPTH ((0x1000 << PRQ_ORDER) >> 5)
|
|
|
|
/*
|
|
* The SVM_FLAG_SUPERVISOR_MODE flag requests a PASID which can be used only
|
|
* for access to kernel addresses. No IOTLB flushes are automatically done
|
|
* for kernel mappings; it is valid only for access to the kernel's static
|
|
* 1:1 mapping of physical memory — not to vmalloc or even module mappings.
|
|
* A future API addition may permit the use of such ranges, by means of an
|
|
* explicit IOTLB flush call (akin to the DMA API's unmap method).
|
|
*
|
|
* It is unlikely that we will ever hook into flush_tlb_kernel_range() to
|
|
* do such IOTLB flushes automatically.
|
|
*/
|
|
#define SVM_FLAG_SUPERVISOR_MODE BIT(0)
|
|
/*
|
|
* The SVM_FLAG_GUEST_MODE flag is used when a PASID bind is for guest
|
|
* processes. Compared to the host bind, the primary differences are:
|
|
* 1. mm life cycle management
|
|
* 2. fault reporting
|
|
*/
|
|
#define SVM_FLAG_GUEST_MODE BIT(1)
|
|
/*
|
|
* The SVM_FLAG_GUEST_PASID flag is used when a guest has its own PASID space,
|
|
* which requires guest and host PASID translation at both directions.
|
|
*/
|
|
#define SVM_FLAG_GUEST_PASID BIT(2)
|
|
|
|
#endif /* __INTEL_SVM_H__ */
|