Home
last modified time | relevance | path

Searched refs:nesting (Results 1 – 25 of 41) sorted by relevance

12

/Linux-v5.15/include/linux/
Drcupdate_trace.h34 void rcu_read_unlock_trace_special(struct task_struct *t, int nesting);
71 int nesting; in rcu_read_unlock_trace() local
75 nesting = READ_ONCE(t->trc_reader_nesting) - 1; in rcu_read_unlock_trace()
79 if (likely(!READ_ONCE(t->trc_reader_special.s)) || nesting) { in rcu_read_unlock_trace()
80 WRITE_ONCE(t->trc_reader_nesting, nesting); in rcu_read_unlock_trace()
83 rcu_read_unlock_trace_special(t, nesting); in rcu_read_unlock_trace()
Dcookie.h10 local_t nesting; member
35 if (likely(local_inc_return(&local->nesting) == 1)) { in gen_cookie_next()
47 local_dec(&local->nesting); in gen_cookie_next()
/Linux-v5.15/arch/arm/probes/kprobes/
Dtest-core.c693 unsigned nesting; member
700 unsigned nesting; member
749 entry->nesting = coverage->nesting; in coverage_start_fn()
755 ++coverage->nesting; in coverage_start_fn()
757 --coverage->nesting; in coverage_start_fn()
770 coverage.nesting = 0; in coverage_start()
847 unsigned nesting = 0; in coverage_add() local
853 if (entry->nesting > nesting) in coverage_add()
856 if (entry->nesting < nesting) in coverage_add()
868 ++nesting; in coverage_add()
/Linux-v5.15/tools/memory-model/
Dlinux-kernel.bell55 (* Validate nesting *)
71 (* Validate nesting *)
79 flag ~empty different-values(srcu-rscs) as srcu-bad-nesting
DREADME174 read-side critical section nesting analysis.
/Linux-v5.15/tools/build/tests/ex/empty2/
DREADME2 to test proper nesting into Build-less directories.
/Linux-v5.15/Documentation/virt/kvm/
Drunning-nested-guests.rst38 a different design for nesting.
82 nesting, set the ``nested`` KVM module parameter to ``Y`` or ``1``. To
145 Once your bare metal host (L0) is configured for nesting, you should be
196 Migrating an L1 guest merely configured to support nesting, while not
219 of "nesting" at all, say so. Unfortunately, this needs to be called
/Linux-v5.15/Documentation/core-api/
Dgfp_mask-from-fs-io.rst46 nesting would be possible via reclaim. The restore function should be
51 allows nesting so it is safe to call ``memalloc_noio_save`` or
/Linux-v5.15/Documentation/admin-guide/device-mapper/
Dpersistent-data.rst83 thin-provisioning target uses a btree with two levels of nesting.
88 64bits, although nesting allows you to use multiple keys.
/Linux-v5.15/kernel/rcu/
Dtree_stall.h234 int nesting; member
249 rscrp->nesting = t->rcu_read_lock_nesting; in check_slow_task()
290 t->pid, rscr.nesting, in rcu_print_task_stall()
Dtasks.h851 void rcu_read_unlock_trace_special(struct task_struct *t, int nesting) in rcu_read_unlock_trace_special() argument
861 WRITE_ONCE(t->trc_reader_nesting, nesting); in rcu_read_unlock_trace_special()
Dtree.c424 long nesting; in rcu_is_cpu_rrupt_from_idle() local
440 nesting = __this_cpu_read(rcu_data.dynticks_nmi_nesting); in rcu_is_cpu_rrupt_from_idle()
441 if (nesting > 1) in rcu_is_cpu_rrupt_from_idle()
447 WARN_ON_ONCE(!nesting && !is_idle_task(current)); in rcu_is_cpu_rrupt_from_idle()
/Linux-v5.15/Documentation/x86/
Dkernel-stacks.rst63 stack size allocated to an IST assumes no nesting for the same code.
98 the IST stackpointer to a guard hole to catch triple nesting.
/Linux-v5.15/include/net/bluetooth/
Dl2cap.h545 atomic_t nesting; member
854 mutex_lock_nested(&chan->lock, atomic_read(&chan->nesting)); in l2cap_chan_lock()
/Linux-v5.15/drivers/infiniband/ulp/ipoib/
Dipoib_ib.c1153 int nesting) in __ipoib_ib_dev_flush() argument
1159 down_read_nested(&priv->vlan_rwsem, nesting); in __ipoib_ib_dev_flush()
1166 __ipoib_ib_dev_flush(cpriv, level, nesting + 1); in __ipoib_ib_dev_flush()
Dipoib_main.c404 int nesting, in ipoib_match_gid_pkey_addr() argument
430 down_read_nested(&priv->vlan_rwsem, nesting); in ipoib_match_gid_pkey_addr()
434 nesting + 1, in ipoib_match_gid_pkey_addr()
/Linux-v5.15/Documentation/locking/
Dlocktypes.rst20 for their nesting, including the rules for use under PREEMPT_RT.
513 Lock type nesting rules
533 spinlock. This results in the following nesting ordering:
Dlockdep-design.rst212 specify a "nesting level". An example call, for the block device mutex,
305 every possible hardirq and softirq nesting scenario (which is impossible
/Linux-v5.15/Documentation/networking/
Dopenvswitch.rst85 and nesting. For example, the following could represent a flow key
244 - Duplicate attributes are not allowed at a given nesting level.
/Linux-v5.15/Documentation/RCU/Design/Requirements/
DRequirements.rst1026 dyntick-idle nesting counter allows 54 bits for interrupt nesting
1506 mass storage, or user patience, whichever comes first. If the nesting is
1509 If the nesting takes the form of loops, perhaps in the guise of tail
1515 RCU implementations that explicitly track nesting depth are limited by
1516 the nesting-depth counter. For example, the Linux kernel's preemptible
1517 RCU limits nesting to ``INT_MAX``. This should suffice for almost all
1830 counts interrupt nesting levels. I learned of this requirement the hard
1994 nesting. The fact that interrupt-disabled regions of code act as RCU
2087 #. Although nesting RCU_NONIDLE() is permitted, they cannot nest
2090 serious restriction. This nesting limit would probably be reached
/Linux-v5.15/tools/testing/selftests/bpf/prog_tests/
Dcore_reloc.c523 NESTING_CASE(nesting),
/Linux-v5.15/net/bluetooth/
Dl2cap_sock.c308 atomic_set(&chan->nesting, L2CAP_NESTING_PARENT); in l2cap_sock_listen()
1528 lock_sock_nested(sk, atomic_read(&chan->nesting)); in l2cap_sock_teardown_cb()
D6lowpan.c937 atomic_set(&chan->nesting, L2CAP_NESTING_PARENT); in bt_6lowpan_listen()
/Linux-v5.15/drivers/vfio/
Dvfio_iommu_type1.c78 bool nesting; member
2320 if (iommu->nesting) { in vfio_iommu_type1_attach_group()
2662 iommu->nesting = true; in vfio_iommu_type1_open()
/Linux-v5.15/Documentation/userspace-api/
Dlandlock.rst235 handle composition of rules. Such property also implies rules nesting.

12