Home
last modified time | relevance | path

Searched refs:precise (Results 1 – 25 of 70) sorted by relevance

123

/linux/kernel/bpf/
H A Dbacktrack.c678 if (reg->type != SCALAR_VALUE || reg->precise) in bpf_mark_all_scalars_precise()
680 reg->precise = true; in bpf_mark_all_scalars_precise()
690 if (reg->type != SCALAR_VALUE || reg->precise) in bpf_mark_all_scalars_precise()
692 reg->precise = true; in bpf_mark_all_scalars_precise()
854 reg->precise = true; in bpf_mark_chain_precision()
915 if (reg->precise) { in bpf_mark_chain_precision()
918 reg->precise = true; in bpf_mark_chain_precision()
935 if (reg->precise) { in bpf_mark_chain_precision()
938 reg->precise = true; in bpf_mark_chain_precision()
946 if (reg->type != SCALAR_VALUE || reg->precise) { in bpf_mark_chain_precision()
[all …]
H A Dstates.c551 if (!rold->precise && exact == NOT_EXACT) in regsafe()
1037 !state_reg->precise) in propagate_precision()
1054 !state_reg->precise) in propagate_precision()
1226 reg->precise = false; in mark_all_scalars_imprecise()
1234 reg->precise = false; in mark_all_scalars_imprecise()
/linux/tools/perf/Documentation/
H A Dperf-list.txt68 p - precise level
69 P - use maximum detected precise level
78 The 'p' modifier can be used for specifying how precise the instruction
87 For Intel systems precise event sampling is implemented with PEBS
88 which supports up to precise-level 2, and precise level 3 for
91 On AMD systems it is implemented using IBS OP (up to precise-level 2).
93 inherently non-precise and IBS is inherently precise. (i.e. ibs_op//,
94 ibs_op//p, ibs_op//pp and ibs_op//ppp are all same). The precise modifier
H A Dperf-amd-ibs.txt17 Instruction-Based Sampling (IBS) provides precise Instruction Pointer (IP)
20 execution (micro-op execution to be precise) with details like d-cache
42 IBS gives samples with precise IP, i.e. the IP recorded with IBS sample has
/linux/tools/perf/util/
H A Dparse-events.l135 struct parse_events_modifier mod = { .precise = 0, }; in modifiers()
155 mod.precise++; in modifiers()
166 if (mod.precise > 3) { in modifiers()
H A Dparse-events.h199 u8 precise; /* Number of repeated 'p' for precision. */ member
H A Dparse-events.c1856 if (mod.precise) { in parse_events__modifier_list()
1857 u8 precise = evsel->core.attr.precise_ip + mod.precise; in parse_events__modifier_list() local
1859 * precise ip: in parse_events__modifier_list()
1868 if (precise > 3) { in parse_events__modifier_list()
1872 "Maximum combined precise value is 3, adding precision to \"%s\"", in parse_events__modifier_list()
1880 evsel->core.attr.precise_ip = precise; in parse_events__modifier_list()
2447 * we have the precise error. in __parse_events_error__print()
/linux/Documentation/features/time/irq-time-acct/
H A Darch-support.txt4 # description: arch supports precise IRQ time accounting
/linux/Documentation/features/time/virt-cpuacct/
H A Darch-support.txt4 # description: arch supports precise virtual CPU time accounting
/linux/tools/testing/selftests/rcutorture/doc/
H A Drcu-test-image.txt39 # Replace "precise" below with your favorite Ubuntu release.
42 sudo debootstrap --verbose --arch i386 precise /mnt http://archive.ubuntu.com/ubuntu
/linux/tools/tracing/rtla/
H A DREADME.txt5 rtla leverages kernel tracing capabilities to provide precise information
/linux/Documentation/userspace-api/media/rc/
H A Dlirc-set-wideband-receiver.rst41 also be more precise. On the other hand its disadvantage it usually
/linux/Documentation/userspace-api/media/v4l/
H A Dv4l2-selection-targets.rst10 The precise meaning of the selection targets may be dependent on which
H A Dmetafmt-uvc.rst19 timing information, required for precise interpretation of timestamps, contained
H A Dvidioc-query-dv-timings.rst66 precise feedback to the user.
/linux/tools/testing/selftests/kvm/x86/
H A Dprivate_mem_conversions_test.c230 static void guest_test_punch_hole(u64 base_gpa, bool precise) in guest_test_punch_hole() argument
254 if (precise) { in guest_test_punch_hole()
/linux/Documentation/admin-guide/media/
H A Dfimc.rst90 In order to enable more precise camera pipeline control through the sub-device
128 more precise FIMC capture subsystem control. In addition a separate v4l2
/linux/Documentation/arch/sparc/
H A Dadi.rst124 MCD precise exception is enabled (MCDPERR=1), a precise
136 ADI tag mismatch on a load always results in precise trap.
/linux/Documentation/timers/
H A Dhrtimers.rst60 users like drivers and subsystems which require precise timed events
68 with other potential users for precise timers gives another reason to
69 separate the "timeout" and "precise timer" subsystems.
/linux/tools/perf/pmu-events/
H A Djevents.py337 precise = jd.get('PEBS')
342 extra_desc += ' Supports address when precise'
370 if precise and self.desc and '(Precise Event)' not in self.desc:
371 extra_desc += ' (Must be precise)' if precise == '2' else (' (Precise '
/linux/Documentation/core-api/
H A Dnetlink.rst47 to take effect. This is useful for programs that need precise feedback
/linux/Documentation/sound/cards/
H A Dhdspm.rst79 precise-pointer.
357 Enable precise pointer, or disable.
/linux/Documentation/firmware-guide/acpi/apei/
H A Doutput_format.rst61 [restartable][, precise IP][, overflow][, corrected]
/linux/Documentation/arch/x86/
H A Dtlb.rst16 it is a much more precise operation, causing no collateral
/linux/Documentation/sound/designs/
H A Dtimestamping.rst13 and precise moment. Applications should not rely solely on the first
108 precise start time (patches WIP)

123