Searched refs:reachable (Results 1 – 19 of 19) sorted by relevance
34 bool reachable; member64 bool reachable; member266 bool reachable; in __prestera_util_kern_n_is_reachable_v4() local268 reachable = false; in __prestera_util_kern_n_is_reachable_v4()274 reachable = true; in __prestera_util_kern_n_is_reachable_v4()277 return reachable; in __prestera_util_kern_n_is_reachable_v4()751 if (!fib_cache || !fib_cache->reachable) { in __prestera_k_arb_n_lpm_set()779 nc->reachable = true; in __prestera_k_arb_nc_kern_fib_fetch()781 nc->reachable = false; in __prestera_k_arb_nc_kern_fib_fetch()825 __prestera_k_arb_n_lpm_set(sw, nc, nc->reachable && nc->in_kernel); in __prestera_k_arb_nc_apply()[all …]
23 is enabled and reachable from the driver module.
155 If set, leaf sptes reachable from this page are for a linear range.218 use this field as non-root TDP MMU pages are reachable only from their270 pages reachable from a given page.302 A tlb flush means that we need to synchronize all sptes reachable from the306 A special case is when a guest page table is reachable from the current315 As a side effect we have to resynchronize all reachable unsynchronized shadow387 - synchronize newly reachable shadow pages393 - synchronize newly reachable shadow pages
46 Finally, assuming CXL memory is reachable via the page allocation (i.e. onlined
351 "$ABIDIFF" --non-reachable-types \
127 devices that are reachable through an I2C-mux. The devices on the mux
5 These are segment of kernel provided user code reachable from user space
62 By default, kunit_tool runs all tests reachable with minimal configuration,
125 the other, as long as the devices are still reachable by the same
609 that both the source and destination cgroups are reachable from the611 is not reachable, the migration is rejected with -ENOENT.
47 be unreachable" situations. If you want to warn about "reachable
140 In that case ``slabinfo -v`` simply tests all reachable objects. Usually
352 NOS is reachable only via digipeating through the kernel AX.25
293 reachable).
71 it is reachable (on which bus it resides) and its configuration –
262 - one or more pages are at addresses not reachable by the HBA
57 (reachable from a folio via :c:member:`!folio->mapping`). VMAs must be stabilised via
1335 which means to always cache a reachable dentry. d_delete must
8370 or moved memslot isn't reachable, i.e KVM