| /linux/include/linux/ |
| H A D | rcupdate_trace.h | 72 int nesting; in rcu_read_unlock_trace() local
76 nesting = READ_ONCE(t->trc_reader_nesting) - 1; in rcu_read_unlock_trace()
79 WRITE_ONCE(t->trc_reader_nesting, INT_MIN + nesting); in rcu_read_unlock_trace()
80 if (likely(!READ_ONCE(t->trc_reader_special.s)) || nesting) { in rcu_read_unlock_trace()
81 WRITE_ONCE(t->trc_reader_nesting, nesting); in rcu_read_unlock_trace()
84 WARN_ON_ONCE(nesting != 0); in rcu_read_unlock_trace()
|
| H A D | cookie.h | 10 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()
|
| H A D | context_tracking_state.h | 36 long nesting; /* Track process nesting level. */ member
110 return __this_cpu_read(context_tracking.nesting); in ct_nesting()
117 return ct->nesting; in ct_nesting_cpu()
|
| /linux/rust/macros/ |
| H A D | pinned_drop.rs | |
| /linux/rust/pin-init/internal/src/ |
| H A D | pinned_drop.rs | 14 let mut nesting: usize = 0; in pinned_drop() localVariable
19 nesting += 1; in pinned_drop()
22 nesting = nesting.checked_sub(1).unwrap(); in pinned_drop()
27 if i >= 1 && nesting == 0 { in pinned_drop()
|
| /linux/arch/arm/probes/kprobes/ |
| H A D | test-core.c | 693 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/Documentation/userspace-api/ |
| H A D | iommufd.rst | 49 running in the user space, or a nesting parent stage-2 domain for mappings
61 feature.) As such, it must be created with a given nesting parent stage-2
79 * Access to a shareable nesting parent pagetable across physical IOMMUs
85 Such a vIOMMU object generally has the access to a nesting parent pagetable
87 must be created given a nesting parent HWPT_PAGING object, and then it would
225 allocates a nesting parent HWPT_PAGING if the IOMMU_HWPT_ALLOC_NEST_PARENT
230 nesting parent HWPT_PAGING via @pt_id to associate the new HWPT_NESTED object
232 must be a nesting parent manually allocated via the same uAPI previously with
235 nesting parent domain and the nested domain being allocated are compatible.
239 can be allocated by (and then associated to) the same nesting parent.
[all …]
|
| /linux/tools/build/tests/ex/empty2/ |
| H A D | README | 2 to test proper nesting into Build-less directories.
|
| /linux/Documentation/virt/kvm/x86/ |
| H A D | running-nested-guests.rst | 40 a different design for nesting.
84 nesting, set the ``nested`` KVM module parameter to ``Y`` or ``1``. To
147 Once your bare metal host (L0) is configured for nesting, you should be
198 Migrating an L1 guest merely configured to support nesting, while not
221 of "nesting" at all, say so. Unfortunately, this needs to be called
|
| /linux/tools/memory-model/ |
| H A D | linux-kernel.bell | 68 (* Validate nesting *)
76 (* Validate nesting *)
|
| H A D | README | 175 read-side critical section nesting analysis.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | persistent-data.rst | 83 thin-provisioning target uses a btree with two levels of nesting.
88 64bits, although nesting allows you to use multiple keys.
|
| /linux/Documentation/bpf/ |
| H A D | map_of_maps.rst | 13 purpose support for map in map storage. One level of nesting is supported, where
27 - Multi-level nesting is not supported.
|
| /linux/Documentation/userspace-api/netlink/ |
| H A D | genetlink-legacy.rst | 84 ``type-value`` can have multiple levels of nesting, for example
96 the nesting serves no good purpose here.
|
| /linux/Documentation/arch/x86/ |
| H A D | kernel-stacks.rst | 63 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/include/net/bluetooth/ |
| H A D | l2cap.h | 515 atomic_t nesting; member
827 mutex_lock_nested(&chan->lock, atomic_read(&chan->nesting)); in l2cap_chan_lock()
|
| /linux/Documentation/RCU/Design/Data-Structures/ |
| H A D | Data-Structures.rst | 971 1 long nesting;
981 The ``->nesting`` field counts the nesting depth of process
987 and nested transitions add two, so that a nesting level of five is
996 ``->nesting`` field is incremented up from zero, the
998 whenever the ``->nesting`` field is decremented down to zero,
1028 | Why not simply combine the ``->nesting`` and |
1106 The ``->rcu_read_lock_nesting`` field records the nesting level for RCU
|
| /linux/Documentation/networking/ |
| H A D | openvswitch.rst | 85 and nesting. For example, the following could represent a flow key
244 - Duplicate attributes are not allowed at a given nesting level.
|
| /linux/kernel/rcu/ |
| H A D | Kconfig.debug | 65 must be enabled for the RCU-nesting checks to take effect.
|
| /linux/net/bluetooth/ |
| H A D | l2cap_sock.c | 319 atomic_set(&chan->nesting, L2CAP_NESTING_PARENT); in l2cap_sock_listen()
1590 * we need separation into separate nesting levels. The simplest in l2cap_sock_teardown_cb()
1591 * way to accomplish this is to inherit the nesting level used in l2cap_sock_teardown_cb()
1594 lock_sock_nested(sk, atomic_read(&chan->nesting)); in l2cap_sock_teardown_cb()
|
| H A D | 6lowpan.c | 954 atomic_set(&chan->nesting, L2CAP_NESTING_PARENT); in bt_6lowpan_listen()
|
| /linux/Documentation/trace/rv/ |
| H A D | monitor_sched.rst | 31 this case), otherwise the linker would not respect the order and the nesting
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | core_reloc.c | 578 /* various struct/enum nesting and resolution scenarios */
579 NESTING_CASE(nesting),
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 1026 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
2118 nesting. The fact that interrupt-disabled regions of code act as RCU
|
| /linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 212 specify a "nesting level". An example call, for the block device mutex,
305 every possible hardirq and softirq nesting scenario (which is impossible
|