The VHOST_[GS]ET_FEATURES_ARRAY ioctl already took 0x83 and it would result in a build error when the vhost uapi header is used for perf tool build like below. In file included from trace/beauty/ioctl.c:93: tools/perf/trace/beauty/generated/ioctl/vhost_virtio_ioctl_array.c: In function ‘ioctl__scnprintf_vhost_virtio_cmd’: tools/perf/trace/beauty/generated/ioctl/vhost_virtio_ioctl_array.c:36:18: error: initialized field overwritten [-Werror=override-init] 36 | [0x83] = "SET_FORK_FROM_OWNER", | ^~~~~~~~~~~~~~~~~~~~~ tools/perf/trace/beauty/generated/ioctl/vhost_virtio_ioctl_array.c:36:18: note: (near initialization for ‘vhost_virtio_ioctl_cmds[131]’)
Showing the changes to include/uapi/linux (1 of 1 file). Show all
Unified · Split
| @@ -260,7 +260,7 @@ · 259 unmodified lines | |||
| 260 | * When fork_owner is set to VHOST_FORK_OWNER_KTHREAD: | 260 | * When fork_owner is set to VHOST_FORK_OWNER_KTHREAD: |
| 261 | * - Vhost will create vhost workers as kernel threads. | 261 | * - Vhost will create vhost workers as kernel threads. |
| 262 | */ | 262 | */ |
| 263 | #define VHOST_SET_FORK_FROM_OWNER _IOW(VHOST_VIRTIO, 0x83, __u8) | 263 | #define VHOST_SET_FORK_FROM_OWNER _IOW(VHOST_VIRTIO, 0x84, __u8) |
| 264 | 264 | ||
| 265 | /** | 265 | /** |
| 266 | * VHOST_GET_FORK_OWNER - Get the current fork_owner flag for the vhost device. | 266 | * VHOST_GET_FORK_OWNER - Get the current fork_owner flag for the vhost device. |
| @@ -268,6 +268,6 @@ · 1 unmodified line | |||
| 268 | * | 268 | * |
| 269 | * @return: An 8-bit value indicating the current thread mode. | 269 | * @return: An 8-bit value indicating the current thread mode. |
| 270 | */ | 270 | */ |
| 271 | #define VHOST_GET_FORK_FROM_OWNER _IOR(VHOST_VIRTIO, 0x84, __u8) | 271 | #define VHOST_GET_FORK_FROM_OWNER _IOR(VHOST_VIRTIO, 0x85, __u8) |
| 272 | 272 | ||
| 273 | #endif | 273 | #endif |