/linux/tools/testing/selftests/kvm/x86_64/ |
H A D | vmx_pmu_caps_test.c | 34 u64 capabilities; member 88 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST() 90 vcpu_args_set(vcpu, 1, host_cap.capabilities); in KVM_ONE_VCPU_TEST() 104 host_cap.capabilities); in KVM_ONE_VCPU_TEST() 106 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST() 113 host_cap.capabilities ^ BIT_ULL(i)); in KVM_ONE_VCPU_TEST() 115 host_cap.capabilities ^ BIT_ULL(i)); in KVM_ONE_VCPU_TEST() 126 vcpu_set_msr(vcpu, MSR_IA32_PERF_CAPABILITIES, host_cap.capabilities); in KVM_ONE_VCPU_TEST() 131 const uint64_t fungible_caps = host_cap.capabilities & ~immutable_caps.capabilities; in KVM_ONE_VCPU_TEST() 137 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/Documentation/userspace-api/media/ |
H A 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 …]
|
/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 171 unsigned int capabilities; member 195 unsigned int capabilities; member 266 cedrus_is_capable(struct cedrus_ctx *ctx, unsigned int capabilities) in cedrus_is_capable() argument 268 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/fs/smb/server/ |
H A 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 …]
|
/linux/drivers/crypto/intel/qat/qat_common/ |
H A D | adf_gen2_hw_data.c | 121 u32 capabilities = ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC | in adf_gen2_get_accel_cap() local 127 /* Read accelerator capabilities mask */ in adf_gen2_get_accel_cap() 132 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC; in adf_gen2_get_accel_cap() 133 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in adf_gen2_get_accel_cap() 136 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap() 138 capabilities &= ~ICP_ACCEL_CAPABILITIES_AUTHENTICATION; in adf_gen2_get_accel_cap() 139 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in adf_gen2_get_accel_cap() 142 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in adf_gen2_get_accel_cap() 145 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in adf_gen2_get_accel_cap() 148 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in adf_gen2_get_accel_cap() [all …]
|
/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/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/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/kernel/ |
H A 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 …]
|
/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/drivers/crypto/intel/qat/qat_dh895xcc/ |
H A D | adf_dh895xcc_hw_data.c | 71 u32 capabilities; in get_accel_cap() local 74 capabilities = ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC | in get_accel_cap() 80 /* Read accelerator capabilities mask */ in get_accel_cap() 85 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_SYMMETRIC; in get_accel_cap() 86 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in get_accel_cap() 89 capabilities &= ~ICP_ACCEL_CAPABILITIES_CRYPTO_ASYMMETRIC; in get_accel_cap() 91 capabilities &= ~ICP_ACCEL_CAPABILITIES_AUTHENTICATION; in get_accel_cap() 92 capabilities &= ~ICP_ACCEL_CAPABILITIES_CIPHER; in get_accel_cap() 95 capabilities &= ~ICP_ACCEL_CAPABILITIES_COMPRESSION; in get_accel_cap() 97 return capabilities; in get_accel_cap()
|
/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/security/ |
H A D | commoncap.c | 2 /* Common capabilities, needed by capability.o. 32 * !secure(SECURE_NOROOT) mode, then we raise capabilities. 34 * the file capabilities to be applied, and the setuid-root 36 * to get full privilege on a kernel without file capabilities 37 * support. So in that case we do not raise capabilities. 46 " effective capabilities. Therefore not raising all" in warn_setuid_and_fcaps_mixed() 47 " capabilities.\n", fname); in warn_setuid_and_fcaps_mixed() 77 /* Do we have the necessary capabilities? */ in cap_capable() 127 * task's capabilities, then ptrace access is allowed. 164 * capabilities, then ptrace access is allowed. [all …]
|
/linux/drivers/staging/most/i2c/ |
H A D | i2c.c | 36 struct most_channel_capability capabilities[NUM_CHANNELS]; member 81 if (channel_config->direction != dev->capabilities[ch_idx].direction) { in configure_channel() 304 dev->capabilities[i].data_type = MOST_CH_CONTROL; in i2c_probe() 305 dev->capabilities[i].num_buffers_packet = MAX_BUFFERS_CONTROL; in i2c_probe() 306 dev->capabilities[i].buffer_size_packet = MAX_BUF_SIZE_CONTROL; in i2c_probe() 308 dev->capabilities[CH_RX].direction = MOST_CH_RX; in i2c_probe() 309 dev->capabilities[CH_RX].name_suffix = "rx"; in i2c_probe() 310 dev->capabilities[CH_TX].direction = MOST_CH_TX; in i2c_probe() 311 dev->capabilities[CH_TX].name_suffix = "tx"; in i2c_probe() 316 dev->most_iface.channel_vector = dev->capabilities; in i2c_probe()
|
/linux/block/ |
H A D | blk-crypto-profile.c | 12 * capabilities and certain functions (e.g., functions to program and evict 466 * blk_crypto_intersect_capabilities() - restrict supported crypto capabilities 471 * This clears all crypto capabilities in @parent that aren't set in @child. If 472 * @child is NULL, then this clears all parent capabilities. 498 * the crypto capabilities that @reference does. 502 * Return: %true if @target supports all the crypto capabilities of @reference. 529 * blk_crypto_update_capabilities() - Update the capabilities of a crypto 532 * @dst: The crypto profile whose capabilities to update. 533 * @src: The crypto profile whose capabilities this function will update @dst's 534 * capabilities to. [all …]
|
/linux/sound/usb/line6/ |
H A D | podhd.c | 242 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_disconnect() 375 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL) { in podhd_init() 393 if (pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO) { in podhd_init() 400 if (pod->line6.properties->capabilities & LINE6_CAP_PCM) { in podhd_init() 410 if (pod->line6.properties->capabilities & LINE6_CAP_HWMON_CTL) { in podhd_init() 419 if (!(pod->line6.properties->capabilities & LINE6_CAP_CONTROL_INFO)) { in podhd_init() 452 .capabilities = LINE6_CAP_PCM 463 .capabilities = LINE6_CAP_PCM 474 .capabilities = LINE6_CAP_PCM | LINE6_CAP_CONTROL 486 .capabilities [all...] |
/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
|
/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/mm/ |
H A D | nommu.c | 688 unsigned long capabilities, rlen; in validate_mmap_request() local 721 capabilities = file->f_op->mmap_capabilities(file); in validate_mmap_request() 723 /* no explicit capabilities set, so assume some in validate_mmap_request() 728 capabilities = NOMMU_MAP_COPY; in validate_mmap_request() 732 capabilities = in validate_mmap_request() 743 /* eliminate any capabilities that we can't support on this in validate_mmap_request() 746 capabilities &= ~NOMMU_MAP_DIRECT; in validate_mmap_request() 748 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request() 764 if (!(capabilities & NOMMU_MAP_DIRECT)) in validate_mmap_request() 768 capabilities &= ~NOMMU_MAP_COPY; in validate_mmap_request() [all …]
|