/linux-4.4.14/arch/arm/probes/kprobes/ |
D | test-core.c | 752 unsigned nesting; member 759 unsigned nesting; member 808 entry->nesting = coverage->nesting; in coverage_start_fn() 814 ++coverage->nesting; in coverage_start_fn() 816 --coverage->nesting; in coverage_start_fn() 828 coverage.nesting = 0; in coverage_start() 905 unsigned nesting = 0; in coverage_add() local 911 if (entry->nesting > nesting) in coverage_add() 914 if (entry->nesting < nesting) in coverage_add() 926 ++nesting; in coverage_add()
|
/linux-4.4.14/tools/build/tests/ex/empty2/ |
D | README | 2 to test proper nesting into Build-less directories.
|
/linux-4.4.14/arch/x86/crypto/sha-mb/ |
D | sha1_mb_mgr_datastruct.S | 88 # # Following only needed if nesting
|
/linux-4.4.14/Documentation/device-mapper/ |
D | persistent-data.txt | 79 thin-provisioning target uses a btree with two levels of nesting. 84 64bits, although nesting allows you to use multiple keys.
|
/linux-4.4.14/drivers/staging/lustre/lustre/obdclass/ |
D | cl_lock.c | 119 enum clt_nesting_level nesting; in cl_lock_counters() local 122 nesting = cl_lock_nesting(lock); in cl_lock_counters() 123 LASSERT(nesting < ARRAY_SIZE(info->clt_counters)); in cl_lock_counters() 124 return &info->clt_counters[nesting]; in cl_lock_counters() 841 enum clt_nesting_level nesting; in cl_lock_hold_mod() local 844 nesting = cl_lock_nesting(lock); in cl_lock_hold_mod() 845 if (nesting == CNL_TOP) { in cl_lock_hold_mod() 860 enum clt_nesting_level nesting; in cl_lock_used_mod() local 863 nesting = cl_lock_nesting(lock); in cl_lock_used_mod() 864 if (nesting == CNL_TOP) { in cl_lock_used_mod()
|
/linux-4.4.14/drivers/vfio/ |
D | vfio_iommu_type1.c | 61 bool nesting; member 778 if (iommu->nesting) { in vfio_iommu_type1_attach_group() 911 iommu->nesting = true; in vfio_iommu_type1_open()
|
/linux-4.4.14/include/net/bluetooth/ |
D | l2cap.h | 492 atomic_t nesting; member 797 mutex_lock_nested(&chan->lock, atomic_read(&chan->nesting)); in l2cap_chan_lock()
|
/linux-4.4.14/drivers/infiniband/ulp/ipoib/ |
D | ipoib_ib.c | 975 int nesting) in __ipoib_ib_dev_flush() argument 981 down_read_nested(&priv->vlan_rwsem, nesting); in __ipoib_ib_dev_flush() 988 __ipoib_ib_dev_flush(cpriv, level, nesting + 1); in __ipoib_ib_dev_flush()
|
D | ipoib_main.c | 335 int nesting, in ipoib_match_gid_pkey_addr() argument 361 down_read_nested(&priv->vlan_rwsem, nesting); in ipoib_match_gid_pkey_addr() 365 nesting + 1, in ipoib_match_gid_pkey_addr()
|
/linux-4.4.14/Documentation/RCU/ |
D | trace.txt | 109 first "/" is the interrupt nesting depth when in idle state, 110 or a large number added to the interrupt-nesting depth when 112 count interrupt nesting when running in non-idle kernel context, 114 interrupt-nesting levels. The number after the second "/" 115 is the NMI nesting depth.
|
D | stallwarn.txt | 120 number between the two "/"s is the value of the nesting, which will
|
/linux-4.4.14/Documentation/networking/ |
D | openvswitch.txt | 82 and nesting. For example, the following could represent a flow key 241 - Duplicate attributes are not allowed at a given nesting level.
|
/linux-4.4.14/Documentation/locking/ |
D | lockdep-design.txt | 150 specify a "nesting level". An example call, for the block device mutex, 196 every possible hardirq and softirq nesting scenario (which is impossible
|
D | lglock.txt | 47 though needs careful considerations for nesting of lglocks and
|
D | rt-mutex-design.txt | 238 the nesting of mutexes. Let's look at the example where we have 3 mutexes,
|
/linux-4.4.14/Documentation/x86/ |
D | kernel-stacks | 57 stack size allocated to an IST assumes no nesting for the same code.
|
/linux-4.4.14/net/bluetooth/ |
D | l2cap_sock.c | 292 atomic_set(&chan->nesting, L2CAP_NESTING_PARENT); in l2cap_sock_listen() 1317 lock_sock_nested(sk, atomic_read(&chan->nesting)); in l2cap_sock_teardown_cb()
|
D | 6lowpan.c | 1086 atomic_set(&chan->nesting, L2CAP_NESTING_PARENT); in bt_6lowpan_listen()
|
D | smp.c | 3101 atomic_set(&chan->nesting, L2CAP_NESTING_SMP); in smp_new_conn_cb() 3199 atomic_set(&chan->nesting, L2CAP_NESTING_PARENT); in smp_add_cid()
|
D | l2cap_core.c | 437 atomic_set(&chan->nesting, L2CAP_NESTING_NORMAL); in l2cap_chan_create()
|
/linux-4.4.14/Documentation/cgroups/ |
D | unified-hierarchy.txt | 204 extra layer of nesting which may not be necessary, makes the interface 266 cgroups in or nesting depth of a delegated sub-hierarchy; however,
|
/linux-4.4.14/Documentation/ |
D | CodingStyle | 35 benefit of warning you when you're nesting your functions too deep. 406 - nesting is reduced
|
D | kernel-parameters.txt | 1782 [KVM,Intel] Enable VMX nesting (nVMX).
|
/linux-4.4.14/Documentation/development-process/ |
D | 5.Posting | 307 creating exceptionally deep nesting.
|
/linux-4.4.14/Documentation/filesystems/ |
D | autofs4-mount-control.txt | 91 entry with a large number of offsets, possibly with nesting, we needed
|
/linux-4.4.14/kernel/trace/ |
D | Kconfig | 596 to the ring buffer, to test/stress the nesting ability.
|
/linux-4.4.14/kernel/events/ |
D | core.c | 958 perf_event_ctx_lock_nested(struct perf_event *event, int nesting) in perf_event_ctx_lock_nested() argument 971 mutex_lock_nested(&ctx->mutex, nesting); in perf_event_ctx_lock_nested()
|
/linux-4.4.14/Documentation/security/ |
D | keys.txt | 587 The link procedure checks the nesting of the keyrings, returning ELOOP if
|