Searched full:entry (Results 1 – 25 of 814) sorted by relevance
12345678910>>...33
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-entries | 16 each entry has a common header indicating the type and
17 length of the entry, as well as a firmware-provided
23 never expect to find a specific entry type on their
28 to handle these duplicate entry types, each entry is
30 derived from an entry type's ordinal position. That is
36 Example entry directories::
45 assigned entry handles as the kernel itself makes no
50 Each DMI entry in sysfs has the common header values
55 entry by the firmware. This handle may be
57 length The length of the entry, as presented in the
[all …]
|
| D | sysfs-firmware-sgi_uv | 17 The archtype entry contains the UV architecture type that
20 UVsystab entry both passed from UV BIOS.
22 The hub_type entry is used to select the type of hub which is
26 The hubless entry basically is present and set only if there
27 is no hub. In this case the hub_type entry is not present.
29 The partition_id entry contains the partition id.
35 The coherence_id entry contains the coherence id.
40 The uv_type entry contains the hub revision number.
68 The cnode entry contains the cnode number of the corresponding hub.
71 The location entry contains the location string of the corresponding hub.
[all …]
|
| D | sysfs-firmware-dmi-tables | 6 data referenced by a SMBIOS table entry point. The SMBIOS
7 entry point contains general information, like SMBIOS
9 size of SMBIOS entry point is dependent on SMBIOS version.
10 The format of SMBIOS entry point and DMI structures
13 The dmi/tables provides raw SMBIOS entry point and DMI tables
15 from /dev/mem. The raw SMBIOS entry point and DMI table are
|
| D | sysfs-firmware-efi-esrt | 27 What: /sys/firmware/efi/esrt/entries/entry<N>/
30 Description: Each ESRT entry is identified by a GUID, and each gets a
34 What: /sys/firmware/efi/esrt/entries/entry<N>/fw_type
37 Description: What kind of firmware entry this is:
46 What: /sys/firmware/efi/esrt/entries/entry<N>/fw_class
49 Description: This is the entry's guid, and will match the directory name.
51 What: /sys/firmware/efi/esrt/entries/entry<N>/fw_version
57 What: /sys/firmware/efi/esrt/entries/entry<N>/lowest_supported_fw_version
62 What: /sys/firmware/efi/esrt/entries/entry<N>/capsule_flags
67 What: /sys/firmware/efi/esrt/entries/entry<N>/last_attempt_version
[all …]
|
| D | sysfs-class-mic | 41 When read, this entry provides the current state of an Intel
48 On reading this entry after an OSPM resume,
49 a "boot" has to be written to this entry if
59 When written, this sysfs entry triggers different state change
79 entry provides the status on why the card OS was shutdown.
99 self-bootable machines. When read, this entry provides
101 boot the card OS. This entry can be written to change the
105 line back to this entry.
112 When read, this sysfs entry provides the path name under
114 card can be found. The entry can be written to change the
[all …]
|
| D | debugfs-scmi-raw | 10 entry if it arrived within the configured timeout.
11 Each write to the entry causes one command request to be built
25 entry if it arrived within the configured timeout.
27 from this same entry too if it arrived within the configured
29 Each write to the entry causes one command request to be built
40 can be read from this entry.
51 read from this entry.
60 Description: SCMI Raw stack reset facility; writing a value to this entry
78 entry if it arrived on channel <m> within the configured
80 Each write to the entry causes one command request to be built
[all …]
|
| /Documentation/translations/zh_CN/core-api/ |
| D | kref.rst | 182 struct my_data *entry = NULL;
185 entry = container_of(q.next, struct my_data, link);
186 kref_get(&entry->refcount);
189 return entry;
194 struct my_data *entry = container_of(ref, struct my_data, refcount);
196 list_del(&entry->link);
197 kfree(entry);
200 static void put_entry(struct my_data *entry)
203 kref_put(&entry->refcount, release_entry);
216 static void put_entry(struct my_data *entry)
[all …]
|
| /Documentation/core-api/ |
| D | xarray.rst | 15 next or previous entry in a cache-efficient manner. In contrast to a
35 You must first convert it into an entry using xa_mk_value().
36 When you retrieve an entry from the XArray, you can check whether it is
37 a value entry by calling xa_is_value(), and convert it back to
41 call xa_tag_pointer() to create an entry with a tag, xa_untag_pointer()
42 to turn a tagged entry back into an untagged pointer and xa_pointer_tag()
43 to retrieve the tag of an entry. Tagged pointers use the same bits that
53 the range will return the same entry as looking up any other index in
56 into any entry will cause the XArray to forget about the range.
67 using xa_load(). xa_store will overwrite any entry with the
[all …]
|
| D | kref.rst | 186 struct my_data *entry = NULL;
189 entry = container_of(q.next, struct my_data, link);
190 kref_get(&entry->refcount);
193 return entry;
198 struct my_data *entry = container_of(ref, struct my_data, refcount);
200 list_del(&entry->link);
201 kfree(entry);
204 static void put_entry(struct my_data *entry)
207 kref_put(&entry->refcount, release_entry);
221 static void put_entry(struct my_data *entry)
[all …]
|
| D | maple_tree.rst | 17 entry in a cache-efficient manner. The tree can also be put into an RCU-safe
61 mtree_store() will overwrite any entry with the new entry and return 0 on
63 but takes a range. mtree_load() is used to retrieve the entry stored at a
65 knowing one value within that range, or mtree_store() call with an entry of
68 If you want to only store a new entry to a range (or index) if that range is
72 You can search for an entry from an index upwards by using mt_find().
74 You can walk each entry within a range by calling mt_for_each(). You must
156 mas->index and mas->last according to the range for the entry.
158 You can set entries using mas_store(). mas_store() will overwrite any entry
159 with the new entry and return the first existing entry that is overwritten.
[all …]
|
| D | entry.rst | 1 Entry/exit handling for exceptions, interrupts, syscalls and KVM
22 for entry code before RCU starts watching and exit code after RCU stops
24 which means that (for example) a breakpoint in the breakpoint entry code would
35 noinstr void entry(void)
55 All non-instrumentable entry/exit code sections before and after the RCU
61 Syscall-entry code starts in assembly code and calls out into low-level C code
88 and then invokes the various entry work functions like ptrace, seccomp, audit,
105 ensure that enter_from_user_mode() is called first on entry and
126 Do not nest KVM entry/exit transitions because doing so is nonsensical.
131 Interrupts entry and exit handling is slightly more complex than syscalls
[all …]
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | partition.yaml | 66 This sets the alignment of the entry in bytes.
68 The entry offset is adjusted so that the entry starts on an aligned
70 <16>’ means that the entry will start on a 16-byte boundary. This may
71 mean that padding is added before the entry. The padding is part of
72 the containing section but is not included in the entry, meaning that
73 an empty space may be created before the entry starts. Alignment
83 This sets the alignment of the entry size in bytes. It must be a power
86 For example, to ensure that the size of an entry is a multiple of 64
88 entry itself (the padding is performed only when its parent section is
89 assembled), the end result is that the entry ends with the padding
[all …]
|
| /Documentation/arch/x86/ |
| D | entry_64.rst | 8 arch/x86/entry/entry_64.S. A lot of this explanation is adapted from
14 kernel code. Most of these entry points are registered in
15 arch/x86/kernel/traps.c and implemented in arch/x86/entry/entry_64.S
16 for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
17 arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
18 syscall entry points and thus provides for 32-bit processes the
60 So when we have a secondary entry, already in kernel mode, we *must
67 The cheap way is to pick this info off the entry frame on the kernel
90 entry interrupting kernel mode execution, then we know that the GS
94 But if we are in an NMI/MCE/DEBUG/whatever super-atomic entry context,
[all …]
|
| D | booting-dt.rst | 6 There is one single 32bit entry point to the kernel at code32_start,
7 the decompressor (the real mode entry point goes to the same 32bit
8 entry point once it switched into protected mode). That entry point
|
| /Documentation/devicetree/bindings/sound/ |
| D | img,i2s-in.txt | 11 - clocks : Contains an entry for each entry in clock-names
13 - clock-names : Must include the following entry:
16 - dmas: Contains an entry for each entry in dma-names.
18 - dma-names: Must include the following entry:
|
| D | img,spdif-in.txt | 11 - dmas: Contains an entry for each entry in dma-names.
13 - dma-names: Must include the following entry:
16 - clocks : Contains an entry for each entry in clock-names
|
| D | img,parallel-out.txt | 11 - dmas: Contains an entry for each entry in dma-names.
13 - dma-names: Must include the following entry:
16 - clocks : Contains an entry for each entry in clock-names.
|
| D | img,spdif-out.txt | 11 - dmas: Contains an entry for each entry in dma-names.
13 - dma-names: Must include the following entry:
16 - clocks : Contains an entry for each entry in clock-names.
|
| D | img,i2s-out.txt | 11 - clocks : Contains an entry for each entry in clock-names
17 - dmas: Contains an entry for each entry in dma-names.
19 - dma-names: Must include the following entry:
|
| /Documentation/networking/devlink/ |
| D | devlink-resource.rst | 49 name kvd size 245760 unit entry
51 name linear size 98304 occ 0 unit entry size_min 0 size_max 147456 size_gran 128
52 name hash_double size 60416 unit entry size_min 32768 size_max 180224 size_gran 128
53 name hash_single size 87040 unit entry size_min 65536 size_max 212992 size_gran 128
69 name kvd size 245760 unit entry size_valid false
71 … name linear size 98304 size_new 147456 occ 0 unit entry size_min 0 size_max 147456 size_gran 128
72 name hash_double size 60416 unit entry size_min 32768 size_max 180224 size_gran 128
73 name hash_single size 87040 unit entry size_min 65536 size_max 212992 size_gran 128
|
| /Documentation/locking/ |
| D | robust-futex-ABI.rst | 58 to itself, 'head'. The last 'lock entry' points back to the 'head'.
61 address of the associated 'lock entry', plus or minus, of what will
62 be called the 'lock word', from that 'lock entry'. The 'lock word'
69 the address of the 'lock entry', during list insertion and removal,
73 Each 'lock entry' on the single linked list starting at 'head' consists
74 of just a single word, pointing to the next 'lock entry', or back to
76 entry', at an offset from the 'lock entry' specified by the 'offset'
87 'lock entry' on this list, with its associated 'lock word' at the
107 it currently holds using the 'lock entry' pointers. It may also have
137 protocol on 'lock entry' insertion and removal:
[all …]
|
| /Documentation/trace/ |
| D | fprobe.rst | 4 Fprobe - Function entry/exit probe
12 Fprobe is a function entry/exit probe mechanism based on ftrace.
14 on function entry and exit, similar to the kprobes and kretprobes, you can
23 attach callbacks to multiple function entry and exit. User needs to set up
87 The fprobe entry/exit handler
90 The prototype of the entry/exit callback function are as follows:
98 Note that the @entry_ip is saved at function entry and passed to exit handler.
99 If the entry callback function returns !0, the corresponding exit callback will be cancelled.
107 This is the ftrace address of the traced function (both entry and exit).
108 Note that this may not be the actual entry address of the function but
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 12 associated with a directory file for the particular directory entry that
24 end of the block; the last entry in the block has a record length that
32 The original directory entry format is ``struct ext4_dir_entry``, which
47 - Number of the inode that this directory entry points to.
51 - Length of this directory entry. Must be a multiple of 4.
62 entry format shortens the name_len field and uses the space for a file
79 - Number of the inode that this directory entry points to.
83 - Length of this directory entry.
125 must also include hash information in the directory entry. We append
129 entry uses this extension, it may be up to 271 bytes.
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smp2p.yaml | 74 Marks the entry as inbound; the node should be specified as a two
76 the outgoing entry.
81 qcom,entry-name:
84 The name of this entry, for inbound entries this will be used to
85 match against the remotely allocated entry and for outbound entries
95 - qcom,entry-name
124 # inbound and one outbound entry.
137 qcom,entry-name = "master-kernel";
142 qcom,entry-name = "slave-kernel";
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | lpc1857-eeprom.txt | 5 - reg: Must contain an entry with the physical base address and length
6 for each entry in reg-names.
10 - clocks: Must contain an entry for each entry in clock-names.
|
12345678910>>...33