Searched full:feature (Results 1 – 25 of 544) sorted by relevance
12345678910>>...22
| /Documentation/x86/ |
| D | cpuinfo.rst | 4 x86 Feature Flags
11 in arch/x86/include/asm/cpufeatures.h. If the kernel cares about a feature
12 or KVM want to expose the feature to a KVM guest, it can and should have
16 If users want to know if a feature is available on a given system, they
19 If such flag represents a hardware feature, it also means that the
25 can explain missing flags: the expected feature failed to enable, the feature
26 is missing in hardware, platform firmware did not enable it, the feature is
28 not support the feature and thus has not enabled it. In general, /proc/cpuinfo
32 How are feature flags created?
35 a: Feature flags can be derived from the contents of CPUID leaves.
[all …]
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,powerpc-cpu-features.txt | 24 Description: Container of CPU feature nodes.
51 compatibility, less the individual feature nodes. For example, an ISA v3.0
66 /cpus/ibm,powerpc-cpu-features/example-feature node bindings
69 Each child node of cpu-features represents a CPU feature / capability.
71 Node: A string describing an architected CPU feature, e.g., "floating-point".
73 Description: A feature or capability supported by the CPUs.
79 Presence of the node indicates the feature is available.
88 First level of the Power ISA that the feature appears in.
105 that can use the feature.
119 feature to lesser privilege levels. If the property does not exist then no
[all …]
|
| /Documentation/hid/ |
| D | hid-sensor.rst | 70 functions, which get and set each input/feature/output report.
121 Set Feature report::
126 This interface is used to set a value for a field in feature report. For example
177 │ │ ├── feature-0-200316
178 │ │ │ ├── feature-0-200316-maximum
179 │ │ │ ├── feature-0-200316-minimum
180 │ │ │ ├── feature-0-200316-name
181 │ │ │ ├── feature-0-200316-size
182 │ │ │ ├── feature-0-200316-unit-expo
183 │ │ │ ├── feature-0-200316-units
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-mmc | 5 Enhanced area is a new feature defined in eMMC4.4 standard.
6 eMMC4.4 or later card can support such feature. This kind of
7 area can help to improve the card performance. If the feature
16 Enhanced area is a new feature defined in eMMC4.4 standard.
17 eMMC4.4 or later card can support such feature. This kind of
18 area can help to improve the card performance. If the feature
|
| D | sysfs-block-device | 34 - If the device does not support the unload heads feature,
41 ATA standard, but support the unload feature nonetheless.
44 does support the unload feature, then you can tell the kernel
59 command queueing) support. By default this feature is turned
|
| D | sysfs-class-watchdog | 21 if the device has the nowayout feature set, otherwise
23 nowayout feature. Once set, the nowayout feature
25 effect (if the feature was already disabled) or
64 is an optional feature.
|
| /Documentation/features/ |
| D | arch-support.txt | 3 arch-support.txt file in each feature directory shows the arch
8 | ok | # feature supported by the architecture
9 |TODO| # feature not yet supported by the architecture
10 | .. | # feature cannot be supported by the hardware
|
| D | list-arch.sh | 2 # Small script that visualizes the kernel feature support status
12 echo "# Kernel feature support matrix of the '$ARCH' architecture:"
17 N=$(grep -h "^# Feature name:" $F | cut -c25-)
|
| /Documentation/driver-api/mei/ |
| D | mei.rst | 9 The actual feature set depends on the Intel chipset SKU.
17 Each Intel ME feature, or Intel ME Client is addressed by a unique GUID and
27 An application maintains communication with an Intel ME feature while
28 /dev/meiX is open. The binding to a specific feature is performed by calling
30 The number of instances of an Intel ME feature that can be opened
31 at the same time depends on the Intel ME feature, but most of the
34 The driver is transparent to data that are passed between firmware feature
47 virtual channels with an Intel ME feature. Not all features support
84 Connect to firmware Feature/Client.
99 in_client_uuid - GUID of the FW Feature that needs
[all …]
|
| /Documentation/driver-api/mmc/ |
| D | mmc-tools.rst | 25 - Enable the eMMC BKOPS feature.
26 - Permanently enable the eMMC H/W Reset feature.
27 - Permanently disable the eMMC H/W Reset feature.
33 - Enable the eMMC cache feature.
34 - Disable the eMMC cache feature.
|
| D | mmc-dev-parts.rst | 35 This is a feature of the card and not of the kernel. If the card does
37 feature has been disabled on the card, the file will be read-only.
39 The boot partitions can also be locked permanently, but this feature is
|
| /Documentation/fpga/ |
| D | dfl.rst | 2 FPGA Device Feature List (DFL) Framework Overview
11 The Device Feature List (DFL) FPGA framework (and drivers according to
19 Device Feature List (DFL) Overview
21 Device Feature List (DFL) defines a linked list of feature headers within the
31 +----------+ | | Feature | | | Feature | | | Feature |
37 +----------+ | | Feature | | Feature | | Feature |
65 Feature Header (Next_DFH) pointer.
67 Each FIU, AFU and Private Feature could implement its own functional registers.
69 e.g. FME Header Register Set, and the one for Private Feature, is named as
70 Feature Register Set, e.g. FME Partial Reconfiguration Feature Register Set.
[all …]
|
| /Documentation/s390/ |
| D | s390dbf.rst | 2 S390 Debug Feature
11 The goal of this feature is to provide a kernel debug logging API
21 The debug feature may also very useful for kernel and driver development.
26 feature with the function call :c:func:`debug_register()`.
64 ``/sys/kernel/debug`` therefore the debug feature can be accessed under
89 It is also possible to deactivate the debug feature globally for every
93 There are currently 2 possible triggers, which stop the debug feature
95 set to 1 the debug feature is running. If ``debug_active`` is set to 0 the
96 debug feature is turned off.
98 The second trigger which stops the debug feature is a kernel oops.
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 21 ATA/ATAPI-7 specifies the IDLE IMMEDIATE command with unload feature.
23 unload disk heads. This feature is being used in modern laptops in
27 situations are anticipated. The desire to have such a feature
42 -EOPNOTSUPP if the device does not support the unload feature.
94 since this feature is supposed to be used on laptops and does not seem
110 feature nonetheless. Unfortunately, there is no safe way Linux can
113 support the unload feature (for instance, because the vendor of your
115 kernel to enable the usage of this feature for that drive by writing
120 will enable the feature for /dev/sda, and giving -2 instead of -1 will
149 to develop an implementation of this feature that is fit to be merged
|
| /Documentation/virt/kvm/ |
| D | cpuid.rst | 65 KVM_FEATURE_PV_UNHALT 7 guest checks this feature bit
69 KVM_FEATURE_PV_TLB_FLUSH 9 guest checks this feature bit
77 KVM_FEATURE_PV_SEND_IPI 11 guest checks this feature bit
85 KVM_FEATURE_PV_SCHED_YIELD 13 guest checks this feature bit
89 KVM_FEATURE_ASYNC_PF_INT 14 guest checks this feature bit
95 KVM_FEATURE_MSI_EXT_DEST_ID 15 guest checks this feature bit
113 KVM_HINTS_REALTIME 0 guest checks this feature bit to
|
| /Documentation/firmware-guide/acpi/ |
| D | method-tracing.rst | 173 The temporary debug_layer used when the tracing feature is enabled.
179 The temporary debug_level used when the tracing feature is enabled.
185 The status of the tracing feature.
187 Users can enable/disable this debug tracing feature by executing
195 Disable the method tracing feature.
198 Enable the method tracing feature.
204 Enable the method tracing feature.
210 Enable the method tracing feature.
216 Enable the method tracing feature.
222 Enable the method tracing feature.
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-fm-tx.rst | 101 Enables or disables the audio deviation limiter feature. The limiter
106 Sets the audio deviation limiter feature release time. Unit is in
114 Enables or disables the audio compression feature. This feature
120 Sets the gain for audio compression feature. It is a dB value. The
128 Sets the attack time for audio compression feature. It is a useconds
132 Sets the release time for audio compression feature. It is a
136 Enables or disables the pilot tone generation feature.
|
| /Documentation/filesystems/ext4/ |
| D | group_descr.rst | 10 the block group descriptor table unless the sparse\_super feature flag
21 If the meta\_bg feature flag is set, then several block groups are
29 In ext2, ext3, and ext4 (when the 64bit feature is not enabled), the
31 bg\_checksum. On an ext4 filesystem with the 64bit feature enabled, the
103 RO\_COMPAT\_GDT\_CSUM feature is set, or
105 RO\_COMPAT\_METADATA\_CSUM feature is set. The bg\_checksum
111 - These fields only exist if the 64bit feature is enabled and s_desc_size
|
| D | super.rst | 10 If the sparse\_super feature flag is set, redundant copies of the
137 Note: the difference between the compatible feature set and the
138 incompatible feature set is that if there is a bit set in the
139 incompatible feature set that the kernel doesn't know about, it should
143 about a feature in either the compatible or incompatible feature set, it
160 - Compatible feature set flags. Kernel can still read/write this fs even
166 - Incompatible feature set. If the kernel or fsck doesn't understand one
172 - Readonly-compatible feature set. If the kernel doesn't understand one of
226 - Device number of journal file, if the external journal feature flag is
250 - Size of group descriptors, in bytes, if the 64bit incompat feature flag
[all …]
|
| /Documentation/powerpc/ |
| D | cpu_features.rst | 17 Detection of the feature set is simple. A list of processors can be found in
20 is assigned to the feature bitmask for this processor and a __setup_cpu
24 particular feature bit. This is done in quite a few places, for example
59 __ftr_fixup, and if the required feature is not present it will loop writing
|
| /Documentation/filesystems/ |
| D | overlayfs.rst | 41 with the "xino" feature. The "xino" feature composes a unique object
48 feature with the "-o xino=on" overlay mount option. That is useful for the
224 2. If the "redirect_dir" feature is enabled, then the directory will be
230 There are several ways to tune the "redirect_dir" feature.
240 feature and follow redirects even if turned off.
259 feature is enabled in the kernel/module config.
262 if "redirect_always_follow" feature is not enabled).
264 When the NFS export feature is enabled, every copied up directory is
370 When metadata only copy up feature is enabled, overlayfs will only copy
378 There are multiple ways to enable/disable this feature. A config option
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | intel-speed-select.rst | 50 multi-level help structure in the tool. For example, to get help for the feature "perf-profile"::
73 Intel(R) SST-PP (feature perf-profile) is supported
75 Intel(R) SST-TF (feature turbo-freq) is supported
76 Intel(R) SST-BF (feature base-freq) is not supported
77 Intel(R) SST-CP (feature core-power) is supported
82 This feature allows configuration of a server dynamically based on workload
85 Technology - Performance Profile (Intel(R) SST-PP) feature introduces a mechanism
90 a change in the base frequency dynamically. This feature is called
287 This means that at performance level 4, the "speed-select-base-freq" feature is
288 not supported. However, at performance level 0, this feature is "supported", but
[all …]
|
| /Documentation/arm64/ |
| D | amu.rst | 55 (secondary or hotplugged) to detect and use the feature.
57 When the feature is detected on a CPU, we flag the availability of the
58 feature but this does not guarantee the correct functionality of the
70 When using kernels that have this feature enabled but boot with broken
106 Also, the presence of the feature is not visible to userspace.
|
| D | elf_hwcaps.rst | 30 Where software relies on a feature described by a hwcap, it should check
31 the relevant hwcap flag to verify that the feature is present before
32 attempting to make use of the feature.
34 Features cannot be probed reliably through other means. When a feature
37 that the feature is unavailable, such as a SIGILL.
103 described by Documentation/arm64/cpu-feature-registers.rst.
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-flakey.rst | 23 [<num_features> [<feature arguments>]]
37 Optional feature parameters:
39 If no feature parameters are present, during the periods of
|
12345678910>>...22