064a57d7dd
This patch is an initial step to replace Intel SVM code with the following IOMMU SVA ops: intel_svm_bind_mm() => iommu_sva_bind_device() intel_svm_unbind_mm() => iommu_sva_unbind_device() intel_svm_is_pasid_valid() => iommu_sva_get_pasid() The features below will continue to work but are not included in this patch in that they are handled mostly within the IOMMU subsystem. - IO page fault - mmu notifier Consolidation of the above will come after merging generic IOMMU sva code[1]. There should not be any changes needed for SVA users such as accelerator device drivers during this time. [1] http://jpbrucker.net/sva/ 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/20200516062101.29541-12-baolu.lu@linux.intel.com Signed-off-by: Joerg Roedel <jroedel@suse.de>
60 lines
2 KiB
C
60 lines
2 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__
|
|
|
|
struct device;
|
|
|
|
struct svm_dev_ops {
|
|
void (*fault_cb)(struct device *dev, int pasid, u64 address,
|
|
void *private, int rwxp, int response);
|
|
};
|
|
|
|
/* 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)
|
|
|
|
/*
|
|
* The SVM_FLAG_PRIVATE_PASID flag requests a PASID which is *not* the "main"
|
|
* PASID for the current process. Even if a PASID already exists, a new one
|
|
* will be allocated. And the PASID allocated with SVM_FLAG_PRIVATE_PASID
|
|
* will not be given to subsequent callers. This facility allows a driver to
|
|
* disambiguate between multiple device contexts which access the same MM,
|
|
* if there is no other way to do so. It should be used sparingly, if at all.
|
|
*/
|
|
#define SVM_FLAG_PRIVATE_PASID (1<<0)
|
|
|
|
/*
|
|
* 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 (1<<1)
|
|
/*
|
|
* 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 (1<<2)
|
|
/*
|
|
* 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 (1<<3)
|
|
|
|
#endif /* __INTEL_SVM_H__ */
|