Home
last modified time | relevance | path

Searched refs:hits (Results 1 – 39 of 39) sorted by relevance

/linux-4.1.27/kernel/
Dprofile.c33 u32 pc, hits; member
252 struct profile_hit *hits = per_cpu(cpu_profile_hits, cpu)[j]; in profile_flip_buffers() local
254 if (!hits[i].hits) { in profile_flip_buffers()
255 if (hits[i].pc) in profile_flip_buffers()
256 hits[i].pc = 0; in profile_flip_buffers()
259 atomic_add(hits[i].hits, &prof_buffer[hits[i].pc]); in profile_flip_buffers()
260 hits[i].hits = hits[i].pc = 0; in profile_flip_buffers()
275 struct profile_hit *hits = per_cpu(cpu_profile_hits, cpu)[i]; in profile_discard_flip_buffers() local
276 memset(hits, 0, NR_PROFILE_HIT*sizeof(struct profile_hit)); in profile_discard_flip_buffers()
285 struct profile_hit *hits; in do_profile_hits() local
[all …]
/linux-4.1.27/fs/
Dfs_struct.c67 int hits = 0; in chroot_fs_refs() local
70 hits += replace_path(&fs->root, old_root, new_root); in chroot_fs_refs()
71 hits += replace_path(&fs->pwd, old_root, new_root); in chroot_fs_refs()
73 while (hits--) { in chroot_fs_refs()
/linux-4.1.27/tools/perf/Documentation/
Dperf-buildid-list.txt25 --with-hits::
26 Show only DSOs with hits.
Dperf-archive.txt15 This command runs perf-buildid-list --with-hits, and collects the files with the
/linux-4.1.27/tools/power/cpupower/utils/idle_monitor/
Dcpupower-monitor.c214 int mon, hits = 0; in parse_monitor_param() local
232 tmp_mons[hits] = monitors[num]; in parse_monitor_param()
233 hits++; in parse_monitor_param()
237 if (hits == 0) { in parse_monitor_param()
245 avail_monitors = hits; in parse_monitor_param()
/linux-4.1.27/Documentation/trace/
Dkprobetrace.txt89 You can check the total number of probe hits and probe miss-hits via
91 The first column is event name, the second is the number of probe hits,
92 the third is the number of probe miss-hits.
169 Each line shows when the kernel hits an event, and <- SYMBOL means kernel
Duprobetracer.txt63 You can check the total number of probe hits and probe miss-hits via
65 The first column is event name, the second is the number of probe hits,
66 the third is the number of probe miss-hits.
/linux-4.1.27/tools/perf/ui/gtk/
Dhists.c104 u64 hits, child_total; in perf_gtk__add_callchain() local
108 hits = callchain_cumul_hits(node); in perf_gtk__add_callchain()
109 percent = 100.0 * hits / total; in perf_gtk__add_callchain()
/linux-4.1.27/tools/perf/
Dperf-archive.sh24 perf buildid-list -i $PERF_DATA --with-hits | grep -v "^$NOBUILDID " > $BUILDIDS
Dbuiltin-record.c479 int hits = rec->samples; in __cmd_record() local
486 if (hits == rec->samples) { in __cmd_record()
Dbuiltin-top.c995 u64 hits = top->samples; in __cmd_top() local
999 if (hits == top->samples) in __cmd_top()
/linux-4.1.27/lib/
Dlru_cache.c214 lc->hits = 0; in lc_reset()
252 lc->hits, lc->misses, lc->starving, lc->locked, lc->changed); in lc_seq_printf_stats()
401 ++lc->hits; in __lc_get()
405 ++lc->hits; in __lc_get()
/linux-4.1.27/Documentation/devicetree/bindings/arc/
Dpct.txt4 CPU and cache events like cache misses and hits. Like conventional PCT there
/linux-4.1.27/scripts/coccinelle/misc/
Dreturnvar.cocci8 // "when strict" can be removed to get more hits, but adds false
/linux-4.1.27/include/linux/
Dlru_cache.h208 unsigned long hits, misses, starving, locked, changed; member
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Dpmu.txt4 and hits. The interface to the PMU is part of the ARM ARM. The ARM PMU
/linux-4.1.27/Documentation/device-mapper/
Dcache.txt88 forwarded to the origin device; additionally, write hits cause cache
221 <#read hits> <#read misses> <#write hits> <#write misses>
233 #read hits : Number of times a READ bio has been mapped
237 #write hits : Number of times a WRITE bio has been mapped
/linux-4.1.27/drivers/acpi/acpica/
Dutcache.c272 ACPI_MEM_TRACKING(cache->hits++); in acpi_os_acquire_object()
/linux-4.1.27/Documentation/fb/
Dcmap_xfbdev.txt35 colormap. For example, Xfbdev hits the following:
/linux-4.1.27/tools/perf/ui/stdio/
Dhist.c39 u64 total_samples, u64 hits, in ipchain__fprintf_graph() argument
55 percent = hits * 100.0 / total_samples; in ipchain__fprintf_graph()
/linux-4.1.27/drivers/media/rc/
Dimon.c1197 static int x, y, prev_result, hits; in stabilize() local
1208 hits = 0; in stabilize()
1226 hits++; in stabilize()
1228 if (hits > 3) { in stabilize()
1245 if (hits == 2 && msec_hit < timeout) { in stabilize()
1247 hits = 1; in stabilize()
1251 hits = 1; in stabilize()
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-block-bcache28 For backing devices: integer number of full cache hits,
41 For backing devices: cache hits as a percentage.
/linux-4.1.27/Documentation/cgroups/
Dmemory.txt66 memory.failcnt # show the number of memory usage hits limits
67 memory.memsw.failcnt # show the number of memory+Swap hits limits
83 memory.kmem.failcnt # show the number of kernel memory usage hits limits
88 memory.kmem.tcp.failcnt # show the number of tcp buf memory usage hits limits
234 * What happens when a cgroup hits memory.memsw.limit_in_bytes
235 When a cgroup hits memory.memsw.limit_in_bytes, it's useless to do swap-out
344 triggered for a cgroup when it hits K while staying below U, which makes
553 hit its limit. When a memory cgroup hits a limit, failcnt increases and
/linux-4.1.27/drivers/uwb/
Duwb-internal.h283 u8 hits; member
/linux-4.1.27/net/netfilter/
Dxt_recent.c297 unsigned int i, hits = 0; in recent_mt() local
302 if (!info->hit_count || ++hits >= info->hit_count) { in recent_mt()
/linux-4.1.27/arch/sh/kernel/cpu/sh3/
Dentry.S98 ! TLB hits, but the access violate the protection.
/linux-4.1.27/tools/perf/util/
Dannotate.c671 unsigned int hits = 0; in disasm__calc_percent() local
674 hits += h->addr[offset++]; in disasm__calc_percent()
677 percent = 100.0 * hits / h->sum; in disasm__calc_percent()
/linux-4.1.27/Documentation/
Dkprobes.txt62 When a CPU hits the breakpoint instruction, a trap occurs, the CPU's
537 so keep this in mind if you're not seeing the probe hits you expect.
549 probe handler. If a probe handler hits a probe, that second probe's
624 microseconds to process. Specifically, a benchmark that hits the same
626 million hits per second, depending on the architecture. A jprobe or
/linux-4.1.27/include/net/
Dneighbour.h119 unsigned long hits; /* number of hits (among lookups) */ member
/linux-4.1.27/Documentation/input/
Dntrig.txt82 events until it hits thresholds and begins propagating. In the interest in
/linux-4.1.27/include/acpi/
Dactypes.h1243 u32 hits; member
/linux-4.1.27/net/core/
Dneighbour.c408 NEIGH_CACHE_STAT_INC(tbl, hits); in neigh_lookup()
437 NEIGH_CACHE_STAT_INC(tbl, hits); in neigh_lookup_nodev()
1844 ndst.ndts_hits += st->hits; in neightbl_fill_info()
2730 st->hits, in neigh_stat_seq_show()
/linux-4.1.27/security/selinux/
Dselinuxfs.c1409 unsigned int hits = lookups - misses; in sel_avc_stats_seq_show() local
1411 hits, misses, st->allocations, in sel_avc_stats_seq_show()
/linux-4.1.27/Documentation/timers/
Dtimekeeping.txt152 independently on each CPU without any synchronization performance hits.
/linux-4.1.27/Documentation/locking/
Dww-mutex-design.txt233 when the dynamic locking step hits -EDEADLK we also need to unlock all the
/linux-4.1.27/Documentation/scsi/
Dscsi_mid_low_api.txt186 scsi_host_put() when the reference count hits zero.
/linux-4.1.27/Documentation/block/
Dbiodoc.txt447 atomic_t bi_cnt; /* pin count: free when it hits zero */
/linux-4.1.27/arch/arm/
DKconfig1577 code which hits this problem, at the cost of a bit of extra runtime
/linux-4.1.27/Documentation/s390/
DDebugging390.txt873 To make VM display a message each time it hits a particular address and