mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-23 04:34:11 +08:00
c7b6bac9c7
PASID is defined as a few different types in iommu including "int", "u32", and "unsigned int". To be consistent and to match with uapi definitions, define PASID and its variations (e.g. max PASID) as "u32". "u32" is also shorter and a little more explicit than "unsigned int". No PASID type change in uapi although it defines PASID as __u64 in some places. Suggested-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Tony Luck <tony.luck@intel.com> Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com> Acked-by: Felix Kuehling <Felix.Kuehling@amd.com> Acked-by: Joerg Roedel <jroedel@suse.de> Link: https://lkml.kernel.org/r/1600187413-163670-2-git-send-email-fenghua.yu@intel.com
60 lines
2.0 KiB
C
60 lines
2.0 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, u32 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__ */
|