Home
last modified time | relevance | path

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

12

/tools/perf/
Dperf-with-kcore.sh121 …find "$USER_HOME/.debug" -xdev -type d ! -user "$SUDO_USER" -ls -exec chown "$SUDO_USE…
122 …find "$USER_HOME/.debug" -xdev -type f -links 1 ! -user "$SUDO_USER" -ls -exec chown "$SUDO_USE…
123 …find "$USER_HOME/.debug" -xdev -type l ! -user "$SUDO_USER" -ls -exec chown -h "$SUDO_USE…
140 PERMISSIONS_OK+=$(find "$HOME/.debug" -xdev -type d ! -user "$USER" -print -quit)
141 PERMISSIONS_OK+=$(find "$HOME/.debug" -xdev -type f -links 1 ! -user "$USER" -print -quit)
142 PERMISSIONS_OK+=$(find "$HOME/.debug" -xdev -type l ! -user "$USER" -print -quit)
Ddesign.txt54 exclude_user : 1, /* don't count user */
193 available to user-space using mmap() (see below).
223 CPU is in user, kernel and/or hypervisor mode.
253 gets schedule to. Per task counters can be created by any user, for
293 * Bits needed to read the hw counters in user-space.
389 * user;
/tools/testing/selftests/media_tests/
Dregression_test.txt2 and unregister paths. There have a few problems that result in user-after
18 Regressions test for cdev user-after free error on /dev/mediaX when driver
22 and cdev user-after-free fixes. This opens media dev files and sits in
27 The test for a random number of iterations or until user kills it with a
43 Run dmesg looking for any user-after free errors or mutex lock errors.
/tools/perf/Documentation/
DMakefile177 pdf: $(OUTPUT)user-manual.pdf
219 $(INSTALL) -m 644 $(OUTPUT)user-manual.pdf $(DESTDIR)$(pdfdir)
284 $(OUTPUT)user-manual.html: $(OUTPUT)user-manual.xml
287 $(OUTPUT)perf.info: $(OUTPUT)user-manual.texi
288 $(QUIET_MAKEINFO)$(MAKEINFO) --no-split -o $@ $(OUTPUT)user-manual.texi
290 $(OUTPUT)user-manual.texi: $(OUTPUT)user-manual.xml
292 $(DOCBOOK2X_TEXI) $(OUTPUT)user-manual.xml --encoding=UTF-8 --to-stdout >$@++ && \
297 $(OUTPUT)user-manual.pdf: $(OUTPUT)user-manual.xml
Dtips.txt25 To record every process run by an user: perf record -u <user>
34 Show user configuration overrides: perf config --user --list
Dperf-mem.txt56 --all-user::
57 Configure all used events to run in user space.
Dperf-script.txt140 warning is given to the user:
149 suppresses trace events. The user is given a warning message about
153 For the 'wildcard' option if a user selected field is invalid for an
154 event type, a message is displayed to the user that the option is
184 Finally, a user may not set fields to none for all event types.
Dperf-record.txt59 - 'stack-size': user stack size for dwarf mode
60 Note: If user explicitly sets options which conflict with the params,
65 the letter '@' is not interpreted in user space and sent down directly
226 platforms, such as Haswell. It can only get user call chain. It
229 When "dwarf" recording is used, perf also records (user) stack dump
325 - u: only when the branch target is at the user level
415 --all-user::
416 Configure all used events to run in user space.
Dperf-inject.txt20 Build-ids are just the first user of perf-inject - potentially anything that
Dperf-trace.txt126 Using this will, for the root user, bump the value of --mmap-pages to 4
128 sysctl. This is done only if the user doesn't specify a --mmap-pages value.
173 - addr level is either 'k' for kernel dso or '.' for user dso.
Dperf-config.txt24 --user::
25 For writing and reading options: write to user
37 The '$HOME/.perfconfig' file is used to store a per-user configuration.
41 When reading or writing, the values are read from the system and user
42 configuration files by default, and options '--system' and '--user'
184 The recording tools also stores a hard link or copy in a per-user
Dperf-script-perl.txt39 When perf script is invoked using a trace script, a user-defined
177 These functions provide some essential functions to user scripts.
191 common, but need to be made accessible to user scripts nonetheless.
Dperf-buildid-cache.txt32 not the user's. Use the -v option to see where the file is created.
Dperf-probe.txt100 can also list functions in a user space executable / shared library.
135 Specify path to the executable or shared library file for user
148 uses it as a target module/target user space binary to probe.
174 'SDTEVENT' and 'PROVIDER' is the pre-defined event name which is defined by user SDT (Statically De…
Dperf-list.txt33 more modifiers. Modifiers allow the user to restrict the events to be
36 u - user-space counting
84 OS/user mode flags must be setup using <<EVENT_MODIFIERS, EVENT
Dperf-report.txt93 - overhead_us: Overhead percentage of sample running in user mode
96 - overhead_guest_us: Overhead percentage of sample running in user mode on
148 supports substring match so user doesn't need to specify full subsystem
399 So user can use "call-graph=no" event modifier to disable callgraph
Dintel-pt.txt372 that in full trace we don't overwrite trace data that the user hasn't collected
389 If an unprivileged user does not specify mmap pages, the mmap pages will be
411 If an unprivileged user does not specify mmap pages, the mmap pages will be
413 user is likely to get an error as they exceed their mlock limit (Max locked
416 against the mlock limit so an unprivileged user is allowed 512KiB per cpu plus
559 debugfs is not mounted or the user does not have read-access, it will again not
638 Note, the sched_switch event is only added if the user is permitted to use it
/tools/perf/util/
Dprobe-event.h160 int show_line_range(struct line_range *lr, const char *module, bool user);
163 int show_available_funcs(const char *module, struct strfilter *filter, bool user);
178 struct map *get_target_map(const char *target, bool user);
Dprobe-event.c183 struct map *get_target_map(const char *target, bool user) in get_target_map() argument
186 if (user) in get_target_map()
430 const char *target, bool user) in get_alternative_line_range() argument
443 target, user); in get_alternative_line_range()
931 bool user) in __show_line_range() argument
948 ret = get_alternative_line_range(dinfo, lr, module, user); in __show_line_range()
1018 int show_line_range(struct line_range *lr, const char *module, bool user) in show_line_range() argument
1022 ret = init_probe_symbol_maps(user); in show_line_range()
1025 ret = __show_line_range(lr, module, user); in show_line_range()
1152 bool user __maybe_unused) in show_line_range()
[all …]
/tools/build/Documentation/
DBuild.txt7 Basically the user provides set of 'Build' files that list objects and
46 The user supplies 'Build' makefiles that contains a objects list, and connects
66 To follow the above example, the user provides following 'Build' files:
105 via user makefiles to get usefull definitions.
120 invoked by the user.
/tools/testing/selftests/breakpoints/
Dbreakpoint_test.c44 offsetof(struct user, u_debugreg[n]), addr); in set_breakpoint_addr()
87 offsetof(struct user, u_debugreg[7]), 0); in toggle_breakpoint()
107 offsetof(struct user, u_debugreg[7]), dr7); in toggle_breakpoint()
/tools/testing/selftests/
DMakefile30 TARGETS += user
/tools/thermal/tmon/
DREADME27 tui.c : handles ncurses based user interface
/tools/testing/selftests/ftrace/
DREADME10 At first, you need to be the root user to run this script.
/tools/testing/selftests/futex/
DREADME11 primitives. These can be used as is in user applications or can serve as

12