| /linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/ |
| H A D | tlb.json | 4 …any Instruction fetch. If there are multiple misses in the TLB that are resolved by the refill, th…
8 …sulted in TLB refills. If there are multiple misses in the TLB that are resolved by the refill, th…
36 …emory read operations. If there are multiple misses in the TLB that are resolved by the refill, th…
40 …mory write operations. If there are multiple misses in the TLB that are resolved by the refill, th…
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/ |
| H A D | tlb.json | 4 …any Instruction fetch. If there are multiple misses in the TLB that are resolved by the refill, th…
8 …sulted in TLB refills. If there are multiple misses in the TLB that are resolved by the refill, th…
36 …emory read operations. If there are multiple misses in the TLB that are resolved by the refill, th…
40 …mory write operations. If there are multiple misses in the TLB that are resolved by the refill, th…
|
| /linux/kernel/bpf/ |
| H A D | stackmap.c | 180 * vm_pgoff, file, build_id are set only when the build ID was resolved.
193 * resolved and the last VMA with no usable build ID. Adjacent stack frames tend
197 * last resolved build ID.
200 struct stack_map_cached_vma resolved; member
205 * Fill @id from a cached range covering @ip. On a hit this writes @id (resolved
215 vm_start = cache->resolved.vm_start; in stack_map_build_id_set_from_cache()
216 vm_end = cache->resolved.vm_end; in stack_map_build_id_set_from_cache()
218 vm_pgoff = cache->resolved.vm_pgoff; in stack_map_build_id_set_from_cache()
220 stack_map_build_id_set_valid(id, offset, cache->resolved.build_id); in stack_map_build_id_set_from_cache()
235 * Record @vma's build ID as the last resolved one. @file is the pinned backing
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-event_source-devices-hv_gpci | 99 HCALL with return error type "H_AUTHORITY" can be resolved during
131 HCALL with return error type "H_AUTHORITY" can be resolved during
163 HCALL with return error type "H_AUTHORITY" can be resolved during
195 HCALL with return error type "H_AUTHORITY" can be resolved during
227 HCALL with return error type "H_AUTHORITY" can be resolved during
|
| H A D | sysfs-firmware-ofw | 25 directory name is the resolved path component name (node
|
| /linux/tools/perf/pmu-events/arch/powerpc/power8/ |
| H A D | pipeline.json | 41 …"BriefDescription": "Completion stall by Dcache miss which resolved on chip ( excluding local L2/L…
47 "BriefDescription": "Completion stall by Dcache miss which resolved in L2/L3",
71 …"BriefDescription": "Completion stall by Dcache miss which resolved from remote chip (cache or mem…
72 …"PublicDescription": "Completion stall by Dcache miss which resolved on chip ( excluding local L2/…
|
| /linux/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/ |
| H A D | core-imp-def.json | 105 …cDescription": "No any micro operation is issued and meanwhile any load operation is not resolved",
108 …efDescription": "No any micro operation is issued and meanwhile any load operation is not resolved"
|
| /linux/arch/m68k/kernel/ |
| H A D | module.c | 40 undefined symbols have been resolved. */ in apply_relocate()
80 undefined symbols have been resolved. */ in apply_relocate_add()
|
| /linux/drivers/net/ethernet/sfc/ |
| H A D | tc_encap_actions.h | 22 * @dst_ip: the IPv4 destination address resolved by this neigh
23 * @dst_ip6: the IPv6 destination address resolved by this neigh
|
| /linux/tools/perf/pmu-events/arch/powerpc/power10/ |
| H A D | frontend.json | 115 …"BriefDescription": "A conditional branch finished with correctly predicted direction. Resolved ta…
120 …"BriefDescription": "A conditional branch finished with correctly predicted direction. Resolved no…
|
| /linux/Documentation/bpf/ |
| H A D | signing.rst | 43 - **kfunc and ksym references** are resolved to ids/addresses in the running
136 has resolved the ``fd_array`` entries into the program's ``used_maps``. The
166 verifier as usual; because that check runs while ``fd_array`` is resolved -
177 ksym or a BTF fd in ``fd_array``, whether resolved up front or lazily for a
411 **user/session key or keyring** that ``keyring_id`` resolved to - the
441 - serial of the resolved key/keyring
|
| /linux/Documentation/livepatch/ |
| H A D | module-elf-format.rst | 104 livepatch symbol. These must be resolved before livepatch can call
192 objects, whose addresses cannot be resolved by the module loader (because
199 symbols are resolved simply when the target module loads. In any case, for
201 section must be resolved before livepatch can call apply_relocate_add() for
|
| /linux/tools/testing/selftests/ftrace/test.d/ftrace/ |
| H A D | func_mod_trace.tc | 18 : "Wildcard should be resolved after loading module"
|
| /linux/Documentation/process/ |
| H A D | 6.Followthrough.rst | 100 anywhere? Most technical disagreements can be resolved through discussion,
115 most of the review issues have been resolved, the next step is usually
143 Now they can be resolved at leisure, before the merge window opens.
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | pyperf180.c | 12 * reduced some branch target distances and resolved the compilation failure.
|
| H A D | test_ksyms_weak.c | 20 /* test existing weak symbols can be resolved. */
|
| /linux/include/linux/ |
| H A D | hidden.h | 6 * may have symbol references that can only be resolved at load time. For a
|
| /linux/tools/net/ynl/pyynl/lib/ |
| H A D | nlspec.py | 402 where the ids of multicast groups get resolved at runtime. Value
510 resolved = []
522 resolved.append(elem)
524 if len(resolved) == 0:
|
| /linux/include/rdma/ |
| H A D | ib_addr.h | 26 * struct rdma_dev_addr - Contains resolved RDMA hardware addresses
65 * @addr: A reference to a data location that will receive the resolved
|
| /linux/arch/alpha/kernel/ |
| H A D | module.c | 163 unresolved symbols have been resolved. */ in apply_relocate_add()
206 value was resolved from somewhere else. */ in apply_relocate_add()
|
| /linux/tools/perf/util/ |
| H A D | llvm-c-helpers.h | 33 * If the address could not be resolved, or an error occurred (e.g. OOM),
|
| /linux/Documentation/networking/devlink/ |
| H A D | devlink-dpipe.rst | 156 interactions between tables can be resolved.
236 In case the egress RIF and destination MAC have been resolved by previous
|
| /linux/security/ipe/ |
| H A D | hooks.c | 69 * @prot: The effective protection on the mmap, resolved from reqprot and
97 * @prot: The effective protection on the mmap, resolved from reqprot and
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | fib_lookup.c | 131 * An error that returns after the egress device is resolved must
306 { .desc = "IPv4 VLAN input, neighbour resolved on the route",
318 * VRF: the resolved subinterface is enslaved, so the l3mdev rule
320 * the VRF table from the resolved ingress
331 { .desc = "IPv4 VLAN input, DIRECT uses VRF table from resolved ingress",
359 * resolved to that device and the lookup used it as ingress
915 * against this FIB, so without the route a kernel that resolved the in test_fib_lookup_vlan_netns()
|
| /linux/arch/openrisc/kernel/ |
| H A D | module.c | 36 undefined symbols have been resolved. */ in apply_relocate_add()
|