Home
last modified time | relevance | path

Searched full:capabilities (Results 1 – 25 of 2942) sorted by relevance

12345678910>>...118

/openbmc/linux/tools/testing/selftests/kvm/x86_64/
H A Dvmx_pmu_caps_test.c34 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 …]
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Dvidioc-subdev-g-client-cap.rst14 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 Dvidioc-querycap.rst13 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 Dvidioc-dv-timings-cap.rst13 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 Dvidioc-subdev-querycap.rst13 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
/openbmc/linux/Documentation/userspace-api/media/
H A Dvideodev2.h.rst.exceptions170 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 …]
/openbmc/linux/drivers/staging/media/sunxi/cedrus/
H A Dcedrus.c94 .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 …]
/openbmc/qemu/tests/functional/
H A Dtest_x86_cpu_model_versions.py244 Validation of Cascadelake arch-capabilities
258 self.assertFalse(self.get_cpu_prop('arch-capabilities'),
259 'pc-i440fx-4.1 + Cascadelake-Server should not have arch-capabilities')
268 self.assertFalse(self.get_cpu_prop('arch-capabilities'),
269 'pc-i440fx-4.0 + Cascadelake-Server should not have arch-capabilities')
277 'enforce=off,+arch-capabilities')
279 self.assertTrue(self.get_cpu_prop('arch-capabilities'),
280 … 'pc-i440fx-4.0 + Cascadelake-Server,+arch-capabilities should have arch-capabilities')
287 'enforce=off,-arch-capabilities')
289 self.assertFalse(self.get_cpu_prop('arch-capabilities'),
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-class-usb_power_delivery23 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 …]
/openbmc/openbmc-test-automation/ipmi/dcmi/
H A Dtest_dcmi_get_capabilities.robot3 Documentation Module to test dcmi get capabilities functionality.
15 Verify Get DCMI Capabilities
16 [Documentation] Verify get DCMI capabilities command output.
21 # Supported DCMI capabilities:
22 ... Mandatory platform capabilities
23 ... Optional platform capabilities
25 ... Managebility access capabilities
40 ... msg=Supported DCMI capabilities not present.
/openbmc/linux/fs/smb/server/
H A Dsmb2ops.c18 .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 …]
/openbmc/openbmc/meta-quanta/meta-s6q/recipes-phosphor/dbus/chassis-intrusion-monitor/
H A Dconfig.yaml1 - name: chassis capabilities path
20 paths: chassis capabilities path
27 paths: chassis capabilities path
34 paths: chassis capabilities path
45 paths: chassis capabilities path
70 paths: chassis capabilities path
78 paths: chassis capabilities path
/openbmc/openbmc-test-automation/ipmi/
H A Dtest_ipmi_chassis.robot123 Verify Get Chassis Capabilities
124 [Documentation] Verify get chassis capabilities IPMI cmd with valid data length and verify
130 ... ${IPMI_RAW_CMD['Chassis Capabilities']['Get'][0]}
138 Verify Chassis Capabilities Response ${ipmi_resp[0]} ${busctl_resp[0]} CapabilitiesFlags
139 Verify Chassis Capabilities Response ${ipmi_resp[1]} ${busctl_resp[0]} FRUDeviceAddress
140 Verify Chassis Capabilities Response ${ipmi_resp[2]} ${busctl_resp[0]} SDRDeviceAddress
141 Verify Chassis Capabilities Response ${ipmi_resp[3]} ${busctl_resp[0]} SELDeviceAddress
142 Verify Chassis Capabilities Response ${ipmi_resp[4]} ${busctl_resp[0]} SMDeviceAddress
143 Verify Chassis Capabilities Response ${ipmi_resp[5]} ${busctl_resp[0]} BridgeDeviceAddress
146 Verify Get Chassis Capabilities With Invalid Data Length
[all …]
/openbmc/qemu/tests/migration/guestperf/
H A Dengine.py133 resp = src.cmd("migrate-set-capabilities",
134 capabilities = [
142 resp = src.cmd("migrate-set-capabilities",
143 capabilities = [
147 resp = dst.cmd("migrate-set-capabilities",
148 capabilities = [
160 resp = src.cmd("migrate-set-capabilities",
161 capabilities = [
167 resp = dst.cmd("migrate-set-capabilities",
168 capabilities = [
[all …]
/openbmc/linux/Documentation/userspace-api/media/dvb/
H A Dfe-get-info.rst13 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`.
/openbmc/linux/Documentation/arch/x86/
H A Dintel-hfi.rst25 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
/openbmc/linux/Documentation/admin-guide/LSM/
H A DSafeSetID.rst13 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
/openbmc/linux/drivers/crypto/intel/qat/qat_common/
H A Dadf_gen2_hw_data.c218 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 …]
/openbmc/qemu/docs/interop/
H A Dqmp-spec.rst66 ready for capabilities negotiation (for more information refer to section
67 `Capabilities Negotiation`_).
73 { "QMP": { "version": json-object, "capabilities": json-array } }
79 - The ``capabilities`` member specifies the availability of features beyond the
83 Capabilities section in Protocol Specification
86 Currently supported capabilities are:
129 With out-of-band execution enabled via `capabilities negotiation`_,
274 "package": "v3.0.0"}, "capabilities": ["oob"] } }
278 Capabilities negotiation
333 Capabilities Negotiation
[all …]
/openbmc/linux/kernel/
H A Dcapability.c43 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 …]
/openbmc/linux/Documentation/security/
H A Dlsm.rst35 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
/openbmc/linux/drivers/crypto/intel/qat/qat_dh895xcc/
H A Dadf_dh895xcc_hw_data.c69 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()
/openbmc/linux/drivers/net/ethernet/mellanox/mlx5/core/lib/
H A Dhv_vhca.c133 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()
/openbmc/qemu/migration/
H A Doptions.c2 * QEMU migration capabilities
83 DEFINE_PROP_BOOL(name, MigrationState, capabilities[x], false)
176 /* Migration capabilities */
206 return s->capabilities[MIGRATION_CAPABILITY_AUTO_CONVERGE]; in migrate_auto_converge()
213 return s->capabilities[MIGRATION_CAPABILITY_BACKGROUND_SNAPSHOT]; in migrate_background_snapshot()
220 return s->capabilities[MIGRATION_CAPABILITY_X_COLO]; in migrate_colo()
227 return s->capabilities[MIGRATION_CAPABILITY_DIRTY_BITMAPS]; in migrate_dirty_bitmaps()
234 return s->capabilities[MIGRATION_CAPABILITY_DIRTY_LIMIT]; in migrate_dirty_limit()
241 return s->capabilities[MIGRATION_CAPABILITY_EVENTS]; in migrate_events()
248 return s->capabilities[MIGRATION_CAPABILITY_MAPPED_RAM]; in migrate_mapped_ram()
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D19467 capabilities = [{'capability': 'events', 'state': True}, variable
69 source_vm.qmp('migrate-set-capabilities', capabilities=capabilities)
70 dest_vm.qmp('migrate-set-capabilities', capabilities=capabilities)

12345678910>>...118