Searched refs:callers (Results 1 – 25 of 25) sorted by relevance
| /linux-4.4.14/Documentation/networking/ |
| D | tc-actions-env-rules.txt | 17 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| /linux-4.4.14/drivers/scsi/ |
| D | xen-scsifront.c | 123 unsigned callers; member
518 info->callers++; in scsifront_enter()
524 info->callers--; in scsifront_return()
525 if (info->callers) in scsifront_return()
923 while (info->callers && !err) { in scsifront_suspend()
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | porting | 103 check for ->link() target not being a directory is done by callers. Feel
109 ->link() callers hold ->i_mutex on the object we are linking to. Some of your
279 nobh_write_begin, blockdev_direct_IO*) to callers. Take a look at
280 ext2_write_failed and callers for an example.
|
| D | relay.txt | 287 buffer - but since it is a global buffer, callers should make sure
|
| D | Locking | 310 keep it that way and don't breed new callers.
|
| /linux-4.4.14/Documentation/firmware_class/ |
| D | README | 126 resume callback, and callers needn't cache the firmware by
|
| /linux-4.4.14/Documentation/target/ |
| D | tcm_mod_builder.txt | 15 *) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
|
| /linux-4.4.14/Documentation/trace/ |
| D | events-kmem.txt | 58 callers should be batching their activities.
|
| /linux-4.4.14/Documentation/usb/ |
| D | dma.txt | 80 This may force your callers to do some bounce buffering, copying from
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.diversion | 61 number and subaddress, callers number and subaddress and whether the rule
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-top.txt | 184 This has the effect of collecting the callers of each such
|
| D | perf-report.txt | 229 This has the effect of collecting the callers of each such
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Transition-notes | 128 can be taken to callers as long as they remain within the area.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | listRCU.txt | 141 a spin_lock() and a spin_unlock(), but in this case, all callers hold
|
| D | whatisRCU.txt | 316 to their callers and (2) call_rcu() callbacks may be invoked. Efficient
|
| /linux-4.4.14/Documentation/scsi/ |
| D | libsas.txt | 384 and its callers, in the file "expander_conf.c".
|
| D | ChangeLog.megaraid | 606 viii. Optimize the build scatter-gather list routine. The callers already
|
| /linux-4.4.14/Documentation/vm/ |
| D | unevictable-lru.txt | 486 The callers of populate_vma_page_range() will have already added the memory range
489 callers then subtract a non-negative return value from the task's locked_vm. A
|
| /linux-4.4.14/arch/sparc/kernel/ |
| D | entry.S | 910 mov %fp, %o1 ! yes, use callers usp
|
| /linux-4.4.14/kernel/trace/ |
| D | Kconfig | 345 histogram of the callers, but actually places the calling
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 4.Coding | 68 always passed as zero by all callers. One could retain that argument just
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | mmu.txt | 308 reserved bit on the spte (see callers of kvm_mmu_set_mmio_spte_mask)
|
| /linux-4.4.14/Documentation/ |
| D | kmemcheck.txt | 748 If a slab cache is NOT set up using the SLAB_NOTRACK flag, callers can still
|
| D | kernel-parameters.txt | 1228 [FTRACE] Limit the top level callers functions traced
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 417 of extra space on the callers stack which is obviously freed
|