| /linux/tools/testing/selftests/kvm/x86/ |
| H A D | vmx_pmu_caps_test.c | 34 u64 capabilities; member
89 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
91 vcpu_args_set(vcpu, 1, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
105 host_cap.capabilities); in KVM_ONE_VCPU_TEST()
107 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
114 host_cap.capabilities ^ BIT_ULL(i)); in KVM_ONE_VCPU_TEST()
116 host_cap.capabilities ^ BIT_ULL(i)); in KVM_ONE_VCPU_TEST()
127 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST()
132 const uint64_t fungible_caps = host_cap.capabilities & ~immutable_caps.capabilities; in KVM_ONE_VCPU_TEST()
138 host_cap.capabilities & ~BIT_ULL(bit)); in KVM_ONE_VCPU_TEST()
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A 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
|
| /linux/drivers/staging/media/sunxi/cedrus/ |
| H A 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 …]
|
| H A D | cedrus.h | 52 unsigned int capabilities; member
176 unsigned int capabilities; member
200 unsigned int capabilities; member
271 cedrus_is_capable(struct cedrus_ctx *ctx, unsigned int capabilities) in cedrus_is_capable() argument
273 return (ctx->dev->capabilities & capabilities) == capabilities; in cedrus_is_capable()
|
| /linux/Documentation/ABI/testing/ |
| H A 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/peak_current
[all …]
|
| /linux/drivers/crypto/intel/qat/qat_common/ |
| H A D | adf_gen2_hw_data.c | 123 u32 capabilities = ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC | in adf_gen2_get_accel_cap() local
129 /* Read accelerator capabilities mask */ in adf_gen2_get_accel_cap()
134 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC; in adf_gen2_get_accel_cap()
135 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in adf_gen2_get_accel_cap()
138 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap()
140 capabilities &= ~ICP_ACCEL_CAPABILITIES_AUTHENTICATION; in adf_gen2_get_accel_cap()
141 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in adf_gen2_get_accel_cap()
144 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in adf_gen2_get_accel_cap()
147 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap()
150 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in adf_gen2_get_accel_cap()
[all …]
|
| /linux/Documentation/admin-guide/LSM/ |
| H A 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
|
| /linux/kernel/ |
| H A D | capability.c | 41 pr_info_once("warning: `%s' uses 32-bit capabilities (legacy support in use)\n", in warn_legacy_capability_use()
46 * Version 2 capabilities worked fine, but the linux/capability.h file
53 * capabilities and may be doing so insecurely.
63 pr_info_once("warning: `%s' uses deprecated v2 capabilities in a way that may be insecure\n", in warn_deprecated_v2()
99 * The only thing that can change the capabilities of the current
101 * at the same time as we are in the process of setting capabilities
129 * sys_capget - get the capabilities of a given process.
133 * and inheritable capabilities that are returned
160 * Annoying legacy format with 64-bit capabilities exposed in SYSCALL_DEFINE2()
170 * we silently drop the upper capabilities here. This in SYSCALL_DEFINE2()
[all …]
|
| /linux/Documentation/arch/x86/ |
| H A 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
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A 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`.
|
| /linux/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| H A D | hv_vhca.c | 133 u32 *capabilities) in mlx5_hv_vhca_capabilities() argument
141 *capabilities |= AGENT_MASK(agent->type); in mlx5_hv_vhca_capabilities()
152 u32 capabilities = 0; in mlx5_hv_vhca_control_agent_invalidate() local
163 mlx5_hv_vhca_capabilities(hv_vhca, &capabilities); in mlx5_hv_vhca_control_agent_invalidate()
165 /* In case no capabilities, send empty block in return */ in mlx5_hv_vhca_control_agent_invalidate()
166 if (!capabilities) { in mlx5_hv_vhca_control_agent_invalidate()
171 if (block->capabilities != capabilities) in mlx5_hv_vhca_control_agent_invalidate()
172 block->capabilities = capabilities; in mlx5_hv_vhca_control_agent_invalidate()
174 if (block->control & ~capabilities) in mlx5_hv_vhca_control_agent_invalidate()
|
| /linux/drivers/crypto/intel/qat/qat_dh895xcc/ |
| H A D | adf_dh895xcc_hw_data.c | 69 u32 capabilities; in get_accel_cap() local
72 capabilities = ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC | in get_accel_cap()
78 /* Read accelerator capabilities mask */ in get_accel_cap()
83 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC; in get_accel_cap()
84 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in get_accel_cap()
87 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in get_accel_cap()
89 capabilities &= ~ICP_ACCEL_CAPABILITIES_AUTHENTICATION; in get_accel_cap()
90 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in get_accel_cap()
93 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in get_accel_cap()
95 return capabilities; in get_accel_cap()
|
| /linux/Documentation/security/ |
| H A 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
|
| /linux/Documentation/infiniband/ |
| H A D | ucaps.rst | 2 Infiniband Userspace Capabilities
5 User CAPabilities (UCAPs) provide fine-grained control over specific
7 more granular capabilities than the existing Linux capabilities,
22 represents the capabilities (e.g., using chown).
27 the corresponding capabilities for the IB device.
|
| /linux/security/ |
| H A D | commoncap.c | 2 /* Common capabilities, needed by capability.o.
35 * !secure(SECURE_NOROOT) mode, then we raise capabilities.
37 * the file capabilities to be applied, and the setuid-root
39 * to get full privilege on a kernel without file capabilities
40 * support. So in that case we do not raise capabilities.
49 " effective capabilities. Therefore not raising all" in warn_setuid_and_fcaps_mixed()
50 " capabilities.\n", fname); in warn_setuid_and_fcaps_mixed()
80 /* Do we have the necessary capabilities? */ in cap_capable_helper()
156 * task's capabilities, then ptrace access is allowed.
193 * capabilities, then ptrace access is allowed.
[all …]
|
| /linux/fs/smb/client/ |
| H A D | smb1session.c | 43 __u32 capabilities = 0; in cifs_ssetup_hdr() local
62 capabilities = CAP_LARGE_FILES | CAP_NT_SMBS | CAP_LEVEL_II_OPLOCKS | in cifs_ssetup_hdr()
68 if (ses->capabilities & CAP_UNICODE) { in cifs_ssetup_hdr()
70 capabilities |= CAP_UNICODE; in cifs_ssetup_hdr()
72 if (ses->capabilities & CAP_STATUS32) { in cifs_ssetup_hdr()
74 capabilities |= CAP_STATUS32; in cifs_ssetup_hdr()
76 if (ses->capabilities & CAP_DFS) { in cifs_ssetup_hdr()
78 capabilities |= CAP_DFS; in cifs_ssetup_hdr()
80 if (ses->capabilities & CAP_UNIX) in cifs_ssetup_hdr()
81 capabilities |= CAP_UNIX; in cifs_ssetup_hdr()
[all …]
|
| /linux/drivers/platform/x86/ |
| H A D | dasharo-acpi.c | 70 struct dasharo_capability capabilities[DASHARO_FEATURE_MAX][MAX_CAPS_PER_FEAT]; member
104 if (feat >= ARRAY_SIZE(data->capabilities)) in dasharo_read_channel()
111 obj[0].integer.value = data->capabilities[feat][channel].group; in dasharo_read_channel()
113 obj[1].integer.value = data->capabilities[feat][channel].index; in dasharo_read_channel()
167 *str = data->capabilities[DASHARO_FEATURE_TEMPERATURE][channel].name; in dasharo_hwmon_read_string()
173 *str = data->capabilities[DASHARO_FEATURE_FAN_TACH][channel].name; in dasharo_hwmon_read_string()
213 // Max 24 capabilities per feature
310 if (cap_count >= ARRAY_SIZE(data->capabilities[feat])) in dasharo_fill_feature_caps()
313 cap = &data->capabilities[feat][cap_count]; in dasharo_fill_feature_caps()
|
| /linux/mm/ |
| H A D | nommu.c | 698 unsigned long capabilities, rlen; in validate_mmap_request() local
731 capabilities = file->f_op->mmap_capabilities(file); in validate_mmap_request()
733 /* no explicit capabilities set, so assume some in validate_mmap_request()
738 capabilities = NOMMU_MAP_COPY; in validate_mmap_request()
742 capabilities = in validate_mmap_request()
753 /* eliminate any capabilities that we can't support on this in validate_mmap_request()
756 capabilities &= ~NOMMU_MAP_DIRECT; in validate_mmap_request()
758 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request()
774 if (!(capabilities & NOMMU_MAP_DIRECT)) in validate_mmap_request()
778 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request()
[all …]
|
| /linux/sound/usb/line6/ |
| H A D | podhd.c | 243 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_disconnect()
376 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL) { in podhd_init()
394 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_init()
401 if (pod->line6.properties->capabilities & LINE6_CAP_PCM) { in podhd_init()
411 if (pod->line6.properties->capabilities & LINE6_CAP_HWMON_CTL) { in podhd_init()
420 if (!(pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO)) { in podhd_init()
454 .capabilities = LINE6_CAP_PCM
465 .capabilities = LINE6_CAP_PCM
476 .capabilities = LINE6_CAP_PCM | LINE6_CAP_CONTROL
488 .capabilities = LINE6_CAP_CONTROL | LINE6_CAP_CONTROL_INFO
[all …]
|
| /linux/drivers/thermal/intel/ |
| H A D | intel_hfi.c | 13 * model, hardware may periodically update these capabilities as a result of
70 union hfi_capabilities capabilities; member
79 * struct hfi_cpu_data - HFI capabilities per CPU
83 * Capabilities of a logical processor in the HFI table. These capabilities are
93 * @perf_updated: Hardware updated performance capabilities
94 * @ee_updated: Hardware updated energy efficiency capabilities
224 /* Process complete chunks of HFI_THERMNL_CAPS_PER_EVENT capabilities. */ in update_capabilities()
234 /* Process the remaining capabilities if any. */ in update_capabilities()
341 * The format of the HFI table depends on the number of capabilities that the
545 * supported capabilities and the size of the HFI table. in hfi_parse_features()
[all …]
|
| /linux/drivers/staging/greybus/ |
| H A D | gb-camera.h | 52 * @capabilities: Retrieve camera capabilities and store them in the buffer
53 * 'buf' capabilities. The buffer maximum size is specified by
55 * capabilities size is returned from the function. If the buffer
56 * size is too small to hold the capabilities an error is
90 ssize_t (*capabilities)(void *priv, char *buf, size_t len); member
|
| /linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-adap-g-caps.rst | 13 CEC_ADAP_G_CAPS - Query device capabilities
58 - ``capabilities``
59 - The capabilities of the CEC adapter, see
60 :ref:`cec-capabilities`.
68 .. _cec-capabilities:
70 .. flat-table:: CEC Capabilities Flags
|