| /linux/rust/pin-init/internal/src/ |
| H A D | helpers.rs | |
| H A D | pinned_drop.rs | 14 let mut nesting: usize = 0; pinned_drop() localVariable
|
| /linux/include/linux/ |
| 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/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()
769 coverage.nesting = 0; in coverage_start()
846 unsigned nesting = 0; in coverage_add() local
852 if (entry->nesting > nesting) in coverage_add()
855 if (entry->nesting < nesting) in coverage_add()
867 ++nesting; in coverage_add()
|
| /linux/kernel/ |
| H A D | context_tracking.c | 31 .nesting = 1,
113 ct->nesting--; in ct_kernel_exit()
127 WRITE_ONCE(ct->nesting, 0); /* Avoid irq-access tearing. */ in ct_kernel_exit()
152 ct->nesting++; in ct_kernel_enter()
166 WRITE_ONCE(ct->nesting, 1); in ct_kernel_enter()
|
| /linux/kernel/trace/ |
| H A D | trace_printk.c | 493 int nesting; member
507 if (!trace_percpu_buffer || buffer->nesting >= 4) in get_trace_buf()
510 buffer->nesting++; in get_trace_buf()
514 return &buffer->buffer[buffer->nesting - 1][0]; in get_trace_buf()
521 this_cpu_dec(trace_percpu_buffer->nesting); in put_trace_buf()
|
| /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/Documentation/core-api/ |
| H A D | gfp_mask-from-fs-io.rst | 46 nesting would be possible via reclaim. The restore function should be
51 allows nesting so it is safe to call ``memalloc_noio_save`` or
|
| H A D | entry.rst | 188 disabled, interrupt nesting is common from an entry/exit perspective. For
279 need to handle nesting.
|
| /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/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/userspace-api/netlink/ |
| H A D | netlink-raw.rst | 66 :ref:`tc<netlink-tc>` use attribute nesting as an
82 example above shows attributes nesting inside the wrapper, the modules generally
|
| 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/kernel/rcu/ |
| H A D | tree_stall.h | 299 int nesting; member
314 rscrp->nesting = t->rcu_read_lock_nesting; in check_slow_task()
355 t->pid, rscr.nesting, in rcu_print_task_stall()
|
| /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 | 517 atomic_t nesting; member
829 mutex_lock_nested(&chan->lock, atomic_read(&chan->nesting)); in l2cap_chan_lock()
|
| /linux/Documentation/locking/ |
| H A D | locktypes.rst | 20 for their nesting, including the rules for use under PREEMPT_RT.
528 Lock type nesting rules
548 spinlock. This results in the following nesting ordering:
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-health.rst | 71 attributes, to avoid actual nesting use which cannot be divided between
|
| /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.
|