Home
last modified time | relevance | path

Searched refs:shared (Results 1 – 20 of 20) sorted by relevance

/tools/testing/selftests/powerpc/ptrace/
Dptrace-tm-spr.c11 struct shared { struct
18 struct shared *cptr, *pptr; argument
37 cptr = (struct shared *)shmat(shm_id, NULL, 0); in tm_spr()
117 shm_id = shmget(IPC_PRIVATE, sizeof(struct shared), 0777|IPC_CREAT); in ptrace_tm_spr()
129 pptr = (struct shared *)shmat(shm_id, NULL, 0); in ptrace_tm_spr()
/tools/testing/selftests/ptrace/
Dpeeksiginfo.c105 int check_direct_path(pid_t child, int shared, int nr) in check_direct_path() argument
112 if (shared == 1) { in check_direct_path()
137 shared, i, siginfo[j].si_code, siginfo[j].si_int); in check_direct_path()
/tools/virtio/ringtest/
DREADME2 Uses shared memory heavily.
/tools/testing/selftests/rseq/
DMakefile29 $(CC) $(CFLAGS) -shared -fPIC $< $(LDLIBS) -o $@
/tools/lib/traceevent/
DMakefile145 $(QUIET_LINK)$(CC) --shared $(LDFLAGS) $^ -Wl,-soname,libtraceevent.so.$(EP_VERSION) -o $@
153 $(QUIET_LINK)$(CC) $(CFLAGS) -shared $(LDFLAGS) -nostartfiles -o $@ $^
/tools/perf/Documentation/
Dperf-c2c.txt144 The perf c2c report command displays shared data analysis. It comes in two
225 - shared object name related to the 'Code address' value
257 dso - coalesced by shared object
270 - overall statistics on shared cachelines
Dperf-probe.txt100 can also list functions in a user space executable / shared library.
140 Specify path to the executable or shared library file for user
Dperf-config.txt228 Each executable and shared library in modern distributions comes with a
234 directory, $HOME/.debug/, of binaries, shared libraries, /proc/kallsyms
/tools/lib/lockdep/
DMakefile105 …$(CC) $(LDFLAGS) --shared $^ -o $@ -lpthread -ldl -Wl,-soname='$(@F)';$(shell ln -sf $(@F) $(@D)/l…
/tools/lib/traceevent/plugins/
DMakefile155 $(QUIET_LINK)$(CC) $(CFLAGS) -shared $(LDFLAGS) -nostartfiles -o $@ $^
/tools/perf/scripts/perl/Perf-Trace-Util/
DREADME29 generated e.g. blib and shared library, etc, except for of course
/tools/testing/selftests/futex/
DREADME26 shared object building and linking.
/tools/perf/lib/
DMakefile125 $(QUIET_LINK)$(CC) --shared -Wl,-soname,libperf.so \
/tools/lib/bpf/
DMakefile193 $(QUIET_LINK)$(CC) --shared -Wl,-soname,libbpf.so.$(LIBBPF_MAJOR_VERSION) \
/tools/testing/selftests/android/ion/
DREADME37 Thus the same kernel buffer is shared among two user space processes using
/tools/memory-model/Documentation/
Dexplanation.txt46 the modeling of bare C (or plain) shared memory accesses. It is meant
53 the basic notions shared by all such models. People already familiar
87 systems, with multiple CPUs making concurrent accesses to shared
107 and the flag are memory locations shared between the two CPUs.
141 shared memory locations and another CPU loads from those locations in
222 each CPU stores to its own shared location and then loads from the
292 Read events correspond to loads from shared memory, such as
296 Write events correspond to stores to shared memory, such as
311 shared memory, do not give rise to events. Thus, arithmetic and
316 gets stored to a shared memory location (or in the case of an array
[all …]
Drecipes.txt44 4. If there are multiple CPUs, accesses to shared variables should
49 i. When there is no possibility of a given shared variable
54 ii. When there is no possibility of a given shared variable
/tools/usb/usbip/
DREADME62 On a server side there are two entities which can be shared.
/tools/perf/
DMakefile.perf612 $(QUIET_LINK)$(CC) -o $@ -shared $(LDFLAGS) $(filter %.o,$^) $(GTK_LIBS)
722 $(QUIET_LINK)$(CC) $(LDFLAGS) -shared -Wl,-soname -Wl,$(LIBJVMTI) -o $@ $<
/tools/lib/traceevent/Documentation/
Dlibtraceevent.txt154 …Additional plugin directory. All shared object files, located in this directory will be loaded as …