| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi | 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
54 entry by the firmware. This handle may be
56 length : The length of the entry, as presented in the
[all …]
|
| D | sysfs-platform-kim | 22 command. The entry is read and made use by the user-space
31 entry most often should be 1, the host's UART is required
33 entry can be made use of for exceptions.
44 entry. This entry would be polled upon by the user-space
|
| D | sysfs-bus-rpmsg | 11 This sysfs entry contains the name of this channel.
26 This sysfs entry contains the src (local) rpmsg address
44 This sysfs entry contains the dst (remote) rpmsg address
73 This sysfs entry tells us whether the channel is a local
|
| D | sysfs-firmware-sgi_uv | 13 The partition_id entry contains the partition id.
21 The coherence_id entry contains the coherence id.
|
| /Documentation/s390/ |
| D | s390dbf.txt | 28 An event-call writes the specified debug entry to the active debug
31 and the next debug entry will be written at the beginning of the active
34 An exception-call writes the specified debug entry to the log and
46 Each debug entry contains the following data:
50 - Level of debug entry (0...6)
52 - Flag, if entry is an exception or not
107 Parameter: name: Name of debug log (e.g. used for debugfs entry)
110 buf_size: size of data area in each debug entry
123 Parameter: name: Name of debug log (e.g. used for debugfs entry)
126 buf_size: Size of data area in each debug entry
[all …]
|
| /Documentation/RCU/ |
| D | listRCU.txt | 95 static inline int audit_add_rule(struct audit_entry *entry,
99 if (entry->rule.flags & AUDIT_PREPEND) {
100 entry->rule.flags &= ~AUDIT_PREPEND;
101 list_add(&entry->list, list);
103 list_add_tail(&entry->list, list);
128 static inline int audit_add_rule(struct audit_entry *entry,
131 if (entry->rule.flags & AUDIT_PREPEND) {
132 entry->rule.flags &= ~AUDIT_PREPEND;
133 list_add_rcu(&entry->list, list);
135 list_add_tail_rcu(&entry->list, list);
[all …]
|
| /Documentation/ |
| D | kref.txt | 156 struct my_data *entry = NULL;
159 entry = container_of(q.next, struct my_data, link);
160 kref_get(&entry->refcount);
163 return entry;
168 struct my_data *entry = container_of(ref, struct my_data, refcount);
170 list_del(&entry->link);
171 kfree(entry);
174 static void put_entry(struct my_data *entry)
177 kref_put(&entry->refcount, release_entry);
191 static void put_entry(struct my_data *entry)
[all …]
|
| D | robust-futex-ABI.txt | 56 to itself, 'head'. The last 'lock entry' points back to the 'head'.
59 address of the associated 'lock entry', plus or minus, of what will
60 be called the 'lock word', from that 'lock entry'. The 'lock word'
67 the address of the 'lock entry', during list insertion and removal,
71 Each 'lock entry' on the single linked list starting at 'head' consists
72 of just a single word, pointing to the next 'lock entry', or back to
74 entry', at an offset from the 'lock entry' specified by the 'offset'
85 'lock entry' on this list, with its associated 'lock word' at the
105 it currently holds using the 'lock entry' pointers. It may also have
135 protocol on 'lock entry' insertion and removal:
[all …]
|
| /Documentation/kbuild/ |
| D | kconfig-language.txt | 20 Every entry has its own dependencies. These dependencies are used
21 to determine the visibility of an entry. Any child entry is only
22 visible if its parent entry is also visible.
38 arguments. "config" starts a new config entry. The following lines
48 A menu entry can have a number of attributes. Not all of them are
63 Every menu entry can have at most one prompt, which is used to display
70 Default values are not limited to the menu entry where they are
86 This defines a dependency for this menu entry. If multiple
88 are applied to all other options within this menu entry (which also
139 which can modify the behaviour of the menu entry and its config
[all …]
|
| /Documentation/x86/ |
| D | entry_64.txt | 8 kernel code. Most of these entry points are registered in
51 So when we have a secondary entry, already in kernel mode, we *must
58 The cheap way is to pick this info off the entry frame on the kernel
84 entry interrupting kernel mode execution, then we know that the GS
88 But if we are in an NMI/MCE/DEBUG/whatever super-atomic entry context,
89 which might have triggered right after a normal entry wrote CS to the
93 So we try only to mark those entry methods 'paranoid' that absolutely
95 'normal' entry points with the regular (faster) entry macros.
|
| /Documentation/filesystems/nfs/ |
| D | nfs.txt | 38 valid entry. If so, it returns that entry and exits.
40 (2) If no valid entry exists, the helper script '/sbin/nfs_cache_getent'
56 script, and <ttl> is the 'time to live' of this cache entry (in
60 entry is created, which will cause the kernel to treat the hostname
|
| D | rpc-cache.txt | 31 cache entries, and replaying those requests when the cache entry
85 cache entry. It is in 'buf' of length 'len'.
100 This will be passed to ->match to identify the target entry. If no
101 entry is found, a new entry will be create, added to the cache, and
106 cache_check will return -ENOENT in the entry is negative or if an up
150 lookup fails, or when it succeeds but finds an entry that may soon
181 entry will fail. This is partly for backward compatibility: The
|
| /Documentation/cgroups/ |
| D | devices.txt | 7 whitelist with each cgroup. A whitelist entry has 4 fields.
22 An entry is added using devices.allow, and removed using
32 will remove the default 'a *:* rwm' entry. Doing
36 will add the 'a *:* rwm' entry to the whitelist.
|
| /Documentation/filesystems/ |
| D | vfat.txt | 145 a get next directory entry approach. The only thing left that uses
190 Here is the description of the traditional FAT entry in the current
225 specially formatted directory entry which holds up to 13 characters of
227 directory entry of the file to which they correspond. Microsoft
228 prefers to refer to the 8.3 entry for a file as its alias and the
231 The C structure for a slot directory entry follows:
249 1) The attribute byte for a slot directory entry is always set
250 to 0x0f. This corresponds to an old directory entry with
262 verify that a slot does in fact belong to an 8.3 directory entry by
266 their corresponding 8.3 directory entry. In addition, each
[all …]
|
| D | sysfs-tagging.txt | 20 Each sysfs directory entry may be tagged with zero or one
22 directory entry is tagged, then sysfs_dirent->s_flags will have a
|
| /Documentation/powerpc/ |
| D | hvcs.txt | 167 "dev" entry in the hvcs directory:
186 Given the example output above, to manually create a /dev/hvcs* node entry
249 attribute has been added to each vty-server sysfs entry. This entry is
251 /dev/hvcs* entry to use to connect to that device. For instance cating the
261 system the /dev/hvcs* entry that interacts with a particular vty-server
298 "vterm_state" sysfs attribute within each vty-server's sysfs entry is used.
324 Each vty-server has a sysfs entry in the /sys/devices/vio directory, which
326 hvcs driver entry, which looks like the following example:
346 address that is created by firmware. An example vty-server sysfs entry
353 Each entry is provided, by default with a "name" attribute. Reading the
[all …]
|
| D | zImage_layout.txt | 17 hard drive. The firmware reads the PReP partition table entry
28 | | PReP partition table entry
|
| /Documentation/devicetree/bindings/fb/ |
| D | sm501fb.txt | 9 - First entry: System Configuration register
10 - Second entry: IO space (Display Controller register)
|
| /Documentation/networking/timestamping/ |
| D | timestamping.c | 286 struct iovec entry; in recvpacket() local
295 msg.msg_iov = &entry; in recvpacket()
297 entry.iov_base = data; in recvpacket()
298 entry.iov_len = sizeof(data); in recvpacket()
|
| /Documentation/networking/ |
| D | proc_net_tcp.txt | 9 TCP connections. A typical entry of /proc/net/tcp would look like this (split
18 |----------------------------------> number of entry
|
| D | scaling.txt | 37 implementation of RSS uses a 128-entry indirection table where each entry
143 can be configured for each receive queue using a sysfs file entry:
183 The CPU recorded in each entry is the one which last processed the flow.
184 If an entry does not hold a valid CPU, then packets mapped to that entry
213 entry i is actually selected by hash and multiple flows may hash to the
214 same entry i).
280 automatically calls this function every time a flow entry in
350 queue is configured using the sysfs file entry:
|
| /Documentation/sh/ |
| D | new-machine.txt | 210 require the proper entry here and there in order to get things done.
212 The first thing to do is to add an entry to arch/sh/Kconfig, under the
221 machdir-y entry in order to be built. This entry needs to be the name of
224 need to be listed). For our new board, this entry can look like:
236 Once that is taken care of, it's time to add an entry for the mach type.
237 This is done by adding an entry to the end of the arch/sh/tools/mach-types
|
| /Documentation/ABI/stable/ |
| D | vdso | 13 entry point. The AT_SYSINFO_EHDR entry will point to the vDSO.
|
| /Documentation/frv/ |
| D | kernel-ABI.txt | 60 handler. On entry to the handler, the PSR.T bit will be cleared.
85 entry.S in the exception prologue. Note that there is a complete set of
98 GR30 Destroyed by kernel mode entry
99 GR31 NOMMU Destroyed by debug mode entry
100 GR31 MMU Destroyed by TLB miss kernel mode entry
160 switch off on entry to an exception. That means unless manually disabled,
|
| /Documentation/arm/SA1100/ |
| D | Brutus | 16 entry.
27 entry 0xc0008000
|