| /kernel/linux/linux-6.6/tools/testing/selftests/kvm/x86_64/ |
| D | vmx_pmu_caps_test.c | 34 u64 capabilities; member
91 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in test_guest_wrmsr_perf_capabilities()
93 vcpu_args_set(vcpu, 1, host_cap.capabilities); in test_guest_wrmsr_perf_capabilities()
107 host_cap.capabilities); in test_guest_wrmsr_perf_capabilities()
109 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in test_guest_wrmsr_perf_capabilities()
116 host_cap.capabilities ^ BIT_ULL(i)); in test_guest_wrmsr_perf_capabilities()
118 host_cap.capabilities ^ BIT_ULL(i)); in test_guest_wrmsr_perf_capabilities()
134 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in test_basic_perf_capabilities()
141 const uint64_t fungible_caps = host_cap.capabilities & ~immutable_caps.capabilities; in test_fungible_perf_capabilities()
150 host_cap.capabilities & ~BIT_ULL(bit)); in test_fungible_perf_capabilities()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 150 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
151 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
152 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
153 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
154 replace define V4L2_CAP_VIDEO_M2M device-capabilities
155 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
156 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
157 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
158 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
159 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-g-client-cap.rst | 14 capabilities.
40 subdevice ioctls) capabilities. The client capabilities are stored in the file
42 capabilities for each opened subdev separately.
44 By default no client capabilities are set when a subdev device node is opened.
46 The purpose of the client capabilities are to inform the kernel of the behavior
50 The ``VIDIOC_SUBDEV_G_CLIENT_CAP`` ioctl returns the current client capabilities
53 The ``VIDIOC_SUBDEV_S_CLIENT_CAP`` ioctl sets client capabilities for the file
54 handle ``fd``. The new capabilities fully replace the current capabilities, the
55 ioctl can therefore also be used to remove capabilities that have previously
59 :c:type:`v4l2_subdev_client_capability` to reflect the capabilities that have
[all …]
|
| D | vidioc-querycap.rst | 13 VIDIOC_QUERYCAP - Query device capabilities
36 information about driver and hardware capabilities. The ioctl takes a
107 - ``capabilities``
108 - Available capabilities of the physical device as a whole, see
109 :ref:`device-capabilities`. The same physical device can export
111 /dev/radioZ). The ``capabilities`` field should contain a union of
112 all capabilities available around the several V4L2 devices
113 exported to userspace. For all those devices the ``capabilities``
114 field returns the same set of capabilities. This allows
120 - Device capabilities of the opened device, see
[all …]
|
| D | vidioc-dv-timings-cap.rst | 13 VIDIOC_DV_TIMINGS_CAP - VIDIOC_SUBDEV_DV_TIMINGS_CAP - The capabilities of the Digital Video receiv…
38 To query the capabilities of the DV receiver/transmitter applications
49 When implemented by the driver DV capabilities of subdevices can be
51 on a subdevice node. The capabilities are specific to inputs (for DV
55 zero the ``reserved`` array. Attempts to query capabilities on a pad
90 - ``capabilities``
91 - Several flags giving more information about the capabilities. See
92 :ref:`dv-bt-cap-capabilities` for a description of the flags.
125 - BT.656/1120 timings capabilities of the hardware.
133 .. _dv-bt-cap-capabilities:
[all …]
|
| D | vidioc-subdev-querycap.rst | 13 VIDIOC_SUBDEV_QUERYCAP - Query sub-device capabilities
36 information about driver and hardware capabilities. The ioctl takes a pointer to
71 - ``capabilities``
72 - Sub-device capabilities of the opened device, see
73 :ref:`subdevice-capabilities`.
80 .. _subdevice-capabilities:
84 .. flat-table:: Sub-Device Capabilities Flags
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 170 replace define V4L2_CAP_VIDEO_CAPTURE device-capabilities
171 replace define V4L2_CAP_VIDEO_CAPTURE_MPLANE device-capabilities
172 replace define V4L2_CAP_VIDEO_OUTPUT device-capabilities
173 replace define V4L2_CAP_VIDEO_OUTPUT_MPLANE device-capabilities
174 replace define V4L2_CAP_VIDEO_M2M device-capabilities
175 replace define V4L2_CAP_VIDEO_M2M_MPLANE device-capabilities
176 replace define V4L2_CAP_VIDEO_OVERLAY device-capabilities
177 replace define V4L2_CAP_VBI_CAPTURE device-capabilities
178 replace define V4L2_CAP_VBI_OUTPUT device-capabilities
179 replace define V4L2_CAP_SLICED_VBI_CAPTURE device-capabilities
[all …]
|
| /kernel/linux/linux-6.6/drivers/staging/media/sunxi/cedrus/ |
| D | cedrus.c | 94 .capabilities = CEDRUS_CAPABILITY_MPEG2_DEC,
100 .capabilities = CEDRUS_CAPABILITY_MPEG2_DEC,
106 .capabilities = CEDRUS_CAPABILITY_MPEG2_DEC,
112 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
118 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
125 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
131 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
137 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
143 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
151 .capabilities = CEDRUS_CAPABILITY_H264_DEC,
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-querycap.rst | 13 VIDIOC_QUERYCAP - Query device capabilities
36 information about driver and hardware capabilities. The ioctl takes a
105 - ``capabilities``
106 - Available capabilities of the physical device as a whole, see
107 :ref:`device-capabilities`. The same physical device can export
109 /dev/radioZ). The ``capabilities`` field should contain a union of
110 all capabilities available around the several V4L2 devices
111 exported to userspace. For all those devices the ``capabilities``
112 field returns the same set of capabilities. This allows
118 - Device capabilities of the opened device, see
[all …]
|
| D | vidioc-dv-timings-cap.rst | 13 VIDIOC_DV_TIMINGS_CAP - VIDIOC_SUBDEV_DV_TIMINGS_CAP - The capabilities of the Digital Video receiv…
38 To query the capabilities of the DV receiver/transmitter applications
49 When implemented by the driver DV capabilities of subdevices can be
51 on a subdevice node. The capabilities are specific to inputs (for DV
55 zero the ``reserved`` array. Attempts to query capabilities on a pad
90 - ``capabilities``
91 - Several flags giving more information about the capabilities. See
92 :ref:`dv-bt-cap-capabilities` for a description of the flags.
125 - BT.656/1120 timings capabilities of the hardware.
133 .. _dv-bt-cap-capabilities:
[all …]
|
| D | vidioc-subdev-querycap.rst | 13 VIDIOC_SUBDEV_QUERYCAP - Query sub-device capabilities
36 information about driver and hardware capabilities. The ioctl takes a pointer to
71 - ``capabilities``
72 - Sub-device capabilities of the opened device, see
73 :ref:`subdevice-capabilities`.
80 .. _subdevice-capabilities:
84 .. flat-table:: Sub-Device Capabilities Flags
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-class-usb_power_delivery | 23 What: /sys/class/usb_power_delivery/.../source-capabilities
27 The source capabilities message "Source_Capabilities" contains a
37 What: /sys/class/usb_power_delivery/.../sink-capabilities
42 of Power Data Objects (PDO) just like with source capabilities,
43 but instead of describing the power capabilities, these objects
47 same as with the source capabilities message.
63 related to the USB capabilities rather than power capabilities.
72 What: /sys/class/usb_power_delivery/.../source-capabilities/1:fixed_supply/usb_suspend_supported
81 What: /sys/class/usb_power_delivery/.../sink-capabilities/1:fixed_supply/higher_capability
127 What: /sys/class/usb_power_delivery/.../source-capabilities/<position>:fixed_supply/maximum_current
[all …]
|
| /kernel/linux/linux-6.6/fs/smb/server/ |
| D | smb2ops.c | 18 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
44 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
71 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
98 .capabilities = SMB2_GLOBAL_CAP_LARGE_MTU,
207 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING; in init_smb2_1_server()
224 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING | in init_smb3_0_server()
229 conn->vals->capabilities |= SMB2_GLOBAL_CAP_ENCRYPTION; in init_smb3_0_server()
234 conn->vals->capabilities |= SMB2_GLOBAL_CAP_ENCRYPTION; in init_smb3_0_server()
237 conn->vals->capabilities |= SMB2_GLOBAL_CAP_MULTI_CHANNEL; in init_smb3_0_server()
254 conn->vals->capabilities |= SMB2_GLOBAL_CAP_LEASING | in init_smb3_02_server()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/dvb/ |
| D | fe-get-info.rst | 13 FE_GET_INFO - Query Digital TV frontend capabilities and returns information
37 obtain information about driver and hardware capabilities. The ioctl
42 frontend capabilities
45 Capabilities describe what a frontend can do. Some capabilities are
48 The frontend capabilities are described at :c:type:`fe_caps`.
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/dvb/ |
| D | fe-get-info.rst | 13 FE_GET_INFO - Query Digital TV frontend capabilities and returns information
37 obtain information about driver and hardware capabilities. The ioctl
42 frontend capabilities
45 Capabilities describe what a frontend can do. Some capabilities are
48 The frontend capabilities are described at :c:type:`fe_caps`.
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | intel-hfi.rst | 25 separate capabilities. Even though on some systems these two metrics may be
26 related, they are specified as independent capabilities in the Intel SDM.
28 These capabilities may change at runtime as a result of changes in the
30 at which these capabilities are updated is specific to each processor model. On
31 some models, capabilities are set at boot time and never change. On others,
32 capabilities may change every tens of milliseconds. For instance, a remote
37 The kernel or a userspace policy daemon can use these capabilities to modify
39 capabilities of a given logical processor becomes zero, it is an indication that
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 13 In absence of file capabilities, processes spawned on a Linux system that need
17 often preferable to use Linux runtime capabilities rather than file
18 capabilities, since using file capabilities to run a program with elevated
23 CAP_SET{U/G}ID capabilities, this is often at odds with the goals of running a
32 capabilities in such a way.
35 other untrusted uids without full blown CAP_SETUID capabilities. The non-root
53 For candidate applications that would like to have restricted setid capabilities
55 setid capabilities from the application completely and refactor the process
69 namespace and give programs in the tree setid capabilities. In this way,
75 Linux checks for capabilities based off of the user namespace that "owns" some
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 13 In absence of file capabilities, processes spawned on a Linux system that need
17 often preferable to use Linux runtime capabilities rather than file
18 capabilities, since using file capabilities to run a program with elevated
23 CAP_SET{U/G}ID capabilities, this is often at odds with the goals of running a
32 capabilities in such a way.
35 other untrusted uids without full blown CAP_SETUID capabilities. The non-root
53 For candidate applications that would like to have restricted setid capabilities
55 setid capabilities from the application completely and refactor the process
69 namespace and give programs in the tree setid capabilities. In this way,
75 Linux checks for capabilities based off of the user namespace that "owns" some
|
| /kernel/linux/linux-6.6/drivers/crypto/intel/qat/qat_common/ |
| D | adf_gen2_hw_data.c | 218 u32 capabilities = ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC | in adf_gen2_get_accel_cap() local
224 /* Read accelerator capabilities mask */ in adf_gen2_get_accel_cap()
229 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC; in adf_gen2_get_accel_cap()
230 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in adf_gen2_get_accel_cap()
233 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap()
235 capabilities &= ~ICP_ACCEL_CAPABILITIES_AUTHENTICATION; in adf_gen2_get_accel_cap()
236 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in adf_gen2_get_accel_cap()
239 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in adf_gen2_get_accel_cap()
242 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap()
245 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in adf_gen2_get_accel_cap()
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_drv.c | 297 static void vmw_print_capabilities(uint32_t capabilities) in vmw_print_capabilities() argument
299 DRM_INFO("Capabilities:\n"); in vmw_print_capabilities()
300 if (capabilities & SVGA_CAP_RECT_COPY) in vmw_print_capabilities()
302 if (capabilities & SVGA_CAP_CURSOR) in vmw_print_capabilities()
304 if (capabilities & SVGA_CAP_CURSOR_BYPASS) in vmw_print_capabilities()
306 if (capabilities & SVGA_CAP_CURSOR_BYPASS_2) in vmw_print_capabilities()
308 if (capabilities & SVGA_CAP_8BIT_EMULATION) in vmw_print_capabilities()
310 if (capabilities & SVGA_CAP_ALPHA_CURSOR) in vmw_print_capabilities()
312 if (capabilities & SVGA_CAP_3D) in vmw_print_capabilities()
314 if (capabilities & SVGA_CAP_EXTENDED_FIFO) in vmw_print_capabilities()
[all …]
|
| /kernel/liteos_a/security/cap/ |
| D | capability_type.h | 35 // posix capabilities
45 // socket capabilities
51 // fs capabilities
55 // process capabilities
58 // time capabilities
62 // process capabilities
|
| /kernel/linux/linux-6.6/kernel/ |
| D | capability.c | 43 pr_info_once("warning: `%s' uses 32-bit capabilities (legacy support in use)\n", in warn_legacy_capability_use()
48 * Version 2 capabilities worked fine, but the linux/capability.h file
55 * capabilities and may be doing so insecurely.
67 pr_info_once("warning: `%s' uses deprecated v2 capabilities in a way that may be insecure\n", in warn_deprecated_v2()
103 * The only thing that can change the capabilities of the current
105 * at the same time as we are in the process of setting capabilities
133 * sys_capget - get the capabilities of a given process.
137 * and inheritable capabilities that are returned
164 * Annoying legacy format with 64-bit capabilities exposed in SYSCALL_DEFINE2()
174 * we silently drop the upper capabilities here. This in SYSCALL_DEFINE2()
[all …]
|
| /kernel/linux/linux-5.10/kernel/ |
| D | capability.c | 24 * Leveraged for setting/resetting capabilities
50 pr_info_once("warning: `%s' uses 32-bit capabilities (legacy support in use)\n", in warn_legacy_capability_use()
55 * Version 2 capabilities worked fine, but the linux/capability.h file
62 * capabilities and may be doing so insecurely.
74 pr_info_once("warning: `%s' uses deprecated v2 capabilities in a way that may be insecure\n", in warn_deprecated_v2()
110 * The only thing that can change the capabilities of the current
112 * at the same time as we are in the process of setting capabilities
140 * sys_capget - get the capabilities of a given process.
144 * and inheritable capabilities that are returned
178 * we silently drop the upper capabilities here. This in SYSCALL_DEFINE2()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/security/ |
| D | lsm.rst | 35 migrating the Linux capabilities code into such a module.
43 report provides an overview of the framework and the capabilities
55 optional, requiring `CONFIG_SECURITY` to be enabled. The capabilities
57 This capabilities module is discussed further in
58 `LSM Capabilities Module`_.
122 LSM Capabilities Module
125 The POSIX.1e capabilities logic is maintained as a security module
126 stored in the file ``security/commoncap.c``. The capabilities
129 The capabilities security module does not use the general security
|
| /kernel/linux/linux-6.6/Documentation/security/ |
| D | lsm.rst | 35 migrating the Linux capabilities code into such a module.
43 report provides an overview of the framework and the capabilities
55 optional, requiring `CONFIG_SECURITY` to be enabled. The capabilities
57 This capabilities module is discussed further in
58 `LSM Capabilities Module`_.
122 LSM Capabilities Module
125 The POSIX.1e capabilities logic is maintained as a security module
126 stored in the file ``security/commoncap.c``. The capabilities
129 The capabilities security module does not use the general security
|