Home
last modified time | relevance | path

Searched refs:was (Results 1 – 200 of 793) sorted by relevance

1234

/linux-4.4.14/Documentation/scheduler/
Dsched-stats.txt7 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel
38 1) # of times sched_yield() was called
43 3) # of times schedule() was called
47 5) # of times try_to_wake_up() was called
48 6) # of times try_to_wake_up() was called to wake up the local cpu
70 1) # of times in this domain load_balance() was called when the
71 cpu was idle
73 the load did not require balancing when the cpu was idle
75 more tasks and failed, when the cpu was idle
77 load_balance() in this domain when the cpu was idle
[all …]
Dsched-nice-design.txt7 Unfortunately that was not that easy to implement under the old
9 support was historically coupled to timeslice length, and timeslice
10 units were driven by the HZ tick, so the smallest timeslice was 1/HZ.
37 changing the ABI to extend priorities was discarded early on.)
44 this was long ago when hardware was weaker and caches were smaller, and
56 coupling to timeslices and granularity it was not really viable.
59 about Linux's nice level support was its assymetry around the origo
75 depend on the nice level of the parent shell - if it was at nice -10 the
76 CPU split was different than if it was at +5 or +10.
78 A third complaint against Linux's nice level support was that negative
[all …]
Dcompletion.txt4 This document was originally written based on 3.18.0 (linux-next)
161 This function marks the task TASK_INTERRUPTIBLE. If a signal was received
178 TASK_INTERRUPTIBLE. If a signal was received it will return -ERESTARTSYS;
184 else 0 if completion was achieved. There is a _timeout variant as well:
/linux-4.4.14/Documentation/filesystems/
Dlocks.txt14 The old flock(2) emulation in the kernel was swapped for proper BSD
29 Because sendmail was unable to use the old flock() emulation, many sendmail
31 for example. This gave rise to some other subtle problems if sendmail was
46 race and deadlock conditions that the current solution was the only
57 'Documentation/filesystems/mandatory-locking.txt' was prior to this release a
58 general configuration option that was valid for all mounted filesystems. This
59 had a number of inherent dangers, not the least of which was the ability to
Ddnotify.txt15 DN_ACCESS A file in the directory was accessed (read)
16 DN_MODIFY A file in the directory was modified (write,truncate)
17 DN_CREATE A file was created in the directory
18 DN_DELETE A file was unlinked from directory
19 DN_RENAME A file in the directory was renamed
Defivarfs.txt4 The efivarfs filesystem was created to address the shortcomings of
7 limitation existed in version 0.99 of the EFI specification, but was
Dautomount-support.txt53 If a vfsmount was already flagged for expiry, and if its usage count is 1
62 mountpoint was accessed.
86 If the mountpoint was not already marked for expiry at that time, an EAGAIN
89 Otherwise if it was already marked and it wasn't referenced, unmounting will
Dhpfs.txt106 file has a pointer to codepage its name is in. However OS/2 was created in
111 Czech OS/2, the file was completely inaccessible under any name. It seems that
115 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
119 funny thing was that, when rebooted, PmShell tried to reopen this directory
122 system although HPFS was designed to allow that.
210 0.91 Fixed bug that caused shooting to memory when write_inode was called on
217 0.95 Fixed a bug that i_hpfs_parent_dir was not updated when moving files
231 1.92 Corrected a bug when sync was called just before closing file
241 (this bug was not destructive)
250 Fixed a bug that it set badly one flag in large anode tree (it was not
[all …]
Dxfs-self-describing-metadata.txt79 block. If we can verify the block contains the metadata it was intended to
82 CRC32c was selected as metadata cannot be more than 64k in length in XFS and
102 and/or corrupted, and how long ago that it was last modified. Knowing the owner
119 Self describing metadata also needs to contain some indication of when it was
121 analysis is how recently the block was modified. Correlation of set of corrupted
129 when the free space btree block that contains the block was last written
130 compared to when the metadata object itself was last written. If the free space
135 Number (LSN) of the most recent transaction it was modified on written into it.
141 modification occurred between the corruption being written and when it was
164 object matches what was expected. If the verification process fails, then it
[all …]
Dext3.txt5 Ext3 was originally released in September 1999. Written by Stephen Tweedie
Dext2.txt5 ext2 was originally released in January 1993. Written by R\'emy Card,
6 Theodore Ts'o and Stephen Tweedie, it was a major rewrite of the
120 was mounted (and if it was cleanly unmounted), when it was modified,
130 machines without having to know what machine it was created on.
221 run if the filesystem was not cleanly unmounted, if the maximum mount
232 the original revision 0 (EXT2_GOOD_OLD_REV) of ext2, but was introduced in
264 INCOMPAT flag because older kernels would think a filename was longer
Dramfs-rootfs-initramfs.txt38 device was of fixed size, so the filesystem mounted on it was of fixed
66 A ramfs derivative called tmpfs was created to add size limits, and the ability
101 - The old initrd was always a separate file, while the initramfs archive is
105 - The old initrd file was a gzipped filesystem image (in some file format,
112 - The program run by the old initrd (which was called /initrd, not /init) did
282 This decision was made back in December, 2001. The discussion started here:
319 extract this format anyway. Using an existing standard was preferable,
Dinotify.txt39 every fd was a separate watch,
77 interfaces. The only real difference was whether we wanted to use open(2)
Dgfs2-uevents.txt47 Because the CHANGE uevent was used (in early versions of gfs_controld)
51 cluster. For this reason the ONLINE uevent was used when adding a new
/linux-4.4.14/Documentation/arm/nwfpe/
DREADME4 The majority of the code was written by me, Scott Bambrough It is
6 where required. It was written quickly, with a goal of implementing a
17 Another choice I made was in the file structure. I have attempted to
30 SoftFloat to the ARM was done by Phil Blundell, based on an earlier
57 SoftFloat was written by John R. Hauser. This work was made possible in
59 1947 Center Street, Berkeley, California 94704. Funding was partially
61 original version of this code was written as part of a project to build
DNOTES11 I was looking at some code, that calculated a double result, stored it in f4
/linux-4.4.14/fs/reiserfs/
DREADME40 fair, ask. (Last I spoke with him Richard was contemplating how best
84 Hans Reiser was the project initiator, primary architect, source of all
88 Vladimir Saveljev was one of the programmers, and he worked long hours
91 was quite remarkable. I don't think that money can ever motivate someone
99 substantial portion of the total code. He realized that there was a
106 tried to put me in a position where I was forced into giving control
109 really force takeovers of sole proprietorships.) This was something
111 why we should do what we do, or why innovation was possible in
112 general, but he was sure that he ought to be controlling it. Every
113 innovation had to be forced past him while he was with us. He added
[all …]
/linux-4.4.14/Documentation/scsi/
Dsym53c500_cs.txt2 package, and was written by Tom Corner (tcorner@via.at). A rewrite was
8 All the USE_BIOS code has been ripped out. It was never used, and could
14 The Symbios Logic 53c500 chip was used in the "newer" (circa 1997) version
Ddpti.txt23 * The original linux driver was ported to Linux by Karen White while at
24 * Dell Computer. It was ported from Bob Pasteur's (of DPT) original
31 * The driver was originally ported to linux version 2.0.34
34 * This was the first full GPL version since the last version used
DFlashPoint.txt82 discover that the FlashPoint was not supported and would not be for quite
85 After this problem was identified, BusLogic contacted its major OEM
89 many purchasers of new systems, it was only a partial solution to the
93 ended up with a FlashPoint LT, believing it was supported, and were unable
100 it was best that these issues be addressed directly. I sent an email
138 I was a beta test site for the BT-948/958, and versions 1.2.1 and 1.3.1 of
140 Additional cosmetic support for the Ultra SCSI MultiMaster cards was added
145 are crucial to overall system stability. It was especially convenient
Dlpfc.txt34 received from the midlayer. In the cases where a cable was pulled, link
51 As a potential new addition to kernel.org, the 8.x driver was asked to
58 The proposed patch was posted to the linux-scsi mailing list. The patch
DChangeLog.lpfc29 if we timed out waiting for command to complete after abort was
33 - was causing spurious 0710 messages.
108 waking up the els_tmo handler un-necessarily. The thread was
116 driver was not handling LPFC_IO_POLL cases correctly in
117 fast_ring_event and was setting the tgt_reset timeout to 0 in
129 * Close humongous memory leak in lpfc_sli.c - driver was losing 13
346 Convert to using block/unblock on list remove (was del/add)
355 freed (after nodev tmo). This bug was causing i/o received in
356 the small window while the device was blocked to be errored w/
388 * Fixed bug introduced when discovery thread implementation was
[all …]
DChangeLog.sym53c8xx_235 Misdetection of BUS mode was triggered on module reload only,
44 from SCRIPTS :) in the patch method (was wrongly placed in
84 - Mask GPCNTL against 0x1c (was 0xfc) for the reading of the NVRAM.
DChangeLog.sym53c8xx14 - Fix an unaligned LOAD from scripts (was used as dummy read).
51 bytes was not enough for the PPR message (fix).
92 This facility was not this useful and thus was not longer
177 profile support option was set in kernel configuration.
287 the SCRIPT processor when this one was already running.
347 - Fix the misdetection of SYM53C875E (was detected as a 876).
348 - Fix the misdetection of SYM53C810 not A (was detected as a 810A).
482 was in fact misplaced. BTW, this may explain why broken PCI
485 binary code was a bit too bloated in my opinion.
503 It was not possible to disable TGQ at system startup for devices
[all …]
DChangeLog.ncr53c8xx28 This facility was not this useful and thus was not longer
231 It was not possible to disable TGQ at system startup for devices
238 - The driver was unhappy when configured with default_tags > MAX_TAGS
281 was read from the SFBR i/o register after the previous message had
283 This was not correct and affects all previous driver versions and
294 the problem observed when the driver was compiled using EGCS or
324 - Remove the ncr_opennings() stuff that was useless under Linux
373 the print statement was misplaced for modules.
Dqlogicfas.txt69 the computer was left on for a few hours. It was worse with longer
/linux-4.4.14/tools/testing/selftests/ftrace/
DREADME55 * FAIL: The test failed, but was expected to succeed. The test which exits
59 for example, the test was interrupted
61 or the test was set up incorrectly
64 * UNTESTED: The test was not run, currently just a placeholder.
70 * XFAIL: The test failed, and was expected to fail.
/linux-4.4.14/arch/arm/kvm/
Dtrace.h304 TP_PROTO(unsigned long vcpu_pc, bool was, bool now),
305 TP_ARGS(vcpu_pc, was, now),
309 __field( bool, was )
315 __entry->was = was;
320 __entry->vcpu_pc, __entry->was ? "on" : "off",
/linux-4.4.14/Documentation/usb/
Derror-codes.txt60 -EPERM Submission failed because urb->reject was set.
62 -EHOSTUNREACH URB was rejected because the device is suspended.
90 -ENOENT URB was synchronously unlinked by usb_unlink_urb
107 driver cannot tell whether there was a protocol
117 completed, and no other error was reported by HC.
130 -EOVERFLOW (*) The amount of data returned by the endpoint was
135 specified buffer, and URB_SHORT_NOT_OK was set in
138 -ENODEV Device was removed. Often preceded by a burst of
147 -ECONNRESET URB was asynchronously unlinked by usb_unlink_urb
Dpersist.txt20 device is still attached or perhaps it was removed and a different
30 If the kernel wants to believe that your USB keyboard was unplugged
31 while the system was asleep and a new keyboard was plugged in when the
37 been unplugged while the system was suspended. If you had a mounted
40 root filesystem was located on the device, since your system will
46 was asleep, on many systems during the initial stages of wakeup the
57 has happened; look for lines saying "root hub lost power or was reset".
73 not in the expected state during resume (i.e., if the controller was
87 but a USB device was unplugged and then replugged, or if a USB device
Dohci.txt5 was written primarily by Roman Weissgaerber <weissg@vienna.at> but with
24 types can be queued. That was also true in "usb-ohci", except for interrupt
Dpower-management.txt50 System PM support is present only if the kernel was built with CONFIG_SUSPEND
52 the kernel was built with CONFIG_PM enabled.
54 [Historically, dynamic PM support for USB was present only if the
57 for USB was present whenever the kernel was built with CONFIG_PM_RUNTIME
136 file was deprecated as of the 2.6.35 kernel and replaced by the
169 suspended and autoresume was not allowed. This
189 from being autosuspended; the behavior was changed in 2.6.22. The
192 was added in 2.6.34, and power/autosuspend_delay_ms was added in
253 (In 2.6.21 and 2.6.22 this wasn't the case. Autosuspend was enabled
406 idle. This is perfectly normal. If the reason for failure was that
[all …]
Dlinux.inf3 ; which was:
/linux-4.4.14/drivers/block/paride/
DTransition-notes36 ps_tq if ps_tq_active was 0.
62 In the first case the thread was already in the area. In the second,
63 the thread was holding pd_lock and found pd_busy not set, which would
64 mean that (2) was already not true.
70 (3) was already not true.
79 pd.c. It means that (4) was already not true.
89 If it was 0 before we tried to acquire pd_lock, (2) would be
108 point, we would have violated either (2.1) (if it was set while ps_set_intr()
109 was acquiring ps_spinlock) or (2.3) (if it was set when we started to
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-api.txt96 printf("The timeout was set to %d seconds\n", timeout);
98 This example might actually print "The timeout was set to 60 seconds"
105 printf("The timeout was is %d seconds\n", timeout);
127 printf("The pretimeout was is %d seconds\n", timeout);
138 printf("The timeout was is %d seconds\n", timeleft);
162 The machine was last rebooted by the watchdog because the thermal limit was
171 External monitoring relay/source 1 was triggered. Controllers intended for
177 External monitoring relay/source 2 was triggered
185 The last reboot was caused by the watchdog card
195 The watchdog saw a keepalive ping since it was last queried.
/linux-4.4.14/arch/arm/mm/
Dtlb-v6.S49 mcr p15, 0, r0, c8, c6, 1 @ TLB invalidate D MVA (was 1)
51 mcrne p15, 0, r0, c8, c5, 1 @ TLB invalidate I MVA (was 1)
53 mcr p15, 0, r0, c8, c7, 1 @ TLB invalidate MVA (was 1)
Dabort-ev5t.S26 teq_ldrd tmp=ip, insn=r3 @ insn was LDRD?
Dabort-ev5tj.S28 teq_ldrd tmp=ip, insn=r3 @ insn was LDRD?
Dabort-ev6.S37 teq_ldrd tmp=ip, insn=r3 @ insn was LDRD?
/linux-4.4.14/Documentation/i2c/
Dfault-codes40 transmit mode: some other master was transmitting different
57 Returned by SMBus adapters when the bus was busy for longer
60 or that the reset was attempted but failed.
64 detected before any I/O operation was started. Use a more
87 an I2C device was temporarily not responding, usually it
100 have verified that functionality was supported before it
117 time, and was aborted before it completed.
Dsmbus-protocol180 SMBus Block Write - Block Read Process Call was introduced in
206 Packet Error Checking was introduced in Revision 1.1 of the specification.
215 The Address Resolution Protocol was introduced in Revision 2.0 of
227 SMBus Alert was introduced in Revision 1.0 of the specification.
Dinstantiating-devices154 pointer that was earlier returned by i2c_new_device() or
191 was done there. Two significant differences are:
192 * Probing is only one way to instantiate I2C devices now, while it was the
212 sysfs interface was added to let the user provide the information. This
Dslave-interface76 our own address and the write bit was detected. The data did not arrive yet, so
86 our own address and the read bit was detected. After returning, the bus driver
117 A stop condition was received. This can happen anytime and the backend should
Dwriting-clients119 The Linux I2C stack was originally written to support access to hardware
122 assumptions was that most adapters and devices drivers support the SMBUS_QUICK
123 protocol to probe device presence. Another was that devices and their drivers
158 matches the device's name. It is passed the entry that was matched so
197 was working, and is now available as an extension to the standard
/linux-4.4.14/tools/perf/Documentation/
Dperf-sched.txt24 was recorded (aliased to 'perf script' for now).
26 'perf sched replay' to simulate the workload that was recorded
30 of the workload as it occurred when it was recorded - and can repeat
Dcallchain-overhead-calculation.txt95 In the above output, the 'self' overhead of 'foo' (60%) was add to the
97 Likewise, the 'self' overhead of 'bar' (40%) was added to the
/linux-4.4.14/Documentation/w1/slaves/
Dw1_ds242324 was successful and CRC matched.
25 If the operation was successful, there is also in the end of each line
32 - 2 bytes for crc16 which was calculated from the data read since the previous crc bytes
34 - crc=YES/NO indicating whether read was ok and crc matched
/linux-4.4.14/arch/m68k/ifpsp060/
DCHANGES33 1) "movep" emulation where data was being read from memory
34 was reading the intermediate bytes. Emulation now only
37 2) "flogn", "flog2", and "flog10" of "1" was setting the
42 mode was pre-decrement or post-increment and the address register
43 was A0 or A1, the address register was not being updated as a result
DREADME58 was connected properly; hex image
61 itest.sa Simple test program to test that isp.sa was
/linux-4.4.14/Documentation/networking/
Dlapb-module.txt136 LAPB_OK LAPB getparms was successful.
148 LAPB_OK LAPB getparms was successful.
150 LAPB_INVALUE One of the values was out of its allowable range.
224 LAPB_OK The LAPB link was terminated normally.
225 LAPB_NOTCONNECTED The remote system was not connected.
226 LAPB_TIMEDOUT No response was received in N2 tries from the remote
237 LAPB_OK The LAPB link was terminated normally by the remote
240 LAPB_NOTCONNECTED The remote system was not connected.
241 LAPB_TIMEDOUT No response was received in N2 tries from the remote
254 file include/linux/netdevice.h) if and only if the frame was dropped
Dskfp.txt125 The functionality of the LED's on the FDDI network adapters was
132 With versions of SMT prior to v2.82 a ring up was indicated if the
133 yellow LED was off while the green LED(s) showed the connection
134 status of the adapter. During a ring down the green LED was off and
135 the yellow LED was on.
186 - Synchronization on SMP machines was buggy
Dnetif-msg.txt9 The design of the debugging message interface was guided and
18 The message level was not precisely defined past level 3, but were
30 Initially this message level variable was uniquely named in each driver
Deql.txt12 which was only created to patch cleanly in the very latest kernel
242 up of the driver was tuned to handle slaves with wildly different
246 All testing I have done was with two 28.8 V.FC modems, one connecting
251 One version of the scheduler was able to push 5.3 K/s through the
265 o icee from LinuxNET patched 1.1.86 without any rejects and was able
363 Once a link was established, I timed a binary ftp transfer of
470 it over twin SL/IP lines, just over null modems, but I was
Dcxacru.txt7 Note: support for cxacru-cf.bin has been removed. It was not loaded correctly
91 "poll" (used to resume status polling if it was disabled due to failure)
Dbatman-adv.txt15 Batman advanced was implemented as a Linux kernel driver to re-
41 Note: After the module was loaded it will continuously watch for
44 chine after batman advanced was initially loaded.
181 as expected. To overcome these problems batctl was created. At
/linux-4.4.14/Documentation/mtd/
Dnand_ecc.txt5 I felt there was room for optimisation. I bashed the code for a few hours
7 After that the speed was increased by 35-40%.
8 Still I was not too happy as I felt there was additional room for improvement.
10 Bad! I was hooked.
24 not use the right terminology, my coding theory class was almost 30
25 years ago, and I must admit it was not one of my favourites).
153 Therefore without implementing this it was clear that the code above was
260 almost 4 times as much time as the linux driver code. But hey, if it was
438 observation was that this one is only 30% slower (according to time)
441 Well, it was expected not to be easy so maybe instead move to a
[all …]
/linux-4.4.14/fs/affs/
DChanges162 This was fixed before, but somehow got lost.
172 inode if the fs was not an OFS. This bug only shows
173 up if a file was enlarged via truncate() and there
174 was not enough space.
188 - Fixed bug in balloc(): Superblock was not set dirty after
189 the bitmap was changed, so the bitmap wasn't sync'd.
192 zone number was zero, the loop didn't terminate,
250 cache. If a file was extended by means of
303 was calculated and in the one following. This
/linux-4.4.14/Documentation/
Dpercpu-rw-semaphore.txt25 The idea of using RCU for optimized rw-lock was introduced by
27 The code was written by Mikulas Patocka <mpatocka@redhat.com>
Dunshare.txt43 shared at the time of their creation. unshare was conceptualized by
85 ability to unshare after the process was created can be very
102 unshare reverses sharing that was done using clone(2) system call,
108 However, there was no easy solution that was less confusing and that
162 EPERM CLONE_NEWNS was specified by a non-root process (process
168 EINVAL Invalid flag was specified as an argument.
202 current context structure was moved into new dup_* functions. Now,
231 function. The first component was split into its own function.
236 copy function was called.
Dbcache.txt34 or dirty data), caching is automatically disabled; if dirty data was present
104 but all the cached data will be invalidated. If there was dirty data in the
252 inconsistent: The backing device was forcibly run by the user when there was
253 dirty data cached but the cache set was unavailable; whatever data was on the
301 Counts instances where data was going to be inserted into the cache from a
302 cache miss, but raced with a write and data was already present (usually 0
303 since the synchronization for cache misses was rewritten)
393 Counts instances where while data was being read from the cache, the bucket
394 was reused and invalidated - i.e. where the pointer was stale after the read
DIRQ-affinity.txt38 As can be seen from the line above IRQ44 was delivered only to the first four
55 This time around IRQ44 was delivered only to the last four processors.
Dcpu-load.txt18 kernel, and was overall 81.63% of the time idle.
25 signalled the kernel looks what kind of task was running at this
Dkmemcheck.txt80 modifies memory that was tracked by kmemcheck, the result is an
264 If your kernel was compiled with CONFIG_DEBUG_INFO=y, then all we have to do
278 In this case, the flag was very important, because otherwise, it would only
297 Since this was a read (kmemcheck usually warns about reads only, though it can
298 warn about writes to unallocated or freed memory as well), it was probably the
300 of calls, we move upwards to see where "from" was allocated or initialized,
322 variable "first" was found on a list -- passed in as the second argument to
324 where the item on "list" was allocated or initialized. We move to line 410:
463 And, you might remember, it was a memcpy() on &first->info that caused the
492 uninitialized memory was located, we have to look at the disassembly. For
[all …]
Dlogo.txt3 that I have not really announced it yet). It was created by Larry Ewing,
Ddebugging-modules.txt10 In the past a debugging message which would fill people's logs was
Dcputopology.txt116 In this example, the NR_CPUS config option is 128, but the kernel was
118 was manually taken offline (and is the only CPU that can be brought
Dunicode.txt38 Linux we call it the "Linux Zone"). U+F000 was picked as the starting
85 In 1996, Linux was the first operating system in the world to add
87 for the "Star Trek" television series. This encoding was later
Doops-tracing.txt70 well made (like this one was - run through ksymoops to get the
119 Essentially, you just look at what doesn't match (in this case it was the
234 2: 'F' if any module was force loaded by "insmod -f", ' ' if all
242 4: 'R' if a module was force unloaded by "rmmod -f", ' ' if all
254 8: 'D' if the kernel has died recently, i.e. there was an OOPS or BUG.
Dbasic_profiling.txt41 a 0Hz CPU, APIC was not on. Be aware that idle=poll may mean a performance
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs-rdma.txt24 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
25 was first included in the following release, Linux 2.6.25.
56 The first kernel release to contain both the NFS/RDMA client and server was
66 nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils
241 If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
246 Regardless of how the server was built (module or built-in), start the
261 If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
266 Regardless of how the client was built (module or built-in), use this
Dknfsd-stats.txt62 an nfsd thread to service it, i.e. no nfsd thread was considered
65 The circumstance this statistic tracks indicates that there was NFS
87 i.e. was not woken to handle any incoming network packets for
Didmapper.txt53 Notice that the new line was added above the line for the generic program.
75 nfs.idmap will return 0 if the key was instantiated, and non-zero otherwise.
/linux-4.4.14/Documentation/hwmon/
Dlm7730 was 80 degrees C, and the hysteresis was 75 degrees C, and you change
Demc140351 was 80 degrees C, and the hysteresis was 75 degrees C, and you change
Dthmc5016 This driver was derived from the 2.4 kernel thmc50.c source file.
72 The driver was tested on Compaq AP550 with two ADM1022 chips (one works
Dlm9235 Support was added later for the LM76 and Maxim MAX6633/MAX6634/MAX6635,
/linux-4.4.14/drivers/video/logo/
Dlogo_blackfin_clut224.ppm2 # This was generated by the GIMP & Netpbm tools
Dlogo_blackfin_vga16.ppm2 # This was generated by the GIMP & Netpbm tools
/linux-4.4.14/Documentation/ABI/testing/
Ddebugfs-driver-genwqe40 Description: Internal chip state of UID0 before card was reset.
46 Description: Internal chip state of UID1 before card was reset.
52 Description: Internal chip state of UID2 before card was reset.
Dsysfs-class-scsi_tape106 was found when the SCSI midlayer indicated that there was
Dconfigfs-usb-gadget-mass-storage24 is enabled as well as when it was impossible
Dsysfs-class-net-mesh48 node if gw_mode was set to 'server'.
62 to choose a gateway if gw_mode was set to 'client'.
Ddebugfs-pfo-nx-crypto14 - A u32 providing a total count of errors since the driver was loaded. The
Dsysfs-driver-hid-wiimote50 Description: This attribute is only provided if the device was detected as a
65 Description: This attribute is only provided if the device was detected as a
Dsysfs-fs-ext472 of data that have been written to this filesystem since it was
81 filesystem since it was mounted.
Dsysfs-kernel-slab72 was empty but there were objects available as the result of
148 was deactivated. It can be written to clear the current count.
158 was deactivated. It can be written to clear the current count.
179 slab was deactivated and added to the head of its node's partial
190 slab was deactivated and added to the tail of its node's partial
231 using the fast path because it was an object from the cpu slab.
/linux-4.4.14/Documentation/block/
Dbiovecs.txt49 * Before, iterating over bios was very awkward when you weren't processing
52 wouldn't necessarily be the same size, the old code was tricky convoluted -
63 it somewhere else if there was an error) had to save the entire bvec array
64 - again, this was being done in a fair number of places.
86 fine to _most_ devices, but since accessing the raw bvec array was the
/linux-4.4.14/fs/befs/
DChangeLog7 * Fixed module makefile problem. It was not compiling all the correct
47 block being read. It was introduced when adding byteswapping in
105 * Removed notion of btree handle from btree.c. It was unnecessary, as the
139 * Anton Altaparmakov figured out (by asking Linus :) ) what was causing the
189 * Fixed a thinko that was corrupting file reads after the first block_run
250 Subtle, because the old version was only sometimes wrong.
281 I have no intention of supporting it, and it was very ugly.
328 Make sure inode we got was the one we asked for.
339 * Fixed the problem with statfs where it would always claim the disk was
369 Not that it was possible to write before. But now the kernel won't even try.
/linux-4.4.14/arch/x86/math-emu/
DREADME26 which was my 80387 emulator for early versions of djgpp (gcc under
27 msdos); wm-emu387 was in turn based upon emu387 which was written by
67 upon Newton's classic method. Performance was improved by capitalizing
71 "optimal" polynomial approximations. My definition of "optimal" was
120 operation was performed.
200 there was no reason not to use it after I had edited it to be
239 each function was tested at about 400 points. Ideal worst-case results
304 the transcendental functions (in their principal range) was not as
314 columns shows that an accuracy of between 63.80 and 63.89 bits was
321 the worst accuracy which was found (in bits) and the approximate value
[all …]
/linux-4.4.14/Documentation/development-process/
D3.Early-stage20 by excessive latency in the system. The solution they arrived at was a
23 access to the realtime scheduler. This module was implemented and sent to
26 To the audio developers, this security module was sufficient to solve their
27 immediate problem. To the wider kernel community, though, it was seen as a
47 The reality of the situation was different; the kernel developers were far
97 - The Devicescape network stack was designed and implemented for
99 until it was made suitable for multiprocessor systems. Retrofitting
101 of this code (now called mac80211) was delayed for over a year.
/linux-4.4.14/Documentation/isdn/
DREADME.sc164 Upon testing, the following problem was noted, the driver would load without
165 problems, but the board would not respond beyond that point. When a check was
166 done with 'cat /proc/interrupts' the interrupt count for sc was 0. In the event
276 It was noted that in Beta Release 1, the module would fail to load and result
277 in a segmentation fault when 'insmod'ed. This problem was created when one of
278 the isdn4linux parameters, (isdn_ctrl, data field) was filled in. In some
279 cases, this data field was NULL, and was left unchecked, so when it was
DREADME.mISDN3 It was designed to allow a broad range of applications and interfaces
DREADME.x2598 work with every existing HL driver. I was able to successfully open X.25
130 was successful to connect via isdn4linux to an X.25 switch using this
131 trick. At the switch side, a terminal adapter X.21 was used to connect
/linux-4.4.14/fs/exofs/
DBUGS2 were written, but the inode attributes failed. Then if the filesystem was
/linux-4.4.14/Documentation/ABI/removed/
Dip_queue7 module was already announced to become obsolete years ago.
Draw13945 /dev/raw1394 was a character device file that allowed low-level
Dvideo13946 controller, which were used for isochronous I/O. It was added as an
/linux-4.4.14/arch/arc/kernel/
Dentry-arcv2.S128 ; TBD: optimize - do this only if a callee reg was involved
155 ; ECR in pt_regs provides whether access was R/W/X
213 ; entry was via Exception in DS which got preempted in kernel).
Dentry-compact.S184 ; need to check STATUS32_L2 to determine if L1 was active
308 ; TBD: optimize - do this only if a callee reg was involved
385 ; paranoid check, given A1 was active when A2 happened, preempt count
/linux-4.4.14/Documentation/sound/alsa/soc/
Doverview.txt7 subsystem there was some support in the kernel for SoC audio, however it
14 * There was no standard method to signal user initiated audio events (e.g.
22 power on portable devices. There was also no support for saving
/linux-4.4.14/Documentation/w1/masters/
Dds249029 was added to the API. The name is just a suggestion. It would take
58 normally the first time the module was loaded after qemu attached
59 the ds2490 hardware, but if the module was unloaded, then reloaded
/linux-4.4.14/Documentation/vm/
Dksm.txt13 KSM was originally developed for use with KVM (where it was known as
34 and MADV_UNMERGEABLE simply fail with EINVAL. If the running kernel was
39 MADV_UNMERGEABLE is applied to a range which was never MADV_MERGEABLE.
Dslub.txt25 be performed if debugging was not switched on.
98 SLUB can validate all object if the kernel was booted with slub_debug. In
105 This also works in a more limited way if boot was without slab debug.
205 2. The object contents if an object was involved.
210 Shows a few bytes before the object where the problem was detected.
236 The stackdump describes the location where the error was detected. The cause
240 4. Report on how the problem was dealt with in order to ensure the continued
248 been overwritten. Here a string of 8 characters was written into a slab that
Duserfaultfd.txt113 guest (UFFDIO_ZEROCOPY is used if the source page was a zero page).
119 userfault was already resolved and waken by a UFFDIO_COPY|ZEROPAGE run
131 was spontaneously sent by the source or if it was an urgent page
Dactive_mm.txt12 > the task_struct are supposed to be used? (My apologies if this was
55 user exited on another CPU while a lazy user was still active, so you do
/linux-4.4.14/drivers/staging/slicoss/
DREADME7 The driver was actually tested on Oasis and Kalahari cards.
/linux-4.4.14/Documentation/arm/SA1100/
DPLEB1 The PLEB project was started as a student initiative at the School of
DItsy10 The port was done on an Itsy version 1.5 machine with a daughtercard with
31 The serial connection we established was at:
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dssd1289fb.txt7 was described in Documentation/devicetree/bindings/powerpc/fsl/lbc.txt
/linux-4.4.14/arch/m68k/fpsp040/
Dskeleton.S15 | the FPSP was entered. In particular, whatever condition
20 | If the exception was completely handled by the package, then
89 | bug, if an E1 snan, ovfl, or unfl occurred, and the process was
91 | return was inex, rather than the correct exception. The snan, ovfl,
404 | If the EXC_SR shows that the exception was from supervisor space,
Dbugfix.S250 | was exceptional, and was completed by the appropriate handler.
275 | Check if the instruction which just completed was exceptional.
372 | was exceptional, and was completed by the appropriate handler.
401 | Check if the instruction which just completed was exceptional.
Dgen_except.S221 | No exceptions are to be reported. If the instruction was
222 | unimplemented, no FPU restore is necessary. If it was
260 | The caller was from an unsupported data type trap. Test if the
346 | busy frame was created as the result of an exception on the final
/linux-4.4.14/Documentation/timers/
Dhrtimers.txt90 another basic requirement was the immediate enqueueing and ordering of
116 The locking and per-CPU behavior of hrtimers was mostly taken from the
118 was not really a win, due to the different data structures. Also, the
131 CPUs. This build-time-selectable ktime_t storage format was implemented
166 The code was successfully compiled for the following platforms:
170 The code was run-tested on the following platforms:
Dtimer_stats.txt22 - the function where the timer was initialized
65 initialized the timer and in parenthesis the callback function which was
/linux-4.4.14/Documentation/ia64/
Dmca.txt27 * If any slave cpu was already spinning disabled when the MCA occurred
40 * If an MCA/INIT event occurs while the kernel was running (not user
80 failed, not on the task that was originally running. Again this
163 was delivered?
177 How do we identify the tasks that were running when MCA/INIT was
193 'MCA 12159' means that pid 12159 was running when the MCA was
Dserial.txt18 - If there was no HCDP, we assumed there were UARTs at the
131 8250_acpi was replaced by the combination of 8250_pnp and
137 The table was originally defined as the "HCDP" for "Headless
Dfsys.txt69 to by "regs" was executing in user mode (privilege level 3).
70 user_stack() returns TRUE if the state pointed to by "regs" was
72 TRUE if the CPU state pointed to by "regs" was executing in fsys-mode.
170 checks whether the interrupted task was in fsys-mode and, if so, sets
285 __kernel_syscall_via_epc() function for historical reasons (it was
/linux-4.4.14/Documentation/crypto/
Ddescore-readme.txt29 This package was designed with the following goals:
56 since i was interested in fast des filters rather than crypt(3)
89 it's 39%-106% slower. because he was interested in fast crypt(3) and
123 so despite the comments in this code, it was possible to get
141 it was too convoluted, the code had been written without taking
144 it was excessively slow, the author had attempted to clarify the code
147 movement (in particular, his use of L1, R1, L2, R2), and it was full of
153 the fact that this guy was computing 2 sboxes per table lookup rather
155 do the same - it was a trivial change from which i had been scared away
171 one thing i did not want to do was write an enormous mess
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dethernet.txt3 - local-mac-address: array of 6 bytes, specifies the MAC address that was
5 - mac-address: array of 6 bytes, specifies the MAC address that was last used by
/linux-4.4.14/Documentation/input/
Dbcm5974.txt5 The USB initialization and package decoding was made by Scott Shawcroft as
58 The driver was developed at the ubuntu forums in June 2008 [1], and now has
/linux-4.4.14/arch/arm/boot/dts/
Domap3-beagle-xm-ab.dts12 /* HS USB Port 2 Power enable was inverted with the xM C */
Dste-hrefprev60.dtsi62 * On the first generation boards, this SSP/SPI port was connected
/linux-4.4.14/arch/um/kernel/
Dconfig.c.in24 " Prints the config file that this UML binary was generated from.\n\n"
/linux-4.4.14/scripts/ksymoops/
DREADME1 ksymoops has been removed from the kernel. It was always meant to be a
/linux-4.4.14/drivers/staging/dgnc/
DTODO6 * there is a lot of unnecessary code in the driver. It was
/linux-4.4.14/Documentation/cpu-freq/
Dboost.txt75 This switch was instantiated in each CPU's cpufreq directory
76 (/sys/devices/system/cpu[0-9]*/cpufreq) and was called "cpb".
79 which was simply reflected into each CPU's file. Writing a 0 or 1 into it
/linux-4.4.14/Documentation/ABI/stable/
Do2cb1 What: /sys/fs/o2cb/ (was /sys/o2cb)
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-tape.1995-20024 * was successful ! (Using tar cvf ... on the block
52 * ide.c. The hwgroup locking method which was used
53 * in the previous version was removed.
72 * (poll_for_dsc was a complete mess).
135 * MTTELL was sometimes returning incorrect results.
154 * of bytes written to the tape was not an integral
231 * - Module use count was gone in the Linux 2.4 driver.
DChangeLog.ide-floppy.1996-200258 * bit was being deasserted by my IOMEGA ATAPI ZIP 100
59 * drive before the drive was actually ready.
DChangeLog.ide-cd.1994-200447 * when a read-write mount was attempted.
153 * -- Fixed a memory leak where info->changer_info was
162 * -- Fixed a stupid bug which egcs was kind enough to
164 * was never returned due to a comparison on data
250 * tray if it was locked prior to the reset.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Darmada-370-xp-pmsu.txt10 - "marvell,armada-370-xp-pmsu" was used for Armada 370/XP but is now
/linux-4.4.14/Documentation/trace/
Dtracepoint-analysis.txt209 on whether the fragmentation event was severe or moderate.
210 o When receiving an event about a PID, it can record who the parent was so
258 take a slightly different example. In the course of writing this, it was
259 noticed that X was generating an insane amount of page allocations so let's look
267 This was interrupted after a few seconds and
326 ancient build of libpixmap out of the library path where it was totally
Dmmiotrace.txt8 MMIO tracing was originally developed by Intel around 2003 for their Fault
13 Mmiotrace was built for reverse engineering any memory-mapped IO device with
17 Out-of-tree mmiotrace was originally modified for mainline inclusion and
145 data value. Map id is an arbitrary id number identifying the mapping that was
/linux-4.4.14/Documentation/locking/
Dlglock.txt74 was motivated by the presence of multiple lock users and also by them
93 variant (and it seems that the non-static was never in use).
156 3.13 kernel series as was suggested in [3] in 2003. The brlock was
Drt-mutex-design.txt17 decisions that were made to implement PI in the manner that was done.
433 was passed by parameter (for the first iteration). The pi_lock of this task is
473 Note: It is possible that the task was the current top waiter on the mutex,
478 If the task was not the top waiter of the mutex, but it was before we
501 the protection of the mutex's wait_lock, which was not taken yet.
525 What this means is that an owner was chosen by the process releasing the
547 new process is given a mutex that it was blocked on, it is only given
632 mutex actually has waiters, or we clear the flag if it doesn't. See, it was
671 Since the wait_lock was taken at the entry of the slow lock, we can safely
691 2) we received a signal and was TASK_INTERRUPTIBLE
[all …]
Dlockstat.txt55 total - total time this lock was held
56 avg - average time this lock was held
/linux-4.4.14/Documentation/arm/
Dkernel_user_helpers.txt143 Return zero if *ptr was changed or non-zero if no exchange happened.
144 The C flag is also set if *ptr was changed to allow for assembly
235 is equal to the 64-bit value pointed by *oldval. Return zero if *ptr was
238 The C flag is also set if *ptr was changed to allow for assembly
DREADME136 RiscOS gets; but it's a heck of a lot better than the 50K/s I was getting
154 A change was made in 2003 to the macro names for new machines.
155 Historically, CONFIG_ARCH_ was used for the bonafide architecture,
157 e.g. Assabet. It was decided to change the implementation macros
/linux-4.4.14/Documentation/video4linux/
Dcafe_ccic3 and this driver was written with support from the OLPC project.
42 ten. That number was carefully picked out of a hat and should not be
Dradiotrack.txt9 This document was made based on 'C' code for Linux from Gideon le Grange
15 Lab (http://www.aimslab.com/) RadioTrack card was made available to the
23 running the card, and found that it was good! Frans Brinkman made a
DZoran190 was introduced in 1997, is used in the BUZ and
194 was introduced in 1995, is used in the Pinnacle/Miro DC10(new), DC10+ and
198 was introduced in 2000, is used in the LML33R10 and
202 was introduced in 1996, and is used in the LML33 and
206 was introduced in 1996, is used in the DC30 and DC30+ and
223 was introduced in 1996, is used in the BUZ
227 was introduced in 1994, is used in the LML33
231 was introduced in 2000, is used in the LML300R10
235 was introduced in 1996, is used in the DC10, DC10+, DC10 old, DC30, DC30+
239 was introduced in 1991, is used in the DC10 old
DREADME.cpia214 contains usb specific functions. The main reason for this was the size of the
15 module was getting out of hand, so I separated them. It is not likely that
130 this one was modelled from.
/linux-4.4.14/arch/alpha/lib/
Dstrncat.S59 zapnot $1, $27, $2 # was last byte a null?
Dev67-strncat.S61 zapnot $1, $27, $2 # U : was last byte a null?
/linux-4.4.14/Documentation/RCU/
Drculist_nulls.txt75 from a chain, and inserted into another chain. If new chain was empty
121 the beginning. If the object was moved to the same chain,
144 * We probably met an item that was moved to another chain.
Dtrace.txt175 this CPU. This will always be zero unless the kernel was built
177 parameter was specified.
400 o "qsp" is the number of times that the RCU was waiting for a
411 grace period while RCU was idle.
414 completed, but this CPU was not yet aware of it.
417 but this CPU was not yet aware of it.
485 that was blocking both an expedited and a normal grace period,
497 other words, we balked) even though it was time to boost because
510 was at least one task blocking the current non-expedited grace
514 o "ny" counts the number of times we balked because it was
Dlockdep.txt84 from taking place. If the above statement was invoked only from updater
92 complain if this was used in an RCU read-side critical section unless one
Dlockdep-splat.txt1 Lockdep-RCU was added to the Linux kernel in early 2010
79 code was invoked either from within an RCU read-side critical section
Dstallwarn.txt64 This message indicates that CPU 5 detected that it was causing a stall,
65 and that the stall was affecting RCU-sched. This message will normally be
78 causing stalls, and that the stall was affecting RCU-bh. This message
112 grace period. If the CPU was not yet aware of the current grace
113 period (for example, if it was offline), then this part of the message
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dpwm-clock.txt17 is not exact but was rounded to nanoseconds.
/linux-4.4.14/net/ieee802154/
DKconfig5 complexity short range wireless personal area networks. It was
/linux-4.4.14/drivers/net/
DLICENSE.SRC11 This software was developed at SRC for use in internal research, and the
/linux-4.4.14/arch/openrisc/
DTODO.openrisc12 which was an older name for the architecture. The name we've settled on is
/linux-4.4.14/Documentation/device-mapper/
Dera.txt65 snapshot was the primary use case when developing this target:
81 - Ascertain which blocks have been written since the snapshot was taken
/linux-4.4.14/Documentation/sound/alsa/
DJoystick.txt31 was a dynamic control API for the joystick activation. It was
Dcompress_offload.txt8 Since its early days, the ALSA API was defined with PCM support or
25 The design of this API was inspired by the 2-year experience with the
136 Note that the list of codecs/profiles/modes was derived from the
210 manner, no matter if the input was PCM or compressed.
/linux-4.4.14/Documentation/x86/
Dexception-tables.txt8 In older versions of Linux this was done with the
13 'addr' and of size 'size' was accessible for the operation specified
16 normal case (correctly working program), this test was successful.
40 was not swapped in, write protected or something similar. However,
283 get_user macro actually returns a value: 0, if the user access was
/linux-4.4.14/net/mpls/
DKconfig11 hardware speeds (before hardware was capable of routing ipv4 packets),
/linux-4.4.14/Documentation/power/
Dtricks.txt26 When you make it work, try to find out what exactly was it that broke
Druntime_pm.txt237 - if set, there was a fatal error (one of the callbacks returned error code
293 function was last called for this device; used in calculating inactivity
318 success, 1 if the device's runtime PM status was already 'suspended', or
331 success, 1 if the device's runtime PM status was already 'active' or
352 runtime status was already 'suspended', or error code if the request
360 success, 1 if the device's runtime PM status was already 'active', or
404 field was previously zero, this prevents subsystem-level runtime PM
407 canceled; returns 1 if there was a resume request pending and it was
415 complete; returns 1 if there was a resume request pending and it was
468 - return true if power.irq_safe flag was set for the device, causing
[all …]
/linux-4.4.14/arch/sh/lib/
Dchecksum.S81 add #2, r5 ! r5 was < 2. Deal with it.
165 ! Check if the buffer was misaligned, if so realign sum
236 add #2,r6 ! r6 was < 2. Deal with it.
/linux-4.4.14/arch/arm/vfp/
Dvfphw.S107 @ state if there was a previous (valid) owner.
139 @ Check this by looking at the CPU number which the state was
/linux-4.4.14/arch/m68k/ifpsp060/src/
Dpfpsp.S965 # no underflow was called for. We do these checks only in
970 # and inexact. and, the inexact is such that overflow occurred and was disabled
971 # but inexact was enabled.
1354 # branch to _real_inex() (even if the result was exact!);
1360 btst &ovfl_bit,FPSR_EXCEPT(%a6) # was overflow set?
1364 btst &inex2_bit,FPCR_ENABLE(%a6) # was inexact enabled?
1369 # An exception occurred and that exception was enabled:
1388 # the enabled exception was inexact
1425 # If the input operand to this operation was opclass two and a single
1560 # it here. if it was used from supervisor mode, then we have to handle this
[all …]
/linux-4.4.14/fs/minix/
DKconfig7 partition or a floppy disk) was the original file system for Linux,
/linux-4.4.14/arch/arc/mm/
Dtlbex.S332 ; Let Linux VM know that the page was accessed
387 ; UPDATE_PTE: Let Linux VM know that page was accessed/dirty
390 btst_s r3, ECR_C_BIT_DTLB_ST_MISS ; See if it was a Write Access ?
/linux-4.4.14/fs/hfsplus/
DKconfig10 This file system is often called HFS+ and was introduced with
/linux-4.4.14/Documentation/kbuild/
DKconfig.select-break9 # currently a feature of kconfig, given select was designed to be heavy handed.
/linux-4.4.14/Documentation/security/
DYama.txt16 (e.g. Pidgin) was compromised, it would be possible for an attacker to
69 The original children-only logic was based on the restrictions in grsecurity.
/linux-4.4.14/drivers/mtd/devices/
DKconfig19 "slide" the window around the PMC551's memory. This was
21 was limited kernel space to deal with.
44 backed-up NVRAM module. The module was originally meant as an NFS
68 device thinks the write was successful, a bit could have been
/linux-4.4.14/Documentation/powerpc/
Deeh-pci-error-recovery.txt36 EEH was originally designed to guard against hardware failure, such
73 This value was chosen because it is the same value you would
74 get if the device was physically unplugged from the slot.
150 error was detected, as the error itself usually occurs slightly
289 trigger any user-space daemon that was watching /sysfs,
305 card was being rebooted.
Dhvcs.txt44 This device driver was written using 2.6.4 Linux kernel APIs and will only
47 This driver was written to operate solely on IBM Power5 ppc64 hardware
48 though some care was taken to abstract the architecture dependent firmware
274 connection was severed to fetch the data from firmware before the fetch is
306 read '0' or if any value other than '0' was written to the vterm_state
343 completed or was never executed.
408 Information on the "vterm_state" attribute was covered earlier on the
530 and vty-server coupling changing if a vty-server adapter was added in a
/linux-4.4.14/Documentation/cdrom/
Dide-cd186 lilo option. See Documentation/ide/ide.txt. (This feature was
229 it was expecting one (on any feasible IRQ). If <n> is negative,
231 it was expecting to receive just one from the CDROM drive.
240 had one report of a system which was shipped with IRQ 15 disabled
321 - There was a bug in the version of the driver in 1.2.x kernels
322 which could cause this. It was fixed in 1.3.0. If you can't
333 - Random data corruption was occasionally observed with the Hitachi
350 * or no slot was specified.
/linux-4.4.14/Documentation/filesystems/caching/
Dbackend-api.txt270 This method is called to ask the cache to release any resources it was
462 If there was an error such as -ENOMEM, then that should be returned; else
501 This is called to write from a page on which there was a previously
658 produced a positive result, or that an object was created. This should
679 (*) Indicate that a stale object was found and discarded:
684 the cache that the netfs decided was stale. The object has been
696 FSCACHE_OBJECT_IS_STALE - the object was stale and needs discarding.
697 FSCACHE_OBJECT_NO_SPACE - there was insufficient cache space
698 FSCACHE_OBJECT_WAS_RETIRED - the object was retired when relinquished.
699 FSCACHE_OBJECT_WAS_CULLED - the object was culled to make space.
Dobject.txt130 The work to be done by the various states was given CPU time by the threads of
131 the slow work facility. This was used in preference to the workqueue facility
253 The object comes to this state if it was waiting on its parent in
307 These are signalled when the netfs relinquishes a cookie it was using.
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-dsp-keystone.txt13 - reading pin value returns 0 - if IRQ was handled or 1 - IRQ is still
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dccf.txt19 is retained for compatibility reasons, as it was already
/linux-4.4.14/arch/arm/nwfpe/
Dentry.S94 cmp r0, #0 @ was emulation successful
DChangeLog46 as a struct user_fp (see user.h). This pointer was cast to a
58 * Second I noticed resetFPA11 was not always being called for a
Dsoftfloat-specialize8 Written by John R. Hauser. This work was made possible in part by the
10 Street, Berkeley, California 94704. Funding was partially provided by the
12 of this code was written as part of a project to build a fixed-point vector
/linux-4.4.14/Documentation/virtual/
Dparavirt_ops.txt6 different hypervisors, this restriction was removed with pv_ops.
/linux-4.4.14/Documentation/tpm/
Dxen-tpmfront.txt23 This mini-os vTPM subsystem was built on top of the previous vTPM work done by
104 Support for the vTPM driver was added in Xen using the libxl toolstack in Xen
/linux-4.4.14/Documentation/namespaces/
Dcompatibility-list.txt25 within the namespace it was obtained in and may refer to some
/linux-4.4.14/tools/testing/ktest/examples/
DREADME22 snowball.conf - An example config that was used to demo ktest.pl against
/linux-4.4.14/fs/jffs2/
DREADME.Locking28 was written afterwards. Hence, we can ensure the newly-obsoleted nodes
52 node belonging to the inode which was locked in the first place by the
131 heavyweight lock was required to prevent the erase code from freeing
/linux-4.4.14/Documentation/virtual/kvm/
Dcpuid.txt21 be interpreted as if the value was 0x40000001.
/linux-4.4.14/net/dccp/
DKconfig49 what was just said, you don't need it: say N.
/linux-4.4.14/net/decnet/
DKconfig7 The DECnet networking protocol was used in many products made by
/linux-4.4.14/Documentation/fb/
Dcirrusfb.txt57 called 'palette' instead of from the VGA registers. This code was
/linux-4.4.14/net/dccp/ccids/
DKconfig33 This text was extracted from RFC 4340 (sec. 10.2),
/linux-4.4.14/arch/m32r/lib/
Dchecksum.S76 .fillinsn ; len(r1) was < 2. Deal with it.
193 addi r1, #2 ; len(r1) was < 2. Deal with it.
/linux-4.4.14/Documentation/frv/
Datomic-ops.txt97 was set to True.
105 Such that the branch can then be taken if the operation was aborted.
/linux-4.4.14/Documentation/nvmem/
Dnvmem.txt18 This was also a problem as far as other in-kernel users were involved, since
20 was a rather big abstraction leak.
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-memory.txt6 Warning! This information was figured out from searching through the memory and
8 was not derived from anything more than searching through the memory space with
/linux-4.4.14/Documentation/devicetree/
Dusage-model.txt36 binding was created without first investigating how i2c devices were
41 The DT was originally created by Open Firmware as part of the
53 and 64-bit support, the decision was made to require DT support on all
56 Tree (FDT) was created which could be passed to the kernel as a binary
59 Device Tree Binary (dtb) and to modify a dtb at boot time. DT was
64 Some time later, FDT infrastructure was generalized to be usable by
167 "ti,omap3450". If a bug was discovered on the original beagleboard
/linux-4.4.14/arch/x86/kernel/
Dverify_cpu.S98 jnc verify_cpu_check # only write MSR if bit was changed
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.WINVIEW17 hardware. The driver was written by visual inspection of the card. If you
/linux-4.4.14/Documentation/sound/oss/
DOpti7 added to the sound driver after Linux-2.1.91 was out.
58 This was tested with isapnptools-1.11 but I recommend that you use
153 and if a cdrom was already mounted it may cause a complete
/linux-4.4.14/arch/cris/arch-v32/mach-a3/
Ddram_init.S22 ;; information from the decompressor (if the kernel was compressed).
/linux-4.4.14/drivers/fmc/
DKconfig15 The framework was born outside of the kernel and at this time
/linux-4.4.14/Documentation/parisc/
Ddebugging34 was interrupted - so if you get an interruption between the instruction

1234