mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-02 07:13:54 -06:00
linux-headers: Update to Linux v6.7-rc5
We'll add a new RISC-V linux-header file, but first let's update all headers. Headers for 'asm-loongarch' were added in this update. Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com> Acked-by: Alistair Francis <alistair.francis@wdc.com> Message-ID: <20231218204321.75757-2-dbarboza@ventanamicro.com> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
This commit is contained in:
parent
871dad3a19
commit
efb91426af
29 changed files with 498 additions and 27 deletions
|
@ -277,8 +277,8 @@ struct vfio_region_info {
|
|||
#define VFIO_REGION_INFO_FLAG_CAPS (1 << 3) /* Info supports caps */
|
||||
__u32 index; /* Region index */
|
||||
__u32 cap_offset; /* Offset within info struct of first cap */
|
||||
__u64 size; /* Region size (bytes) */
|
||||
__u64 offset; /* Region offset from start of device fd */
|
||||
__aligned_u64 size; /* Region size (bytes) */
|
||||
__aligned_u64 offset; /* Region offset from start of device fd */
|
||||
};
|
||||
#define VFIO_DEVICE_GET_REGION_INFO _IO(VFIO_TYPE, VFIO_BASE + 8)
|
||||
|
||||
|
@ -294,8 +294,8 @@ struct vfio_region_info {
|
|||
#define VFIO_REGION_INFO_CAP_SPARSE_MMAP 1
|
||||
|
||||
struct vfio_region_sparse_mmap_area {
|
||||
__u64 offset; /* Offset of mmap'able area within region */
|
||||
__u64 size; /* Size of mmap'able area */
|
||||
__aligned_u64 offset; /* Offset of mmap'able area within region */
|
||||
__aligned_u64 size; /* Size of mmap'able area */
|
||||
};
|
||||
|
||||
struct vfio_region_info_cap_sparse_mmap {
|
||||
|
@ -450,9 +450,9 @@ struct vfio_device_migration_info {
|
|||
VFIO_DEVICE_STATE_V1_RESUMING)
|
||||
|
||||
__u32 reserved;
|
||||
__u64 pending_bytes;
|
||||
__u64 data_offset;
|
||||
__u64 data_size;
|
||||
__aligned_u64 pending_bytes;
|
||||
__aligned_u64 data_offset;
|
||||
__aligned_u64 data_size;
|
||||
};
|
||||
|
||||
/*
|
||||
|
@ -476,7 +476,7 @@ struct vfio_device_migration_info {
|
|||
|
||||
struct vfio_region_info_cap_nvlink2_ssatgt {
|
||||
struct vfio_info_cap_header header;
|
||||
__u64 tgt;
|
||||
__aligned_u64 tgt;
|
||||
};
|
||||
|
||||
/*
|
||||
|
@ -816,7 +816,7 @@ struct vfio_device_gfx_plane_info {
|
|||
__u32 drm_plane_type; /* type of plane: DRM_PLANE_TYPE_* */
|
||||
/* out */
|
||||
__u32 drm_format; /* drm format of plane */
|
||||
__u64 drm_format_mod; /* tiled mode */
|
||||
__aligned_u64 drm_format_mod; /* tiled mode */
|
||||
__u32 width; /* width of plane */
|
||||
__u32 height; /* height of plane */
|
||||
__u32 stride; /* stride of plane */
|
||||
|
@ -829,6 +829,7 @@ struct vfio_device_gfx_plane_info {
|
|||
__u32 region_index; /* region index */
|
||||
__u32 dmabuf_id; /* dma-buf id */
|
||||
};
|
||||
__u32 reserved;
|
||||
};
|
||||
|
||||
#define VFIO_DEVICE_QUERY_GFX_PLANE _IO(VFIO_TYPE, VFIO_BASE + 14)
|
||||
|
@ -863,9 +864,10 @@ struct vfio_device_ioeventfd {
|
|||
#define VFIO_DEVICE_IOEVENTFD_32 (1 << 2) /* 4-byte write */
|
||||
#define VFIO_DEVICE_IOEVENTFD_64 (1 << 3) /* 8-byte write */
|
||||
#define VFIO_DEVICE_IOEVENTFD_SIZE_MASK (0xf)
|
||||
__u64 offset; /* device fd offset of write */
|
||||
__u64 data; /* data to be written */
|
||||
__aligned_u64 offset; /* device fd offset of write */
|
||||
__aligned_u64 data; /* data to be written */
|
||||
__s32 fd; /* -1 for de-assignment */
|
||||
__u32 reserved;
|
||||
};
|
||||
|
||||
#define VFIO_DEVICE_IOEVENTFD _IO(VFIO_TYPE, VFIO_BASE + 16)
|
||||
|
@ -1434,6 +1436,27 @@ struct vfio_device_feature_mig_data_size {
|
|||
|
||||
#define VFIO_DEVICE_FEATURE_MIG_DATA_SIZE 9
|
||||
|
||||
/**
|
||||
* Upon VFIO_DEVICE_FEATURE_SET, set or clear the BUS mastering for the device
|
||||
* based on the operation specified in op flag.
|
||||
*
|
||||
* The functionality is incorporated for devices that needs bus master control,
|
||||
* but the in-band device interface lacks the support. Consequently, it is not
|
||||
* applicable to PCI devices, as bus master control for PCI devices is managed
|
||||
* in-band through the configuration space. At present, this feature is supported
|
||||
* only for CDX devices.
|
||||
* When the device's BUS MASTER setting is configured as CLEAR, it will result in
|
||||
* blocking all incoming DMA requests from the device. On the other hand, configuring
|
||||
* the device's BUS MASTER setting as SET (enable) will grant the device the
|
||||
* capability to perform DMA to the host memory.
|
||||
*/
|
||||
struct vfio_device_feature_bus_master {
|
||||
__u32 op;
|
||||
#define VFIO_DEVICE_FEATURE_CLEAR_MASTER 0 /* Clear Bus Master */
|
||||
#define VFIO_DEVICE_FEATURE_SET_MASTER 1 /* Set Bus Master */
|
||||
};
|
||||
#define VFIO_DEVICE_FEATURE_BUS_MASTER 10
|
||||
|
||||
/* -------- API for Type1 VFIO IOMMU -------- */
|
||||
|
||||
/**
|
||||
|
@ -1449,7 +1472,7 @@ struct vfio_iommu_type1_info {
|
|||
__u32 flags;
|
||||
#define VFIO_IOMMU_INFO_PGSIZES (1 << 0) /* supported page sizes info */
|
||||
#define VFIO_IOMMU_INFO_CAPS (1 << 1) /* Info supports caps */
|
||||
__u64 iova_pgsizes; /* Bitmap of supported page sizes */
|
||||
__aligned_u64 iova_pgsizes; /* Bitmap of supported page sizes */
|
||||
__u32 cap_offset; /* Offset within info struct of first cap */
|
||||
__u32 pad;
|
||||
};
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue