Home
last modified time | relevance | path

Searched refs:calls (Results 1 – 200 of 427) sorted by relevance

123

/linux-4.4.14/arch/powerpc/platforms/cell/
Dspu_syscalls.c39 struct spufs_calls *calls = NULL; in spufs_calls_get() local
42 calls = rcu_dereference(spufs_calls); in spufs_calls_get()
43 if (calls && !try_module_get(calls->owner)) in spufs_calls_get()
44 calls = NULL; in spufs_calls_get()
47 return calls; in spufs_calls_get()
50 static inline void spufs_calls_put(struct spufs_calls *calls) in spufs_calls_put() argument
52 BUG_ON(calls != spufs_calls); in spufs_calls_put()
65 static inline void spufs_calls_put(struct spufs_calls *calls) { } in spufs_calls_put() argument
73 struct spufs_calls *calls; in SYSCALL_DEFINE4() local
75 calls = spufs_calls_get(); in SYSCALL_DEFINE4()
[all …]
/linux-4.4.14/drivers/misc/cxl/
Dbase.c26 struct cxl_calls *calls = NULL; in cxl_calls_get() local
29 calls = rcu_dereference(cxl_calls); in cxl_calls_get()
30 if (calls && !try_module_get(calls->owner)) in cxl_calls_get()
31 calls = NULL; in cxl_calls_get()
34 return calls; in cxl_calls_get()
37 static inline void cxl_calls_put(struct cxl_calls *calls) in cxl_calls_put() argument
39 BUG_ON(calls != cxl_calls); in cxl_calls_put()
52 static inline void cxl_calls_put(struct cxl_calls *calls) { } in cxl_calls_put() argument
58 struct cxl_calls *calls; in cxl_slbia() local
60 calls = cxl_calls_get(); in cxl_slbia()
[all …]
Dcxl.h638 int register_cxl_calls(struct cxl_calls *calls);
639 void unregister_cxl_calls(struct cxl_calls *calls);
/linux-4.4.14/net/ax25/
Dax25_addr.c149 if (ax25cmp(&digi1->calls[i], &digi2->calls[i]) != 0) in ax25digicmp()
197 memcpy(&digi->calls[d], buf, AX25_ADDR_LEN); in ax25_addr_parse()
256 memcpy(buf, &d->calls[ct], AX25_ADDR_LEN); in ax25_addr_build()
296 out->calls[ct] = in->calls[in->ndigi - ct - 1]; in ax25_digi_invert()
299 out->calls[ct].ax25_call[6] |= AX25_HBIT; in ax25_digi_invert()
302 out->calls[ct].ax25_call[6] &= ~AX25_HBIT; in ax25_digi_invert()
Dax25_route.c103 ax25_rt->digipeat->calls[i] = route->digi_addr[i]; in ax25_rt_add()
132 ax25_rt->digipeat->calls[i] = route->digi_addr[i]; in ax25_rt_add()
319 ax2asc(buf, &ax25_rt->digipeat->calls[i])); in ax25_rt_seq_show()
400 if (ax25cmp(addr, &digipeat->calls[k]) == 0) in ax25_adjust_path()
Daf_ax25.c371 digi.calls[k] = ax25_ctl.digi_addr[k]; in ax25_ctl_ioctl()
1203 digi->calls[ct] = fsa->fsa_digipeater[ct]; in ax25_connect()
1416 ax25->digipeat->calls[i]; in ax25_getname()
1510 dtmp.calls[ct] = fsa->fsa_digipeater[ct]; in ax25_sendmsg()
1661 fsa->fsa_digipeater[ct] = digi.calls[ct]; in ax25_recvmsg()
1892 ax2asc(buf, &ax25->digipeat->calls[k]), in ax25_info_show()
Dax25_in.c216 next_digi = &dp.calls[dp.lastrepeat + 1]; in ax25_rcv()
/linux-4.4.14/Documentation/ioctl/
D00-INDEX6 - summary of CDROM ioctl calls
8 - summary of HDIO_ ioctl calls
12 - how to implement and register device/driver ioctl calls
Dcdrom.txt1 Summary of CDROM ioctl calls.
8 This document attempts to describe the ioctl(2) calls supported by
81 Unless otherwise specified, all ioctl calls return 0 on success
85 Unless otherwise specified, all ioctl calls return -1 and set
/linux-4.4.14/arch/m68k/include/asm/
Dfloppy.h191 static int calls=0; in floppy_hardint() local
201 if(!calls) in floppy_hardint()
229 calls++; in floppy_hardint()
238 virtual_dma_count, virtual_dma_residue, calls, bytes, in floppy_hardint()
240 calls = 0; in floppy_hardint()
Dsun3xflop.h121 static int calls=0; in sun3xflop_hardint() local
133 if(!calls) in sun3xflop_hardint()
172 calls++; in sun3xflop_hardint()
184 virtual_dma_count, virtual_dma_residue, calls, bytes, in sun3xflop_hardint()
186 calls = 0; in sun3xflop_hardint()
/linux-4.4.14/Documentation/powerpc/
Deeh-pci-error-recovery.txt174 It saves the device BAR's and then calls rpaphp_unconfig_pci_adapter().
181 any bridges underneath. It then calls rpaphp_enable_pci_slot(),
198 calls
201 calls
204 calls
207 calls
210 calls
213 calls
216 calls
220 calls
[all …]
/linux-4.4.14/scripts/
Dchecksyscalls.sh71 /* System calls for 32-bit kernels only */
102 /* i386-specific or historical system calls */
173 /* these can be expressed using other calls */
/linux-4.4.14/arch/parisc/include/asm/
Dfloppy.h72 static int calls=0; in floppy_hardint() local
82 if(!calls) in floppy_hardint()
107 calls++; in floppy_hardint()
116 virtual_dma_count, virtual_dma_residue, calls, bytes, in floppy_hardint()
118 calls = 0; in floppy_hardint()
/linux-4.4.14/Documentation/i2c/
Ddev-interface89 the means of read() and write() calls. In particular, so-called combined
143 You can do plain i2c transactions by using read(2) and write(2) calls.
166 The above functions are all inline functions, that resolve to calls to
167 the i2c_smbus_access function, that on its turn calls a specific ioctl
178 1* Your program opens /dev/i2c-N and calls ioctl() on it, as described in
181 2* These open() and ioctl() calls are handled by the i2c-dev kernel
186 3* Some ioctl() calls are for administrative tasks and are handled by
191 4* Other ioctl() calls are converted to in-kernel function calls by
198 difference between these calls that came from user-space through i2c-dev
199 and calls that would have been performed by kernel I2C chip drivers
[all …]
Dwriting-clients285 These are standard driver model calls, and they work just like they
286 would for any other driver stack. The calls can sleep, and can use
288 parent I2C adapter is active when these calls are issued, and IRQs
300 would for any other driver stack: the calls can sleep, and can use
/linux-4.4.14/arch/x86/include/asm/
Dfloppy.h61 static int calls; in floppy_hardint() local
69 if (!calls) in floppy_hardint()
94 calls++; in floppy_hardint()
103 virtual_dma_count, virtual_dma_residue, calls, bytes, in floppy_hardint()
105 calls = 0; in floppy_hardint()
/linux-4.4.14/arch/tile/
DKconfig.debug18 bool "Provide wrapper functions for hypervisor ABI calls"
21 Provide wrapper functions for the hypervisor ABI calls
23 mechanisms, etc., to have visibility into those calls.
/linux-4.4.14/arch/arc/
DMakefile84 KBUILD_CFLAGS_MODULE += -mlong-calls -mno-millicode
136 export CFLAGS_decompress_inflate.o = -mmedium-calls
137 export CFLAGS_initramfs.o = -mmedium-calls
139 export CFLAGS_core.o = -mmedium-calls
/linux-4.4.14/tools/perf/scripts/python/bin/
Dexport-to-postgresql-report19 calls=$3
29 perf script $@ -s "$PERF_EXEC_PATH"/scripts/python/export-to-postgresql.py $dbname $columns $calls
/linux-4.4.14/scripts/tracing/
Ddraw_functrace.py44 def calls(self, func, calltime): member in CallTree
63 child = CallTree.ROOT.calls(func, None)
124 tree = tree.calls(callee, calltime)
/linux-4.4.14/Documentation/infiniband/
Dcore_locking.txt54 if multiple function calls using the same object are run
57 The IB midlayer does not perform any serialization of function calls.
64 information between different calls of ib_poll_cq() is not defined.
100 consumers when it calls ib_register_device(), all initialization
106 semaphores that could cause deadlock if a consumer calls back into
107 the driver across these calls.
Duser_verbs.txt48 get_user_pages() and put_page() calls. It also accounts for the
Dipoib.txt60 on/off using ethtool calls. Currently LRO is supported only for
/linux-4.4.14/Documentation/serial/
Dtty.txt57 No further calls into the ldisc code will occur.
61 the line. Multiple read calls may occur in parallel
67 line. Multiple write calls are serialized by the
85 calls. Multiple poll calls may occur in parallel.
90 ioctl calls may occur in parallel. May sleep.
94 Multiple ioctl calls may occur in parallel.
114 is needed but always races versus calls. Thus the
116 handle unexpected calls. Must not sleep.
212 calls on the tty to fail, returning -EIO.
223 take line discipline locks. The same is true of calls from the driver side
[all …]
Dserial-rs485.txt37 serial_core calls rs485_config to do the device specific part in response
/linux-4.4.14/arch/mn10300/kernel/
Dswitch_to.S105 calls flush_icache_range
119 calls flush_icache_range
152 calls flush_icache_range
167 calls flush_icache_range
Dentry.S62 calls (a0)
87 calls (a0)
393 calls (a2)
/linux-4.4.14/Documentation/prctl/
Dseccomp_filter.txt7 A large number of system calls are exposed to every userland process
9 As system calls change and mature, bugs are found and eradicated. A
11 of available system calls. The resulting set reduces the total kernel
16 incoming system calls. The filter is expressed as a Berkeley Packet
20 filtering of system calls using a filter program language with a long
39 system calls in socketcall() is allowed, for instance) which could be
185 The vDSO can cause some system calls to run entirely in userspace,
193 legacy variants on vDSO calls.) Currently, emulated vsyscalls will honor seccomp, with a few oddit…
219 instructions at 0xF...F600{0,4,8,C}00 will not be system calls in these
224 syscalls. New code will use the vDSO, and vDSO-issued system calls
[all …]
/linux-4.4.14/Documentation/arm/
Dkernel_mode_neon.txt10 * Put kernel_neon_begin() and kernel_neon_end() calls around the calls into your
59 If latency is a concern, it is possible to put back to back calls to
61 the NEON registers are live. (Additional calls to kernel_neon_begin() should be
82 between calls to these respective functions. Furthermore, GCC may generate NEON
91 * issue the calls to kernel_neon_begin(), kernel_neon_end() as well as the calls
Dfirmware.txt27 the macro checks if the operation is provided and calls it or otherwise returns
/linux-4.4.14/arch/c6x/
DMakefile13 cflags-$(CONFIG_C6X_BIG_KERNEL) += -mlong-calls
15 CFLAGS_MODULE += -mlong-calls -mno-dsbt -msdata=none
DKconfig45 for function calls. Use this option to have the compiler generate
46 function calls with 32-bit range. This will make the kernel both
/linux-4.4.14/Documentation/security/
Dkeys-request-key.txt51 The request_key*_with_auxdata() calls are like the in-kernel request_key*()
52 calls, except that they permit auxiliary data to be passed to the upcaller (the
56 The two async in-kernel calls may return keys that are still in the process of
76 (1) Process A calls request_key() [the userspace syscall calls the kernel
155 firstly calls key_permission(SEARCH) on the keyring it's starting with,
159 matches the criteria specified, calls key_permission(SEARCH) on it to see
165 searching. It calls key_permission(SEARCH) on each keyring, and if this
DIMA-templates.txt43 a given template but, instead, it simply calls the init() method of the template
/linux-4.4.14/arch/sparc/kernel/
Dtraps_32.c225 static int calls; local
295 calls++;
296 if(calls > 2)
325 if(calls > 0)
326 calls=0;
/linux-4.4.14/Documentation/
Dadding-syscalls.txt13 the alternatives might be suitable instead. Although system calls are the
57 together with the corresponding follow-up system calls -- eventfd/eventfd2,
61 For simpler system calls that only take a couple of arguments, the preferred
72 For more sophisticated system calls that involve a larger number of arguments,
117 what it means to use the poll(2) family of system calls on that file
138 (For more details on the rationale of the *at() calls, see the openat(2) man
169 To make new system calls easy to review, it's best to divide up the patchset
199 calls are invoked:
212 note that if multiple new system calls are added in the same merge window,
262 For most system calls the same 64-bit implementation can be invoked even when
[all …]
Dhighuid.txt26 - Need to validate that OS emulation calls the 16-bit UID
28 uses the 32-bit UID system calls properly otherwise.
34 (need to support whatever new 32-bit UID system calls are added to
Dfutex-requeue-pi.txt23 Consider the simplified glibc calls:
81 necessary changes inside the existing calls rather than creating new
82 calls for the PI cases. Similar changes are needed for
100 Two new system calls provide the kernel<->user interface to
Dphy.txt97 consumer calls on the NULL phy become NOPs. That is the release calls,
98 the phy_init() and phy_exit() calls, and phy_power_on() and
99 phy_power_off() calls are all NOP when applied to a NULL phy. The NULL
130 device created by this subsystem will be a child of the device that calls
Ddma-buf-sharing.txt181 This API removes the attachment from the list in dmabuf, and optionally calls
192 operation related to this fd is called. It calls the dmabuf->ops->release()
197 The attach-detach calls allow the exporter to figure out backing-storage
300 dma_buf kmap calls outside of the range specified in begin_cpu_access are
305 Note that these calls need to always succeed. The exporter needs to complete
318 the dma-buf layer keeps a reference count for all vmap access and calls down
320 unmaps it once. Protection against concurrent vmap/vunmap calls is provided
327 unpinning of any pinned resources). The result of any dma_buf kmap calls
356 No special interfaces, userspace simply calls mmap on the dma-buf fd.
Dpercpu-rw-semaphore.txt14 writing is very expensive, it calls synchronize_rcu() that can take
DIntel-IOMMU.txt38 Well behaved drivers call pci_map_*() calls before sending command to device
40 required, device performs a pci_unmap_*() calls to unmap the region.
Dhw_random.txt24 and read() system calls, you can read random data from
71 request_mem_region calls always fail for proper setups.
Dclk.txt245 The enable lock is a spinlock and is held across calls to the .enable,
247 sleep, and calls to the clk_enable(), clk_disable() and clk_is_enabled() API
250 The prepare lock is a mutex and is held across calls to all other operations.
251 All those operations are allowed to sleep, and calls to the corresponding API
Dkernel-per-CPU-kthreads.txt70 is non-idle, for example, by avoiding system calls and by forcing
102 calls to things like tasklet_schedule().)
120 is non-idle, for example, by avoiding system calls and by
126 is non-idle. For example, avoid system calls and force both
145 calls and by forcing both kernel threads and interrupts
157 calls and by forcing both kernel threads and interrupts
Dkprobes.txt93 calls jprobe_return(), which traps again to restore the original stack
119 handler calls the user-specified return handler associated with the
209 - a call to the trampoline code which calls user's probe handlers.
236 rather, it calls synchronize_sched() for safety first, because it's
243 After that, the Kprobe-optimizer calls stop_machine() to replace
339 hit, Kprobes calls kp->pre_handler. After the probed instruction
340 is single-stepped, Kprobe calls kp->post_handler. If a fault
342 or during single-stepping of the probed instruction, Kprobes calls
422 rp->kp.addr. When that function returns, Kprobes calls rp->handler.
567 address with the trampoline's address, stack backtraces and calls
Dmen-chameleon-bus.txt68 device provides callback methods to translate the driver's MCB function calls
69 to hardware related function calls. For example a carrier device may
Dpreempt-locking.txt90 small, atomic code that you wrote and which calls no complex functions.
133 be made. Do note that calls from interrupt context or bottom half/ tasklets
Dirqflags-tracing.txt30 - in lowlevel entry code add (build-conditional) calls to the
Dmedia-framework.txt298 When a link is enabled or disabled, the media framework calls the
336 be identical for all nested calls to the function.
345 If multiple calls to media_entity_pipeline_start() have been made the same
346 number of media_entity_pipeline_stop() calls are required to stop streaming. The
Dkasan.txt165 function calls (__asan_load*(addr), __asan_store*(addr)) before each memory
170 function calls GCC directly inserts the code to check the shadow memory.
Dpadata.txt87 Padata calls the notifier chain with:
129 fact that the workqueue is used to make these calls, parallel() is run with
Dio-mapping.txt69 On 64-bit processors, io_mapping_create_wc calls ioremap_wc for the whole
/linux-4.4.14/Documentation/arm/Samsung/
DGPIO.txt8 specific calls provided alongside the drivers/gpio core.
23 specific calls for the items that require Samsung specific handling, such
/linux-4.4.14/tools/perf/Documentation/
Dperf-bench.txt195 Suite for evaluating wake calls.
198 Suite for evaluating parallel wake calls.
201 Suite for evaluating requeue calls.
204 Suite for evaluating futex lock_pi calls.
Ditrace.txt3 c synthesize branches events (calls only)
DBuild.txt14 top level Makefile working as a wrapper that calls the main
Dintel-bts.txt13 code is still needed to pair up calls and returns correctly, consequently much
Dperf-script-perl.txt47 available as calls back into the perf executable (see below).
96 $context an opaque 'cookie' used in calls back into perf
/linux-4.4.14/Documentation/virtual/kvm/
Ds390-diag.txt15 DIAGNOSE calls by the guest cause a mandatory intercept. This implies
16 all supported DIAGNOSE calls need to be handled by either KVM or its
19 All DIAGNOSE calls supported by KVM use the RS-a format:
/linux-4.4.14/Documentation/usb/
Ddma.txt15 - New calls enable DMA-aware drivers, letting them allocate dma buffers and
106 It's probably easier to use the new usb_sg_*() calls, which do the DMA
115 These calls all work with initialized urbs: urb->dev, urb->pipe,
117 valid when these calls are used (urb->setup_packet must be valid too
126 The calls manage urb->transfer_dma for you, and set URB_NO_TRANSFER_DMA_MAP
132 calls (where the underlying DMA primitives have changed), most of them can
Ddwc3.txt23 goes through every event and calls generic_handle_irq() for event
Dpower-management.txt398 The simplest usage pattern is that a driver calls
464 External suspend calls should never be allowed to fail in this way,
465 only autosuspend calls. The driver can tell them apart by applying
477 suspend/resume events are mutually exclusive with calls to probe,
481 If a driver wants to block all suspend/resume calls during some
485 external PM calls, and the usb_autopm_get_interface() will prevent any
486 internal PM calls, even if it fails. (Exercise: Why?)
562 method calls to set the port power state. For more background see the
/linux-4.4.14/Documentation/isdn/
DREADME.diversion45 only supported by isdn phones. Incoming calls may be diverted
49 as normally done by isdn phones. In this case all incoming calls
56 In this case all incoming calls are checked by rules that may be
62 matches to all filtered calls or only those when all B-channel resources
66 All incoming calls matching a rule except the ignore rule a reported and
116 your network incoming calls and reactions by the module may be shown on
DREADME.gigaset120 The devices accept the following device specific ioctl calls
246 ISDN calls. Their use can be enabled ("CID mode") or disabled ("Unimodem
249 does not signal incoming calls or other base events.
259 - If you want to receive incoming calls, you can use the default
277 Internal calls can be made by providing an internal extension number
280 number. Dialing "***" (three asterisks) calls all extensions
284 does not support internal calls.
DREADME.audio87 On incoming calls, if the application responds to a RING
91 On outgoing voice calls, the emulator responds with VCON
DREADME254 bit. In this case, on incoming calls
259 of register 14. On outgoing calls,
288 calls and are NOT assigned to a specific tty or network interface.
365 f) Set the number for outgoing calls on the interface:
369 and the number(s) for incoming calls:
409 Then all incoming calls are logged, even if they are not addressed
426 Only incoming calls, for which the caller-id is listed in the access
446 Switch the hang-up-timer for incoming calls on or off.
535 If switched on, isdn4linux replies a REJECT to incoming calls, it
DINTERFACE.CAPI48 driver has to call capi_ctr_down(). This will prevent further calls to the
54 Kernel CAPI forwards registration requests from applications (calls to CAPI
62 application may be passed to the driver for the device via calls to the
68 forwarded as calls to the release_appl() callback function, passing the same
DINTERFACE225 This command is intended for performing ioctl-calls for configuring
227 etc.) For this purpose, in the LL all ioctl-calls with an argument
231 If a userlevel-program calls ioctl(0x101,...) the function gets
303 calls to the LL.
313 With this command, the HL-driver is told to signal incoming calls for
322 HL-driver should respond to ALL incoming calls,
340 calls with the given Service-Indicators.
/linux-4.4.14/Documentation/filesystems/
Dmandatory-locking.txt32 processes. File locks are applied using the flock() and fcntl() system calls
89 All the reference systems reject all calls to open() for a file on which
91 contravention of SVID 3, which states that only calls to open() with the
93 definition, which is the "Right Thing", since only calls with O_TRUNC can
146 5. Which system calls are affected?
155 for the total number of bytes read or written. For the truncate calls it is
160 Note 3: I may have overlooked some system calls that need mandatory lock
162 better still fix the system calls yourself and submit a patch to me or Linus.
Dinotify.txt75 device file or a family of new system calls. We decided to implement a
76 family of system calls because that is the preferred approach for new kernel
78 and ioctl(2) or a couple of new system calls. System calls beat ioctls.
Ddlmfs.txt62 Users may access dlmfs via standard file system calls, or they can use
64 system calls and presents a more traditional locking api.
Dvfs.txt23 VFS system calls open(2), stat(2), read(2), write(2), chmod(2) and so
32 calls. The pathname argument that is passed to them is used by the VFS
57 To look up an inode requires that the VFS calls the lookup() method of
316 Implementations must include conditional reschedule calls inside any
373 create: called by the open(2) and creat(2) system calls. Only
387 calls like create(2), mknod(2), mkdir(2) and so on will fail.
463 is called by chmod(2) and related system calls.
466 is called by stat(2) and related system calls.
545 cause various VM routines to make extra calls into the address_space
844 read: called by read(2) and related system calls
[all …]
Dseq_file.txt168 the programmer is aware that things can happen between calls to the
170 between the calls to start() and stop(), so holding a lock during that time
210 and avoid further seq_<output> calls if true is returned.
328 calls:
Dsysfs.txt124 set of sysfs operations for forwarding read and write calls to the
136 When a file is read or written, sysfs calls the appropriate method
139 calls the associated methods.
Dcoda.txt92 2. Servicing Coda filesystem calls
160 client cache and makes remote procedure calls to Coda file servers and
173 describe the semantic invariants resulting from the calls.
198 traps to the OS kernel. Examples of such calls trapping to the kernel
200 context. Similar calls exist in the Win32 environment, and are named
215 First and foremost the VFS must be able to make all necessary calls to
259 not go into the calls exported to the VFS layer but we will state the
311 namely when Venus calls sendmsg_to_kernel. At this moment the Coda FS
414 Before delving into the specific calls we need to discuss a variety of
550 We now proceed to document the individual calls:
[all …]
Dautomount-support.txt60 The expiration flag is cleared by calls to mntput. This means that expiration
Ddax.txt74 calls to get_block() (for example by a page-fault racing with a read()
/linux-4.4.14/net/decnet/
DTODO21 send/recvmsg() calls should simply be a vector of set/getsockopt()
22 calls]
/linux-4.4.14/arch/s390/kernel/
DMakefile21 CFLAGS_stacktrace.o += -fno-optimize-sibling-calls
22 CFLAGS_dumpstack.o += -fno-optimize-sibling-calls
/linux-4.4.14/Documentation/gpio/
Dgpio-legacy.txt5 These calls use the gpio_* naming prefix. No other calls should use that
77 standard GPIO calls should have Kconfig entries which depend on GPIOLIB. The
78 GPIO calls are available, either as "real code" or as optimized-away stubs,
117 A number that's not valid will be rejected by calls which may request
139 be checked, since the get/set calls don't have error returns and since
140 misconfiguration is possible. You should normally issue these calls from
166 Use the following calls to access such GPIOs,
180 The get/set calls have no error returns because "invalid GPIO" should have
183 return zero. Also, using these calls for GPIOs that can't safely be accessed
187 calls to access the GPIO value in cases where the GPIO number (and for
[all …]
Dconsumer.txt12 Drivers that can't work without standard GPIO calls should have Kconfig entries
153 checked, since the get/set calls don't return errors and since misconfiguration
154 is possible. You should normally issue these calls from a task context. However,
178 Use the following calls to access GPIOs from an atomic context:
188 The get/set calls do not return errors because "invalid GPIO" should have been
191 Also, using these calls for GPIOs that can't safely be accessed without sleeping
217 that can't be accessed from hardIRQ handlers, these calls act the same as the
218 spinlock-safe calls.
226 following set of calls ignore the active-low property of a GPIO and work on the
Ddriver.txt47 - flag saying whether calls to its methods may sleep
239 - Generic chained GPIO irqchips: take care about generic_handle_irq() calls and
254 does not help since it pins the module to the kernel forever (it calls
/linux-4.4.14/arch/parisc/
DMakefile55 cflags-y += -mfast-indirect-calls
72 KBUILD_CFLAGS_KERNEL += -mlong-calls
DKconfig179 bool "Enable the -mlong-calls compiler option for big kernels"
187 to overcome this limit by using the -mlong-calls compiler option.
/linux-4.4.14/net/rxrpc/
Dar-call.c333 p = rx->calls.rb_node; in rxrpc_get_client_call()
363 pp = &rx->calls.rb_node; in rxrpc_get_client_call()
383 rb_insert_color(&call->sock_node, &rx->calls); in rxrpc_get_client_call()
486 p = &conn->calls.rb_node; in rxrpc_incoming_call()
508 rb_insert_color(&call->conn_node, &conn->calls); in rxrpc_incoming_call()
586 p = rx->calls.rb_node; in rxrpc_find_server_call()
641 rb_erase(&call->sock_node, &rx->calls); in rxrpc_release_call()
790 for (p = rb_first(&rx->calls); p; p = rb_next(p)) { in rxrpc_release_calls_on_socket()
857 rb_erase(&call->conn_node, &call->conn->calls); in rxrpc_cleanup_call()
Dar-recvmsg.c29 rb_erase(&call->sock_node, &call->socket->calls); in rxrpc_remove_user_ID()
74 if (RB_EMPTY_ROOT(&rx->calls)) { in rxrpc_recvmsg()
Dar-connection.c208 conn->calls = RB_ROOT; in rxrpc_alloc_connection()
312 p = &conn->calls.rb_node; in rxrpc_add_call_ID_to_conn()
327 rb_insert_color(&call->conn_node, &conn->calls); in rxrpc_add_call_ID_to_conn()
834 ASSERT(RB_EMPTY_ROOT(&conn->calls)); in rxrpc_destroy_connection()
Dar-accept.c338 pp = &rx->calls.rb_node; in rxrpc_accept_call()
379 rb_insert_color(&call->sock_node, &rx->calls); in rxrpc_accept_call()
Dar-internal.h65 struct rb_root calls; /* outstanding calls on this socket */ member
249 struct rb_root calls; /* calls on this connection */ member
Dar-connevent.c38 for (p = rb_first(&conn->calls); p; p = rb_next(p)) { in rxrpc_abort_calls()
/linux-4.4.14/include/
DKbuild1 # Top-level Makefile calls into asm-$(ARCH)
/linux-4.4.14/Documentation/trace/
Dftrace-design.txt53 the mcount function normally calls __mcount_internal -- the first argument is
57 For example, if the function foo() calls bar(), when the bar() function calls
116 calls the arch-specific function prepare_ftrace_return. Neither of these
200 that calls prepare_ftrace_return(), pass the frame pointer as the 3rd argument.
224 - Put the trace_sys_enter() and trace_sys_exit() tracepoints calls from ptrace
227 of addresses of the system calls, implement an arch_syscall_addr to return
229 - If the symbol names of the system calls do not match the function names on
354 at that location to support the new function calls you'll be inserting. Some
/linux-4.4.14/Documentation/networking/
Drxrpc.txt64 to speed up subsequent calls.
123 billion calls, but only up to four calls may be in progress on a
141 set for the lifetime of that connection, and all subsequent calls made
176 make multiple simultaneous calls to the same service. One server socket
177 may handle calls from many clients.
180 concurrent calls, up to a tunable limit.
190 (*) A client-side connection is only shared between calls if they have have
191 the same key struct describing their security (and assuming the calls
192 would otherwise share the connection). Non-secured calls would also be
203 (*) If an ICMP error is received, all calls affected by that error will be
[all …]
Dppp_generic.txt21 For sending and receiving PPP frames, the generic PPP driver calls on
70 destroyed. For example, the ppp_async channel code calls this when
153 when the core networking code calls the generic layer's start_xmit()
170 when the channel calls ppp_output_wakeup() or when the core
171 networking code calls the generic layer's start_xmit() function
264 calls, along with poll() if necessary. Similarly, an instance
281 The ioctl calls which are available on an instance of /dev/ppp depend
283 to a PPP channel. The ioctl calls which are available on an
300 The ioctl calls available on an instance of /dev/ppp attached to a
321 The ioctl calls that are available on an instance that is attached to
Dframerelay.txt14 The DLCI uses a number of function calls to communicate with the FRAD, all
Dlapb-module.txt109 callbacks, and is used by the device driver in all calls to the LAPB module.
110 For multiple LAPB links in a single device driver, multiple calls to
123 this call, the value of token is no longer valid for any calls to the LAPB
Dgen_stats.txt64 A struct tc_stats will be filled out during gnet_stats_copy_* calls
Dtimestamping.txt60 calls, one to enable timestamp generation and one to disable it.
133 queue out of order from the original send() calls. It is not always
134 possible to uniquely match timestamps to the original send() calls
199 independent send() calls). Segments can be reordered and the same
318 accordingly. Until the process calls recvmsg() on the error queue,
Drds.txt48 setsockopt calls.
313 calls rds_send_xmit() until queue is empty
317 calls transport to send either non-RDMA or RDMA message
/linux-4.4.14/include/uapi/
DKbuild2 # Top-level Makefile calls into asm-$(ARCH)
/linux-4.4.14/arch/nios2/
DMakefile31 KBUILD_CFLAGS += -fno-optimize-sibling-calls
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DGPIO.txt80 The s3c2410_gpio and gpio_ calls have always operated on the same gpio
82 between the calls.
152 These calls are now implemented by the relevant gpiolib calls, convert
/linux-4.4.14/drivers/staging/goldfish/
DREADME8 - Remove excess checking of parameters in calls
/linux-4.4.14/drivers/block/paride/
DTransition-notes24 * in do_pd_request1(): to calls of pi_do_claimed() and return in
28 * in do_pd_read_start(): to calls of pi_do_claimed(), next_request()
30 * in do_pd_read_drq(): to calls of pi_do_claimed() and next_request()
32 * in do_pd_write_start(): to calls of pi_do_claimed(), next_request()
34 * in do_pd_write_done(): to calls of pi_do_claimed() and next_request()
/linux-4.4.14/Documentation/scheduler/
Dcompletion.txt17 look into using one of the wait_for_completion*() calls instead. The
94 Using on-stack completions for code that calls any of the _timeout or
106 calls wait_for_completion() on the initialized completion structure.
203 achieved calls complete() to signal exactly one of the waiters that it can
208 or calls complete_all() to signal all current and future waiters.
224 queue spinlock. Any such concurrent calls to complete() or complete_all()
/linux-4.4.14/Documentation/PCI/
DPCIEBUS-HOWTO.txt97 service driver should always calls pcie_port_service_register at
98 module init. Note that after service driver being loaded, calls
100 necessary since these calls are executed by the PCI Port Bus driver.
169 calls pci_disable_msi to disable MSI interrupts and revert back to
172 calls pci_enable_msi/pci_disable_msi it may result unpredictable
177 of them calls pci_disable_msi, it puts the other service driver
Dpcieaer-howto.txt178 at upstream is not required. The AER driver calls error_detected(dev,
187 whether it can recover or the AER driver calls mmio_enabled as next.
239 A: This infrastructure calls the error callback functions of the
/linux-4.4.14/
DKbuild7 # 4) Check for missing system calls
87 # 4) Check for missing system calls
/linux-4.4.14/Documentation/ABI/removed/
Ddevfs9 along with the assorted devfs function calls throughout the
/linux-4.4.14/arch/arm/include/asm/xen/
Dhypercall.h52 int HYPERVISOR_multicall(struct multicall_entry *calls, uint32_t nr);
/linux-4.4.14/arch/hexagon/
DMakefile16 CFLAGS_MODULE += -mlong-calls
/linux-4.4.14/Documentation/kbuild/
Dheaders_install.txt10 system calls, as well as constants and structures to be used with these
11 system calls. The C library's header files include the kernel header files
/linux-4.4.14/kernel/livepatch/
DKconfig17 a patch, causing calls to patched functions to be redirected
/linux-4.4.14/fs/notify/inotify/
DKconfig8 associated system calls. Inotify allows monitoring of both files and
/linux-4.4.14/arch/blackfin/
DMakefile18 KBUILD_CFLAGS += -mlong-calls
21 KBUILD_CFLAGS_MODULE += -mlong-calls
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-calling.txt1 This page describes how to make calls to the firmware api.
17 reserved for API calls. The second 10 are used by the firmware for event
/linux-4.4.14/Documentation/ia64/
Defirtc.txt14 EFI provides 4 calls one can make once the OS is booted: GetTime(),
16 driver. We describe those calls as well the design of the driver in the
56 Two ioctl()s, compatible with the legacy RTC calls:
Dfsys.txt84 calls, it is possible to write a hand-tuned fsyscall_handler. For
239 * Using fast system calls
241 To use fast system calls, userspace applications need simply call
282 loader that recognises the library, you should be able to make calls to
/linux-4.4.14/arch/blackfin/kernel/
DMakefile41 CFLAGS_kgdb_test.o := -mlong-calls
/linux-4.4.14/arch/sh/
DKconfig.debug14 in FLASH or EPROM. The kernel will use standard BIOS calls during
15 boot for various housekeeping tasks (including calls to read and
/linux-4.4.14/Documentation/wimax/
DREADME.wimax23 calls to notify about changes of state in the device.
25 The stack exports the API calls needed to control the device to user
/linux-4.4.14/drivers/message/fusion/
DKconfig79 of MPT adapters via system ioctl calls. Use of ioctl calls to
/linux-4.4.14/Documentation/vm/
Dhugetlbpage.txt14 system call or standard SYSV shared memory system calls (shmget, shmat).
25 proper alignment and size of the arguments to system calls that map huge page
66 or shared memory system calls to use the huge pages. See the discussion of
299 While read system calls are supported on files that reside on hugetlb
300 file systems, write system calls are not.
306 applications are going to use only shmat/shmget system calls or mmap with
313 applications to use any combination of mmaps and shm* calls, though the mount of
314 filesystem will be required for using mmap calls without MAP_HUGETLB.
Dunevictable-lru.txt232 extra evictabilty checks should not occur in the majority of calls to
296 (1) mapped in a range unlocked via the munlock()/munlockall() system calls;
374 mlock_fixup() treats these VMAs the same as hugetlbfs VMAs. It calls
386 The munlock() and munlockall() system calls are handled by the same functions -
387 do_mlock[all]() - as the mlock() and mlockall() system calls with the unlock vs
388 lock operation indicated by an argument. So, these system calls are also
468 In addition the mlock()/mlockall() system calls, an application can request
513 for the munlock case, calls __munlock_vma_pages_range() to walk the page table
546 munlock or munmap system calls, mm teardown (munlock_vma_pages_all), reclaim,
562 try_to_munlock() calls the same functions as try_to_unmap() for anonymous and
Dremap_file_pages.txt4 over using repeated calls to mmap(2) is that the former approach does not
Dksm.txt35 built with CONFIG_KSM=y, those calls will normally succeed: even if the
41 Like other madvise calls, they are intended for use on mapped areas of
Dzswap.txt76 During a page fault on a PTE that is a swap entry, frontswap calls the zswap
81 in the swap_map goes to 0) the swap code calls the zswap invalidate function,
Dcleancache.txt57 may be shared among those kernels, calls to init_shared_fs that specify the
189 to avoid unnecessary cleancache_invalidate calls. If you want inclusive,
229 or add hooks to do the equivalent cleancache calls done there.
260 tens-of-thousands) of unnecessary function calls per second. So the
/linux-4.4.14/arch/x86/entry/vdso/
DMakefile69 -fno-omit-frame-pointer -foptimize-sibling-calls \
144 KBUILD_CFLAGS_32 += $(call cc-option, -foptimize-sibling-calls)
/linux-4.4.14/scripts/coccinelle/api/
Dd_find_alias.cocci1 /// Make sure calls to d_find_alias() have a corresponding call to dput().
Dpm_runtime.cocci1 /// Make sure pm_runtime_* calls does not use unnecessary IS_ERR_VALUE
Dplatform_no_drv_owner.cocci1 /// Remove .owner field if calls are used which set it automatically
/linux-4.4.14/Documentation/frv/
Dmmu-layout.txt88 the kernel calls kmap(), does the access and then calls kunmap(); or it calls kmap_atomic(), does
89 the access and then calls kunmap_atomic().
93 wills. When it's finished, the kernel calls kunmap() to clear the PTE.
Dkernel-ABI.txt113 Certain registers are also used or modified across function calls:
139 This is the same as the kernel-mode register ABI for functions calls. The
/linux-4.4.14/Documentation/sound/alsa/soc/
Dcodec.txt140 This function is a callback that handles codec domain PM calls and system
141 domain PM calls (e.g. suspend and resume). It is used to put the codec
/linux-4.4.14/Documentation/firmware_class/
DREADME22 - calls request_firmware(&fw_entry, $FIRMWARE, device)
59 8), kernel(driver): Driver code calls release_firmware(fw_entry) releasing
/linux-4.4.14/Documentation/RCU/
DlistRCU.txt49 you are turning auditing off, it is OK to audit a few extra system calls.
70 The read_lock() and read_unlock() calls have become rcu_read_lock()
144 writers to exclude readers. Normally, the write_lock() calls would
145 be converted into spin_lock() calls.
Drcubarrier.txt65 calls, but this is still not guaranteed to work. If there is a very
168 RCU callbacks rarely include calls to call_rcu(). However, the rcutorture
223 ensures that all the calls to rcu_barrier_func() will have completed
Dtorture.txt39 fqs_holdoff Holdoff time (in microseconds) between consecutive calls
43 of calls to force_quiescent_state().
73 torture_type, with a delay between calls to allow for various
/linux-4.4.14/Documentation/driver-model/
Dplatform.txt110 calls to clk_get(&pdev->dev, clock_name) return them as needed.
136 using these calls except with such hotplug-deficient drivers.
204 The architecture code calls parse_early_param() to parse the kernel
230 The architecture code calls early_platform_driver_probe() to match
Ddevice.txt105 calls device_create_file() on the device structure passed to it, then
Dbus.txt31 When a bus driver is initialized, it calls bus_register. This
/linux-4.4.14/drivers/media/usb/pwc/
Dphilips.txt185 'trace' of some of the calls the module makes; it logs all items in your
199 4 0x4 Trace open() and close() calls Off
201 8 0x8 read(), mmap() and associated ioctl() calls Off
228 settings after open() with the Video4Linux ioctl() calls. The default of
/linux-4.4.14/arch/x86/um/vdso/
DMakefile42 -fno-omit-frame-pointer -foptimize-sibling-calls
/linux-4.4.14/Documentation/video4linux/
Dvideobuf8 to implement many of the standard POSIX I/O system calls, including read(),
10 implement the bulk of the V4L2 ioctl() calls related to streaming I/O,
136 videobuf calls into the implementation of the other driver callbacks. The
221 The release() function requires two separate videobuf calls:
240 calls. The relevant helper functions are:
354 enough to get started with. Note also that all of these calls are exported
DREADME.davinci-vpbe37 a set of API calls to V4L2 drivers to set the output/standards
/linux-4.4.14/drivers/md/
Ddm-era-target.c1276 struct list_head calls; in process_rpc_calls() local
1279 INIT_LIST_HEAD(&calls); in process_rpc_calls()
1281 list_splice_init(&era->rpc_calls, &calls); in process_rpc_calls()
1284 list_for_each_entry_safe(rpc, tmp, &calls, list) { in process_rpc_calls()
1292 list_for_each_entry_safe(rpc, tmp, &calls, list) in process_rpc_calls()
1296 list_for_each_entry_safe(rpc, tmp, &calls, list) in process_rpc_calls()
/linux-4.4.14/net/sunrpc/
DKconfig30 Secure RPC calls with Kerberos require an auxiliary user-space
/linux-4.4.14/Documentation/devicetree/
Dchangesets.txt17 2. A number of DT tree change calls, of_changeset_attach_node(),
Dof_unittest.txt109 Secondly, it calls of_fdt_unflatten_tree() to unflatten the flattened
192 whole tree). selftest_data_remove() calls detach_node_and_children() that uses
/linux-4.4.14/arch/
DKconfig201 # TIF_SYSCALL_TRACE calls tracehook_report_syscall_{entry,exit}
202 # TIF_NOTIFY_RESUME calls tracehook_notify_resume()
203 # signal delivery calls tracehook_signal_handler()
247 The <linux/clk.h> calls support software clock gating and
346 directly to seccomp_phase1; this avoids multiple calls
/linux-4.4.14/Documentation/device-mapper/
Dkcopyd.txt27 To start the copy, the user calls kcopyd_copy(), passing in the client
/linux-4.4.14/Documentation/input/
Dgpio-tilt.txt18 input_set_abs_params calls needed to init the axes.
/linux-4.4.14/drivers/pinctrl/
DKconfig22 bool "Debug PINCTRL calls"
25 Say Y here to add some extra checks and diagnostics to PINCTRL calls.
/linux-4.4.14/arch/s390/
DMakefile55 cflags-$(CONFIG_FRAME_POINTER) += -fno-optimize-sibling-calls
/linux-4.4.14/tools/perf/tests/
DBuild58 CFLAGS_dwarf-unwind.o += -fno-optimize-sibling-calls
/linux-4.4.14/Documentation/filesystems/nfs/
Dpnfs-block-server.txt21 If the nfsd server needs to fence a non-responding client it calls
Dknfsd-stats.txt55 of NFS calls received (which statistic is available elsewhere).
67 thus introducing a small delay in servicing NFS calls. The ideal
/linux-4.4.14/fs/pstore/
DKconfig40 With this option kernel traces function calls into a persistent
/linux-4.4.14/Documentation/hid/
Dhiddev.txt64 The hiddev API uses a read() interface, and a set of ioctl() calls.
143 be filled in by the user through HIDIOCSUSAGE calls (below) to fill in
193 HIDDEV_FLAG_UREF - read() calls will now return
Dhid-transport.txt78 verifications. Generally, HID calls operating on asynchronous channels must be
248 ->open() calls are nested for each client that opens the HID device.
255 ->open() calls have been followed by a ->close() call. However, ->start() may
292 must not cause SET_REPORT calls! This must be implemented as asynchronous
/linux-4.4.14/Documentation/timers/
Dhighres.txt132 adding the dynamic tick specific calls to the idle routine (a total of 3 lines
157 calls when an interrupt happens. The overhead would be much larger than the
188 and calls update_process_times and profiling. The implementation of the hrtimer
226 it calls schedule(). hrtimer_restart_sched_tick() resumes the periodic tick,
Dtimers-howto.txt53 driving each of these calls varies, thus there are
/linux-4.4.14/Documentation/rapidio/
Drapidio.txt97 within the subsystem controller driver's initialization code calls function
153 When a network scan process is started it calls an enumeration or discovery
209 initialization routine calls rio_init_mports() to perform enumeration or
282 devices by clearing device ID locks (calls rio_clear_locks()). For each endpoint
308 method's module initialization routine calls rio_register_scan() to attach
/linux-4.4.14/arch/mn10300/include/asm/
Dframe.inc40 add -12,sp # allow for calls to be made
/linux-4.4.14/arch/sh/kernel/
Dentry-common.S198 ! This allows the parent to rewrite system calls
/linux-4.4.14/drivers/staging/gs_fpgaboot/
DREADME61 separate driver (pcie or others), then THAT driver calls my driver to
/linux-4.4.14/arch/ia64/
DMakefile30 -falign-functions=32 -frename-registers -fno-optimize-sibling-calls
DKconfig502 make ESI calls. ESI calls are used to support vendor-specific
507 bool "Support ACPI AML calls to native firmware"
/linux-4.4.14/arch/powerpc/include/asm/
Dspu.h273 int register_spu_syscalls(struct spufs_calls *calls);
274 void unregister_spu_syscalls(struct spufs_calls *calls);
/linux-4.4.14/tools/perf/scripts/perl/Perf-Trace-Util/
DREADME7 that the core perf support for Perl calls on and should always be
/linux-4.4.14/Documentation/laptops/
Dtoshiba_haps.txt52 a couple HCI (Hardware Configuration Interface) calls (0x6D and 0xA6) are
/linux-4.4.14/Documentation/fmc/
DAPI.txt41 Finally, the fmc_reprogram function calls the reprogram method (see
/linux-4.4.14/Documentation/x86/
Dexception-tables.txt27 accessible, the CPU generates a page fault exception and calls the
266 3.) CPU calls do_page_fault
267 4.) do page fault calls search_exception_table (regs->eip == c017e7a5);
Dintel_mpx.txt41 when it calls the prctl(). This might be hard to guarantee if the app
73 * calls a new prctl(PR_MPX_ENABLE_MANAGEMENT) to notify the kernel to
151 these calls.
/linux-4.4.14/Documentation/scsi/
DChangeLog.lpfc10 * Removed pci dma sync calls to coherent/consistent pci memory.
23 * Removed extraneous calls to lpfc_sli_next_iotag which should
217 function calls in this function which are not safe to call from
259 * Removed loop which calls fc_remote_port_unblock and
327 operations for mempool_alloc calls. General code cleanup. All
458 * Hung dt session fix. When the midlayer calls to abort a scsi
523 unmap calls.
526 * Use scsi_[activate|deactivate]_tcq calls provided in scsi_tcq.h.
531 that are using pci_dma_sync calls. Probably these should be
692 * Incorporating block/unblock calls into driver with ifdefs. This
[all …]
Dscsi_eh.txt51 just calls blk_complete_request() to delete the block layer timer and
54 SCSI_SOFTIRQ handler scsi_softirq calls scsi_decide_disposition() to
61 function does some maintenance chores and then calls
186 calls scsi_block_when_processing_errors() on the host.
Dlibsas.txt104 can find your way around faster when the SAS layer calls one
155 /* LLDD calls these to notify the class of an event. */
166 /* The class calls these to notify the LLDD of an event. */
DChangeLog.ips29 4.80.04 - Eliminate calls to strtok() if 2.4.x or greater
/linux-4.4.14/arch/mips/
DMakefile93 KBUILD_AFLAGS_MODULE += -mlong-calls
94 KBUILD_CFLAGS_MODULE += -mlong-calls
/linux-4.4.14/drivers/firmware/
DKconfig31 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
35 Services real mode BIOS calls to determine which disk
/linux-4.4.14/drivers/isdn/
DKconfig16 voice calls (eg. turning your PC into a software answering machine
/linux-4.4.14/Documentation/cgroups/
Dcpusets.txt55 set_mempolicy(2) system calls to include Memory Nodes in its memory
147 - in the mbind and set_mempolicy system calls, to mask the requested
154 new system calls are added for cpusets - all support for querying and
203 using the sched_setaffinity, mbind and set_mempolicy system calls.
334 instead. Tasks using mbind() or set_mempolicy() calls to set NUMA
335 mempolicies will not notice any change in these calls as a result of
349 joins that cpuset. The page allocation calls for the page cache
704 The sched_setaffinity calls can also be done at the shell prompt using
706 calls can be done at the shell prompt using the numactl command
828 A: bash's builtin 'echo' command does not check calls to write() against
/linux-4.4.14/arch/powerpc/
DKconfig.debug43 Adds code to keep track of the number of hypervisor calls made and
44 the amount of time spent in hypervisor calls. Wall time spent in
51 calls.
/linux-4.4.14/arch/m68k/ifpsp060/
Dfplsp.doc41 making subroutine calls in place of the unimplemented
126 subroutine calls for all fp instructions. The code does NOT emulate
DTEST.DOC120 In "C"-like fashion, the test program calls:
148 3 different calls to the package if each of the three following tests
/linux-4.4.14/Documentation/hwmon/
Dpmbus-core218 This function calls the device specific write_byte function if defined.
225 This function calls the device specific write_byte function if defined to
232 This function calls the device specific write_byte function if defined to
/linux-4.4.14/Documentation/leds/
Dleds-class-flash.txt69 flash API device would. The calls are simply routed to the LED flash API.
Dleds-class.txt48 There have been calls for LED properties such as colour to be exported as
/linux-4.4.14/Documentation/ptp/
Dptp.txt45 clock_gettime, clock_settime, and clock_adjtime. These calls
/linux-4.4.14/Documentation/mn10300/
DABI.txt136 System calls are called with the following convention:
/linux-4.4.14/fs/befs/
DChangeLog106 linux VFS doesn't allow us to keep any state between calls. Updated
235 of blocks, which in turn calls befs_fpos2brun() in datastream.c to do
396 * Removed superblock locking calls in befs_read_super(). In 2.4, the VFS
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt251 Finally, when userspace calls rmdir(2) on the item or group,
403 configfs provides two additional API calls: configfs_depend_item() and
407 item. When the item is no longer depended on, the client driver calls
418 up. Here, the heartbeat code calls configfs_depend_item(). If it
/linux-4.4.14/kernel/trace/
DKconfig162 address on the current task structure into a stack of calls.
343 calls in the kernel. The difference between this and the
452 This option will modify all the calls to function tracing
547 run), and calls the tracepoint. Each iteration will record the time
/linux-4.4.14/Documentation/cdrom/
Dcdrom-standard.tex138 implemented the \cdrom\ $ioctl()$ calls through their own routines. This
501 Seconds, Frames) for all audio calls. It also verifies the memory
549 Instead of just implementing some $ioctl$ calls, the interface in
671 subsequent calls to the device don't cause the calling process to
801 calls the device-dependent $release()$ routine. When the use-count has
802 reached 0, the allocated buffers are flushed by calls to $sync_dev(dev)$
811 devices in a uniform way. The different calls fall into three
829 set behavior to non-moving on $open()$ and $release()$ calls.
882 the last call. Note that calls to $cdrom_media_changed$ by the VFS
984 just calls to the routines you adapted in the previous step.
/linux-4.4.14/include/net/
Dax25.h180 ax25_address calls[AX25_MAX_DIGIS]; member
/linux-4.4.14/Documentation/filesystems/cifs/
DTODO22 d) quota support (needs minor kernel change since quota calls
/linux-4.4.14/Documentation/cpu-freq/
Dboost.txt22 On Intel CPUs this is called "Turbo Boost", AMD calls it "Turbo-Core",

123