CoreSight January 2017

coresight@lists.linaro.org

10 participants
13 discussions

[PATCH 0/2] Support generation of last branch events with perf inject

by Sebastian Pop

The first patch is a minor typo to allow printing the trace info. The second patch enables translation of perf.data files into last branch events that are then processed by the autoFDO tool to extract a coverage file. Sebastian Pop (2): perf tools: fix printing of auxtrace_info perf tools: new inject capabilitity for CoreSight traces tools/perf/Documentation/cs-etm.txt | 38 +++++++++ tools/perf/util/cs-etm.c | 163 ++++++++++++++++++++++++++++++++++-- 2 files changed, 196 insertions(+), 5 deletions(-) create mode 100644 tools/perf/Documentation/cs-etm.txt -- 2.6.3

7 years, 7 months

Re: CoreSight post from yan_lin_aung@yahoo.com requires approval

by Mathieu Poirier

On 11 November 2016 at 06:45, Yan Lin Aung <yan_lin_aung(a)yahoo.com> wrote: > Hi Mathieu, > > I have made progress with getting things up. > > I now switched to another platform with quad-core A53 processors because > the Juno r2 environment is a bit difficult for me to work with. > > The following describes the steps taken: > > 1) I have Linux 4.4.23 running on quad-core A53. CoreSight is enabled. > I can see CoreSight components under "/sys/bus/coresight/devices" > > linaro@linaro-alip:~/OpenCSD-perf-opencsd-4.9-rc1/tools/perf$ ls > /sys/bus/coresight/devices/ > 820000.tpiu 821000.funnel 824000.replicator 825000.etf 826000.etr > 841000.funnel 85c000.etm 85d000.etm 85e000.etm 85f000.etm > > > I can enable/disable ETM and ETR (e.g. echo 1 > 85c000.etm/enable_source, > cat 85c000.etm/enable_source). Ok, but that is not required since identification of the sink to use is now done from the perf cmd line. > > 2) I am able to build OpenCSD library. Then, share libraries > (libcstraced_c_api.so, libcstraced.so) are copied to "/usr/lib". > Then, I tried testing the library by running "c_api_pkt_print_test". Below > shows the sample outputs. > > C-API packet print test > Library Version 0.4.2 > > Idx:86; I_NOT_SYNC : I Stream not synchronised > Idx:1650; I_ASYNC : Alignment Synchronisation. > Idx:1662; I_TRACE_INFO : Trace Info. > Idx:1666; I_ADDR_L_64IS0 : Address, Long, 64 bit, IS0.; > Addr=0xFFFFFFC000096A00; > Idx:1675; I_TRACE_ON : Trace On. > Idx:1676; I_ADDR_CTXT_L_64IS0 : Address & Context, Long, 64 bit, IS0.; > Addr=0xFFFFFFC000096A00; Ctxt: AArch64,EL1, NS; CID=0x00000000; VMID=0x0000; > Idx:1692; I_ATOM_F1 : Atom format 1.; E > Idx:1693; I_ADDR_L_64IS0 : Address, Long, 64 bit, IS0.; > Addr=0xFFFFFFC000594AC0; > Idx:1703; I_ATOM_F1 : Atom format 1.; E > Idx:1704; I_ADDR_S_IS0 : Address, Short, IS0.; Addr=0xFFFFFFC000592B58 > ~[0x12B58] > Idx:1707; I_ATOM_F3 : Atom format 3.; ENN > Idx:1708; I_ATOM_F1 : Atom format 1.; E > Idx:1709; I_ADDR_L_32IS0 : Address, Long, 32 bit, IS0.; Addr=0x005AC4C8; > Idx:1715; I_ATOM_F2 : Atom format 2.; EE > Idx:1716; I_ADDR_L_32IS0 : Address, Long, 32 bit, IS0.; Addr=0x000EA588; > Idx:1721; I_ATOM_F3 : Atom format 3.; NNE > Idx:1722; I_ADDR_L_32IS0 : Address, Long, 32 bit, IS0.; Addr=0x00592B60; > > > 3) Then, perf tool under the "OpenCSD-perf-opencsd-4.9-rc1" branch is > compiled on target. > The following is the compilation log. It seems to me there is no issue with > compilation ("CC util/cs-etm-decoder/cs-etm-decoder.o" is compiled > properly). I also exported "CSTRACE_PATH=/home/linaro/OpenCSD-0.4.2/decoder" > before compilation. > > linaro@linaro-alip:~/OpenCSD-perf-opencsd-4.9-rc1$ make -C tools/perf/ > make: Entering directory > '/home/linaro/OpenCSD-perf-opencsd-4.9-rc1/tools/perf' > BUILD: Doing 'make -j4' parallel build > > Auto-detecting system features: > ... dwarf: [ on ] > ... dwarf_getlocations: [ on ] > ... glibc: [ on ] > ... gtk2: [ on ] > ... libaudit: [ on ] > ... libbfd: [ on ] > ... libelf: [ on ] > ... libnuma: [ on ] > ... numa_num_possible_cpus: [ on ] > ... libperl: [ on ] > ... libpython: [ on ] > ... libslang: [ on ] > ... libcrypto: [ on ] > ... libunwind: [ on ] > ... libdw-dwarf-unwind: [ on ] > ... zlib: [ on ] > ... lzma: [ on ] > ... get_cpuid: [ OFF ] > ... bpf: [ on ] > > Makefile.config:349: BPF prologue is not supported by architecture arm64, > missing regs_query_register_offset() > Makefile.config:400: No debug_frame support found in libunwind-aarch64 > Makefile.config:459: No debug_frame support found in libunwind > GEN common-cmds.h > HOSTCC fixdep.o > HOSTCC pmu-events/json.o > HOSTLD fixdep-in.o > LINK fixdep > HOSTCC pmu-events/jsmn.o > HOSTCC pmu-events/jevents.o > CC fd/array.o > CC fs/fs.o > HOSTLD pmu-events/jevents-in.o > CC event-parse.o > LD fd/libapi-in.o > CC cpu.o > CC debug.o > CC str_error_r.o > CC fs/tracing_path.o > CC exec-cmd.o > PERF_VERSION = 4.9.0-rc1 > Warning: tools/include/uapi/linux/bpf.h differs from kernel > CC libbpf.o > LD fs/libapi-in.o > LD libapi-in.o > AR libapi.a > CC bpf.o > CC help.o > CC pager.o > LD libbpf-in.o > LINK libbpf.a > LINK pmu-events/jevents > CC event-plugin.o > CC plugin_jbd2.o > CC parse-options.o > LD plugin_jbd2-in.o > CC plugin_hrtimer.o > LD plugin_hrtimer-in.o > CC trace-seq.o > CC plugin_kmem.o > CC run-command.o > LD plugin_kmem-in.o > CC plugin_kvm.o > CC parse-filter.o > CC sigchain.o > LD plugin_kvm-in.o > CC plugin_mac80211.o > LD plugin_mac80211-in.o > CC plugin_sched_switch.o > CC plugin_function.o > CC parse-utils.o > LD plugin_sched_switch-in.o > CC plugin_xen.o > LD plugin_xen-in.o > CC plugin_scsi.o > LD plugin_function-in.o > CC plugin_cfg80211.o > CC kbuffer-parse.o > LD plugin_scsi-in.o > LD plugin_cfg80211-in.o > LINK plugin_jbd2.so > LINK plugin_hrtimer.so > LINK plugin_kmem.so > LINK plugin_kvm.so > LINK plugin_mac80211.so > LD libtraceevent-in.o > LINK libtraceevent.a > LINK plugin_sched_switch.so > GEN perf-archive > LINK plugin_function.so > GEN perf-with-kcore > CC ui/gtk/browser.o > LINK plugin_xen.so > LINK plugin_scsi.so > LINK plugin_cfg80211.so > CC subcmd-config.o > CC ui/gtk/hists.o > LD libsubcmd-in.o > CC util/alias.o > AR libsubcmd.a > Warning: tools/arch/x86/lib/memcpy_64.S differs from kernel > Warning: tools/arch/x86/lib/memset_64.S differs from kernel > Warning: tools/arch/arm/include/uapi/asm/kvm.h differs from kernel > CC util/annotate.o > Warning: tools/include/uapi/asm-generic/mman-common.h differs from kernel > CC builtin-bench.o > CC builtin-annotate.o > CC ui/gtk/setup.o > CC ui/gtk/util.o > CC builtin-config.o > CC builtin-diff.o > CC util/block-range.o > CC ui/gtk/helpline.o > CC arch/common.o > CC util/build-id.o > CC arch/arm64/util/dwarf-regs.o > CC arch/arm64/util/unwind-libunwind.o > CC ui/gtk/progress.o > CC builtin-evlist.o > CC arch/arm64/util/../../arm/util/pmu.o > CC util/config.o > CC arch/arm64/util/../../arm/util/auxtrace.o > CC builtin-help.o > CC ui/gtk/annotate.o > CC arch/arm64/util/../../arm/util/cs-etm.o > CC builtin-sched.o > CC util/ctype.o > LD arch/arm64/util/libperf-in.o > CC arch/arm64/tests/regs_load.o > CC arch/arm64/tests/dwarf-unwind.o > CC util/db-export.o > LD ui/gtk/gtk-in.o > LD arch/arm64/tests/libperf-in.o > LD arch/arm64/libperf-in.o > LD arch/libperf-in.o > CC ui/setup.o > CC util/env.o > CC ui/helpline.o > LD gtk-in.o > GEN pmu-events/pmu-events.c > CC pmu-events/pmu-events.o > LD pmu-events/pmu-events-in.o > CC ui/progress.o > CC util/event.o > CC ui/util.o > GEN libtraceevent-dynamic-list > CC ui/hist.o > CC ui/stdio/hist.o > CC builtin-buildid-list.o > CC builtin-buildid-cache.o > CC builtin-list.o > CC ui/browser.o > CC util/evlist.o > CC builtin-record.o > CC builtin-report.o > CC ui/browsers/annotate.o > CC ui/browsers/hists.o > CC util/evsel.o > CC builtin-stat.o > CC builtin-timechart.o > CC builtin-top.o > CC util/evsel_fprintf.o > CC builtin-script.o > CC util/find_bit.o > CC util/kallsyms.o > CC util/levenshtein.o > CC util/llvm-utils.o > BISON util/parse-events-bison.c > CC builtin-kmem.o > CC ui/browsers/map.o > CC util/perf_regs.o > CC util/path.o > CC ui/browsers/scripts.o > CC util/rbtree.o > CC ui/browsers/header.o > CC util/libstring.o > CC builtin-lock.o > CC util/bitmap.o > LD ui/browsers/libperf-in.o > CC util/hweight.o > CC ui/tui/setup.o > CC util/quote.o > CC util/strbuf.o > CC ui/tui/util.o > CC util/string.o > CC builtin-kvm.o > CC builtin-inject.o > CC ui/tui/helpline.o > CC util/strlist.o > CC ui/tui/progress.o > CC util/strfilter.o > LD ui/tui/libperf-in.o > LD ui/libperf-in.o > GEN python/perf.so > CC scripts/perl/Perf-Trace-Util/Context.o > CC builtin-mem.o > CC util/top.o > LD scripts/perl/Perf-Trace-Util/libperf-in.o > CC scripts/python/Perf-Trace-Util/Context.o > CC builtin-data.o > CC util/usage.o > LD scripts/python/Perf-Trace-Util/libperf-in.o > LD scripts/libperf-in.o > CC builtin-version.o > CC builtin-trace.o > CC util/dso.o > CC builtin-probe.o > CC bench/sched-messaging.o > CC bench/sched-pipe.o > CC util/symbol.o > CC bench/mem-functions.o > CC bench/futex-hash.o > CC bench/futex-wake.o > CC bench/futex-wake-parallel.o > CC bench/futex-requeue.o > CC util/symbol_fprintf.o > CC util/color.o > CC bench/futex-lock-pi.o > CC bench/numa.o > CC util/header.o > CC util/callchain.o > CC util/values.o > LD bench/perf-in.o > CC tests/builtin-test.o > CC tests/parse-events.o > CC perf.o > CC util/debug.o > CC util/machine.o > CC util/map.o > CC util/pstack.o > CC tests/dso-data.o > CC util/session.o > CC tests/attr.o > CC util/syscalltbl.o > CC tests/vmlinux-kallsyms.o > CC util/ordered-events.o > CC tests/openat-syscall.o > CC tests/openat-syscall-all-cpus.o > CC tests/openat-syscall-tp-fields.o > CC tests/mmap-basic.o > CC util/comm.o > CC tests/perf-record.o > CC util/thread.o > CC tests/evsel-roundtrip-name.o > CC tests/evsel-tp-sched.o > CC tests/fdarray.o > CC util/thread_map.o > CC tests/pmu.o > CC tests/hists_common.o > CC util/trace-event-parse.o > CC tests/hists_link.o > CC util/parse-events-bison.o > BISON util/pmu-bison.c > CC util/trace-event-read.o > CC util/trace-event-info.o > CC tests/hists_filter.o > CC util/trace-event-scripting.o > CC util/trace-event.o > CC tests/hists_output.o > CC tests/hists_cumulate.o > CC util/svghelper.o > CC tests/python-use.o > CC tests/bp_signal.o > CC tests/bp_signal_overflow.o > CC tests/task-exit.o > CC tests/sw-clock.o > CC tests/mmap-thread-lookup.o > CC util/sort.o > CC util/hist.o > CC tests/thread-mg-share.o > CC tests/switch-tracking.o > CC util/util.o > CC tests/keep-tracking.o > CC util/xyarray.o > CC tests/code-reading.o > CC tests/sample-parsing.o > CC tests/parse-no-sample-id-all.o > CC tests/kmod-path.o > CC tests/thread-map.o > CC util/cpumap.o > CC util/cgroup.o > CC tests/llvm.o > CC util/target.o > CC tests/bpf.o > CC tests/topology.o > CC util/rblist.o > CC util/intlist.o > CC util/vdso.o > CC util/counts.o > CC tests/cpumap.o > CC tests/stat.o > CC tests/event_update.o > CC tests/event-times.o > CC util/stat.o > CC util/stat-shadow.o > CC tests/backward-ring-buffer.o > CC tests/sdt.o > CC tests/is_printable_array.o > CC tests/bitmap.o > CC tests/dwarf-unwind.o > CC tests/llvm-src-base.o > CC util/record.o > CC tests/llvm-src-kbuild.o > CC tests/llvm-src-prologue.o > CC tests/llvm-src-relocation.o > CC util/srcline.o > CC util/data.o > LD tests/perf-in.o > CC util/tsc.o > CC util/cloexec.o > CC util/call-path.o > CC util/thread-stack.o > CC util/auxtrace.o > CC util/intel-pt-decoder/intel-pt-pkt-decoder.o > LD perf-in.o > GEN util/intel-pt-decoder/inat-tables.c > CC util/intel-pt-decoder/intel-pt-log.o > CC util/intel-pt-decoder/intel-pt-decoder.o > CC util/intel-pt-decoder/intel-pt-insn-decoder.o > CC util/cs-etm-decoder/cs-etm-decoder.o > LD util/cs-etm-decoder/libperf-in.o > CC util/scripting-engines/trace-event-perl.o > CC util/scripting-engines/trace-event-python.o > CC util/intel-pt.o > LD util/intel-pt-decoder/libperf-in.o > CC util/intel-bts.o > CC util/cs-etm.o > LD util/scripting-engines/libperf-in.o > CC util/parse-branch-options.o > CC util/parse-regs-options.o > CC util/term.o > CC util/help-unknown-cmd.o > CC util/mem-events.o > CC util/vsprintf.o > CC util/drv_configs.o > CC util/bpf-loader.o > CC util/symbol-elf.o > CC util/probe-file.o > CC util/probe-event.o > CC util/probe-finder.o > CC util/dwarf-aux.o > CC util/dwarf-regs.o > CC util/unwind-libunwind-local.o > CC util/unwind-libunwind.o > CC util/libunwind/arm64.o > CC util/zlib.o > CC util/lzma.o > CC util/demangle-java.o > CC util/demangle-rust.o > CC util/jitdump.o > CC util/genelf.o > CC util/genelf_debug.o > FLEX util/parse-events-flex.c > FLEX util/pmu-flex.c > CC util/parse-events.o > CC util/pmu-bison.o > CC util/parse-events-flex.o > CC util/pmu.o > CC util/pmu-flex.o > LD util/libperf-in.o > LD libperf-in.o > AR libperf.a > LINK perf > LINK libperf-gtk.so > make: Leaving directory > '/home/linaro/OpenCSD-perf-opencsd-4.9-rc1/tools/perf' > > 4) Then, I test the perf as follows: > > linaro@linaro-alip:~/OpenCSD-perf-opencsd-4.9-rc1/tools/perf$ ./perf record > -e cs_etm/(a)826000.etr/ --per-thread uname > invalid or unsupported event: 'cs_etm/(a)826000.etr/' > Run 'perf list' for a list of valid events > > Usage: perf record [<options>] [<command>] > or: perf record [<options>] -- <command> [<options>] > > -e, --event <event> event selector. use 'perf list' to list available > events > > It seems that "perf" is not able to populate the cs_etm events. "perf list" > output shows: > > linaro@linaro-alip:~/OpenCSD-perf-opencsd-4.9-rc1/tools/perf$ ./perf list > > List of pre-defined events (to be used in -e): > > branch-misses [Hardware event] > cache-misses [Hardware event] > cache-references [Hardware event] > cpu-cycles OR cycles [Hardware event] > instructions [Hardware event] > > alignment-faults [Software event] > bpf-output [Software event] > context-switches OR cs [Software event] > cpu-clock [Software event] > cpu-migrations OR migrations [Software event] > dummy [Software event] > emulation-faults [Software event] > major-faults [Software event] > minor-faults [Software event] > page-faults OR faults [Software event] > task-clock [Software event] > > L1-dcache-load-misses [Hardware cache event] > L1-dcache-loads [Hardware cache event] > L1-dcache-store-misses [Hardware cache event] > L1-dcache-stores [Hardware cache event] > branch-load-misses [Hardware cache event] > branch-loads [Hardware cache event] > > rNNN [Raw hardware event > descriptor] > cpu/t1=v1[,t2=v2,t3 ...]/modifier [Raw hardware event > descriptor] > (see 'man perf-list' on how to encode it) > > mem:<addr>[/len][:access] [Hardware breakpoint] > > I think I am very close to getting things up properly. Also, I need to get > this working for a research work here. > > Any idea on why "perf" is not showing the events corresponding to "cs_etm"? > Where possibly is the issue? > Your kind help on this will be very much appreciated. Did you get the kernel from github as per my previous email? Kernel 4.4.23 is very old and doesn't have all of the CoreSight features required to integrate with perf. Also, keep in mind that since you are not working with Juno CPUIdle _needs_ to be disabled and you have to do make sure all power domains and clocks for the CoreSight IP blocks are managed properly. Out of curiosity, what platform is this? Mathieu > > Looking forward to hear from you and thanks. > > > Regards, > Yan Lin Aung > > On Thursday, November 10, 2016 12:23 AM, Mathieu Poirier > <mathieu.poirier(a)linaro.org> wrote: > > > On 9 November 2016 at 08:06, Yan Lin Aung <yan_lin_aung(a)yahoo.com> wrote: >> Hi Mathieu, >> >> Thanks for your reply. Sorry for a bit of delay on my response. >> >> Just a bit of intro on myself. I am a research staff from Nanyang >> Technological University, Singapore. >> >> Basically, I used the build scripts provided with Linaro deliverables for >> Juno and TC2 from ARM >> at this link: https://community.arm.com/docs/DOC-10803 >> >> I am able to get the system running either with prebuilt binaries or >> building from source. >> For Linaro release 16.09 with built from source option, the Linux 4.8.x >> runs >> on Juno r2. >> In the default configuration, coresight was not activated. >> I tried to update the config file to enable coresight drive and >> recompiled. >> However, the coresight devices are not populated somehow. >> >> I would like to have a setup with which I will be able to do some >> experiments as demonstrated in your presentation at the very minimum. >> So, my specific question will be that how shall I proceed to get >> coresight, >> perf with coresight and OpenCSD working properly >> using the Linaro release 16.09. > > You won't have the required pieces in 16.09. To replicate the > examples shown in the presentation you will have to use the kernel > found on github [1]. Since you have a Juno R2 I suggest to use branch > perf-opencsd-4.9-rc1 - that way you won't have to deal with power > domain management. Note that CoreSight is not part of the default V8 > configuration as needs to be explicitly enabled. > > Thanks, > Mathieu > > [1]. https://github.com/Linaro/OpenCSD > > >> >> If you are not using Linaro release 16.09 and have other means of getting >> things up with coresight, perf and OpenCSD on Juno, please kindly share >> with >> me. I am quite keen to follow your steps and try it out at my side here. >> >> Looking forward to hear from you and thanks. >> >> Regards, >> Yan Lin Aung >> >> >> >> >> >> >> >> >> >> On Monday, November 7, 2016 11:32 PM, Mathieu Poirier >> <mathieu.poirier(a)linaro.org> wrote: >> >> >>> ---------- Forwarded message ---------- >>> From: Yan Lin Aung <yan_lin_aung(a)yahoo.com> >>> To: "coresight(a)lists.linaro.org" <coresight(a)lists.linaro.org> >>> Cc: >>> Date: Mon, 7 Nov 2016 03:45:45 +0000 (UTC) >>> Subject: perf with CoreSight and OpenCSD on TC2 and Juno r2 >>> Hi Linaro Coresight Team, >>> >>> I came to know of "Hardware Assisted Tracing on ARM with CoreSight and >>> OpenCSD" by Mathieu Poirier. >>> In his presentation, he mentioned the reference platforms to evaluate >>> perf >>> with CoreSight and OpenCSD are Vexpress TC2 and Juno (Page 7 on his >>> slide). >>> >>> I just checked the "HOWTO.MD" at OpenCSD github site. >>> However, there is very limited info on how to get started with Vexpress >>> TC2 and Juno. >>> >>> I have access to the TC2 and Juno r2 platforms. >>> Please provide a rather detailed version of getting started guide to try >>> out perf with CoreSight and OpenCSD on either TC2 or Juno r2. >> >> Hello Yan Lin, >> >> You are correct, the HOWTO.md on github concentrates on CoreSight and >> doesn't address platform specifics - something like this would be out >> of scope. I'm not exactly sure of what you are looking for in a >> "getting started guide"... Both Juno and TC2 are well supported >> upstream and can be booted with a mainline kernel. The choice of >> bootloader and user space are entirely up to users and don't affect >> the CoreSight suite nor its integration with the perf subsystem. >> >> The fact that you have access to both platform leads me to believe you >> are part of a large organisation. As such there is definitely people >> around you with experience on how to set-up the platforms. >> >> I can try to answer specific questions if you have any. >> >> Thanks, >> Mathieu >> >>> >>> Thanx. >>> >>> Regards, >>> Yan Lin Aung >>> >> >> > >

7 years, 8 months

Re: Trace issue on Linux-4.9-rc1

by Mathieu Poirier

On 19 December 2016 at 07:45, Yehuda Yitschak <yehuday(a)marvell.com> wrote: > Hi Mathieu > > > > After some more debug I was able to resolve the trace issue I had on > Linux-4.9-rc1 > > If you remember I only got trace for CPU2 out of 4 CPUs which was really > strange > > > > Turns out the issue comes from some quirk in our busses > > Our internal fabric is not able to write 64bit data to registers, only to > memory > > So the address comparators in the ETM got corrupted values and there wasn’t > any match on address for most CPUs. > > For some cryptic reason only CPU2 got somewhat reasonable comparator value > (still not the intended, but a working one) and so it could generate trace > > > > Now I am able to generate proper trace consistently. > Very good. > > > I was wondering how can I add latency or timing information to the trace > > I noticed the cs_etm event can accept an option of “cycacc” and “timestamp“ > > How can I view this information later ? > > Should I use perf script –f ? That information, when configured on the cmd line, will end up in the perf.data file. From there it will be decoded and rendered by the openCSD library. Mike, can you comment on the format of the information that will be found in the packet? Perhaps you have an example somewhere of traces generated by the "cycacc" and "timestamp" option? You will definitely need to create your own scripts as nothing we have done so far uses those configuration parameters. Thanks, Mathieu > > > > Thanks a lot > > > > ------------------- > > Yehuda Yitschak > > Marvell Semiconductor Ltd. > >

7 years, 8 months

[PATCH v3 0/3] arm64: dts: juno: CoreSight support updates

by Sudeep Holla

Hi Mike, I just did some refactoring to reduced thge churn and duplication. Can you check if this work for you ? I could not give it much testing. Regards, Sudeep --->8 Juno r1/r2 boards have different CoreSight infrastructure outside the CPU clusters. This patchset adds the additional coreSight components to separate .dtsi files to support these differences. v1->v2: - moved the addition of the STM component into a separate patch v2->v3: - moved the back the common coreSight components back into juno-base.dtsi Mike Leach (2): arm64: dts: juno: fix CoreSight support for Juno r1/r2 variants arm64: dts: juno: add missing CoreSight STM component Sudeep Holla (1): arm64: dts: juno: refactor CoreSight support on Juno r0 arch/arm64/boot/dts/arm/juno-base.dtsi | 31 ++++++--- arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi | 102 ++++++++++++++++++++++++++++++ arch/arm64/boot/dts/arm/juno-r1.dts | 13 ++++ arch/arm64/boot/dts/arm/juno-r2.dts | 13 ++++ arch/arm64/boot/dts/arm/juno.dts | 24 +++++++ 5 files changed, 175 insertions(+), 8 deletions(-) create mode 100644 arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi -- 2.7.4

7 years, 8 months

Re: [PATCH v4 4/4] arm64: dts: juno: add missing CoreSight STM component

by Suzuki K Poulose

On 17/01/17 12:15, Sudeep Holla wrote: > From: Mike Leach <mike.leach(a)linaro.org> > > This patch adds the missing CoreSight STM component definition to the > device tree of all the juno variants(r0,r1,r2) > > STM component is connected to different funnels depending on Juno > platform variant. > > Reviewed-and-Tested-by: Mathieu Poirier <mathieu.poirier(a)linaro.org> > Signed-off-by: Mike Leach <mike.leach(a)linaro.org> > [sudeep.holla(a)arm.com: minor changelog update and reorganising the STM > node back into juno-base.dtsi to avoid duplication] > Signed-off-by: Sudeep Holla <sudeep.holla(a)arm.com> > --- > arch/arm64/boot/dts/arm/juno-base.dtsi | 15 +++++++++++++++ > arch/arm64/boot/dts/arm/juno-r1.dts | 4 ++++ > arch/arm64/boot/dts/arm/juno-r2.dts | 4 ++++ > arch/arm64/boot/dts/arm/juno.dts | 16 ++++++++++++++++ > 4 files changed, 39 insertions(+) > > diff --git a/arch/arm64/boot/dts/arm/juno-base.dtsi b/arch/arm64/boot/dts/arm/juno-base.dtsi > index faedf357db3b..58c1773c3aa4 100644 > --- a/arch/arm64/boot/dts/arm/juno-base.dtsi > +++ b/arch/arm64/boot/dts/arm/juno-base.dtsi > @@ -185,6 +185,21 @@ > }; > }; > > + stm@20100000 { > + compatible = "arm,coresight-stm", "arm,primecell"; > + reg = <0 0x20100000 0 0x1000>, > + <0 0x28000000 0 0x180000>; The size of the stimulus base is 16MB (as per TRM), implies => 0x1000000. with that fixed : Reviewed-by: Suzuki K Poulose <suzuki.poulose(a)arm.com>

7 years, 8 months

Re: [PATCH v4 3/4] arm64: dts: juno: add CoreSight support for Juno r1/r2 variants

by Suzuki K Poulose

On 17/01/17 12:15, Sudeep Holla wrote: > From: Mike Leach <mike.leach(a)linaro.org> > > The CoreSight support added for Juno is valid for only Juno r0. > The Juno r1 and r2 variants have additional components and alternative > connection routes between trace source and sinks. > > This patch builds on top of the existing r0 support and extends it to > Juno r1/r2 variants. > > Reviewed-by: Mathieu Poirier <mathieu.poirier(a)linaro.org> > Signed-off-by: Mike Leach <mike.leach(a)linaro.org> > [sudeep.holla(a)arm.com: minor changelog update and major reorganisation of > the common coresight components back into juno-base.dtsi to avoid > duplication, also renamed funnel node names] > Signed-off-by: Sudeep Holla <sudeep.holla(a)arm.com> > --- > arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi | 100 ++++++++++++++++++++++++++++++ > arch/arm64/boot/dts/arm/juno-r1.dts | 9 +++ > arch/arm64/boot/dts/arm/juno-r2.dts | 9 +++ > 3 files changed, 118 insertions(+) > create mode 100644 arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi > > diff --git a/arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi b/arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi > new file mode 100644 > index 000000000000..563463ed28c7 > --- /dev/null > +++ b/arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi > @@ -0,0 +1,100 @@ > +/ { > + funnel@20130000 { /* cssys2 */ Typo, that should be csys1. Rest looks good to me. Reviewed-by: Suzuki K Poulose <suzuki.poulose(a)arm.com>

7 years, 8 months

[PATCH] makefile: Support to cross compile for arm/arm64

by Chunyan Zhang

In order to support cross compile the OpenCSD for arm/arm64, this patch added two environment variables, 'CROSS_COMPILE' and 'ARCH' which can be set by users before compiling the code. Like documented in Kernel Makefile, CROSS_COMPILE specifies the prefix used for all executables used during compilation. CROSS_COMPILE can be set on the command line, as is ARCH. For example, if you want to build the libraryies for Aarch64, you can set "ARCH=arm64", the the compiled libs will be located at lib/linux-arm64/<rel\dbg>.` Signed-off-by: Chunyan Zhang <zhang.chunyan(a)linaro.org> --- decoder/build/linux/makefile | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/decoder/build/linux/makefile b/decoder/build/linux/makefile index 3b6a623..dc1f32b 100644 --- a/decoder/build/linux/makefile +++ b/decoder/build/linux/makefile @@ -47,7 +47,11 @@ export LIB_CAPI_NAME # determine base architecture, heavily borrowed from the Linux kernel v4.4's # tools/perf/config/Makefile.arch +# For example, to compile for arm64 on a X86 PC, you can issue the command: +# "export ARCH=arm64" +ifndef ARCH ARCH := $(shell uname -m 2>/dev/null || echo not) +endif # source root directories export OCSD_LIB_ROOT=$(OCSD_ROOT)/lib @@ -58,10 +62,10 @@ export OCSD_SOURCE=$(OCSD_ROOT)/source export OCSD_TESTS=$(OCSD_ROOT)/tests # tools -export MASTER_CC=gcc -export MASTER_CPP=g++ -export MASTER_LINKER=g++ -export MASTER_LIB=ar +export MASTER_CC=$(CROSS_COMPILE)gcc +export MASTER_CPP=$(CROSS_COMPILE)g++ +export MASTER_LINKER=$(CROSS_COMPILE)g++ +export MASTER_LIB=$(CROSS_COMPILE)ar # compile flags MASTER_CC_FLAGS := -c -Wall -DLINUX @@ -87,6 +91,10 @@ ifeq ($(ARCH),x86) else ifeq ($(ARCH),x86_64) MFLAG:="-m64" BIT_VARIANT=64 +else ifeq ($(ARCH),arm) + BIT_VARIANT=-arm +else ifeq ($(ARCH),arm64) + BIT_VARIANT=-arm64 endif MASTER_CC_FLAGS += $(MFLAG) -- 2.7.4

7 years, 9 months

[PATCH v2 0/2] arm64: dts: juno: Updates for juno r1/r2 boards

by Mike Leach

Juno r1/r2 boards have different CoreSight infrastructure outside the clusters. This patchset moves the none cluster CoreSight to separate .dtsi files to allow for these differences. v2 moves the Addition of the STM component into a separate patch. Mike Leach (2): arm64: dts: juno: Fix CoreSight support for Juno r1/r2 variants arm64: dts: juno: Adds missing CoreSight STM component. arch/arm64/boot/dts/arm/juno-base.dtsi | 135 --------------- arch/arm64/boot/dts/arm/juno-cs-r0.dtsi | 166 +++++++++++++++++++ arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi | 266 ++++++++++++++++++++++++++++++ arch/arm64/boot/dts/arm/juno-r1.dts | 1 + arch/arm64/boot/dts/arm/juno-r2.dts | 1 + arch/arm64/boot/dts/arm/juno.dts | 1 + 6 files changed, 435 insertions(+), 135 deletions(-) create mode 100644 arch/arm64/boot/dts/arm/juno-cs-r0.dtsi create mode 100644 arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi -- 2.7.4

7 years, 9 months

[PATCH] arm64: dts: juno: Fix CoreSight support for Juno r1/r2 variants

by Mike Leach

The CoreSight support added for Juno is valid for only Juno r0. The Juno r1 and r2 variants have additional components and alternative connection routes between trace source and sinks. The CoreSight infrastructure external to the Cortex-Axx clusters, has been split into separate .dtsi include files for r0 and r1/r2 to correctly represent these variations. Adds missing DT entry for the CoreSight STM component in the infrastructure .dtsi files. Signed-off-by: Mike Leach <mike.leach(a)linaro.org> --- arch/arm64/boot/dts/arm/juno-base.dtsi | 135 --------------- arch/arm64/boot/dts/arm/juno-cs-r0.dtsi | 166 +++++++++++++++++++ arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi | 266 ++++++++++++++++++++++++++++++ arch/arm64/boot/dts/arm/juno-r1.dts | 1 + arch/arm64/boot/dts/arm/juno-r2.dts | 1 + arch/arm64/boot/dts/arm/juno.dts | 1 + 6 files changed, 435 insertions(+), 135 deletions(-) create mode 100644 arch/arm64/boot/dts/arm/juno-cs-r0.dtsi create mode 100644 arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi diff --git a/arch/arm64/boot/dts/arm/juno-base.dtsi b/arch/arm64/boot/dts/arm/juno-base.dtsi index 7d83224..7c89000 100644 --- a/arch/arm64/boot/dts/arm/juno-base.dtsi +++ b/arch/arm64/boot/dts/arm/juno-base.dtsi @@ -83,104 +83,6 @@ * The actual size is just 4K though 64K is reserved. Access to the * unmapped reserved region results in a DECERR response. */ - etf@20010000 { - compatible = "arm,coresight-tmc", "arm,primecell"; - reg = <0 0x20010000 0 0x1000>; - - clocks = <&soc_smc50mhz>; - clock-names = "apb_pclk"; - power-domains = <&scpi_devpd 0>; - ports { - #address-cells = <1>; - #size-cells = <0>; - - /* input port */ - port@0 { - reg = <0>; - etf_in_port: endpoint { - slave-mode; - remote-endpoint = <&main_funnel_out_port>; - }; - }; - - /* output port */ - port@1 { - reg = <0>; - etf_out_port: endpoint { - remote-endpoint = <&replicator_in_port0>; - }; - }; - }; - }; - - tpiu@20030000 { - compatible = "arm,coresight-tpiu", "arm,primecell"; - reg = <0 0x20030000 0 0x1000>; - - clocks = <&soc_smc50mhz>; - clock-names = "apb_pclk"; - power-domains = <&scpi_devpd 0>; - port { - tpiu_in_port: endpoint { - slave-mode; - remote-endpoint = <&replicator_out_port0>; - }; - }; - }; - - main-funnel@20040000 { - compatible = "arm,coresight-funnel", "arm,primecell"; - reg = <0 0x20040000 0 0x1000>; - - clocks = <&soc_smc50mhz>; - clock-names = "apb_pclk"; - power-domains = <&scpi_devpd 0>; - ports { - #address-cells = <1>; - #size-cells = <0>; - - port@0 { - reg = <0>; - main_funnel_out_port: endpoint { - remote-endpoint = <&etf_in_port>; - }; - }; - - port@1 { - reg = <0>; - main_funnel_in_port0: endpoint { - slave-mode; - remote-endpoint = <&cluster0_funnel_out_port>; - }; - }; - - port@2 { - reg = <1>; - main_funnel_in_port1: endpoint { - slave-mode; - remote-endpoint = <&cluster1_funnel_out_port>; - }; - }; - - }; - }; - - etr@20070000 { - compatible = "arm,coresight-tmc", "arm,primecell"; - reg = <0 0x20070000 0 0x1000>; - iommus = <&smmu_etr 0>; - - clocks = <&soc_smc50mhz>; - clock-names = "apb_pclk"; - power-domains = <&scpi_devpd 0>; - port { - etr_in_port: endpoint { - slave-mode; - remote-endpoint = <&replicator_out_port1>; - }; - }; - }; - etm0: etm@22040000 { compatible = "arm,coresight-etm4x", "arm,primecell"; reg = <0 0x22040000 0 0x1000>; @@ -351,43 +253,6 @@ }; }; - coresight-replicator { - /* - * Non-configurable replicators don't show up on the - * AMBA bus. As such no need to add "arm,primecell". - */ - compatible = "arm,coresight-replicator"; - - ports { - #address-cells = <1>; - #size-cells = <0>; - - /* replicator output ports */ - port@0 { - reg = <0>; - replicator_out_port0: endpoint { - remote-endpoint = <&tpiu_in_port>; - }; - }; - - port@1 { - reg = <1>; - replicator_out_port1: endpoint { - remote-endpoint = <&etr_in_port>; - }; - }; - - /* replicator input port */ - port@2 { - reg = <0>; - replicator_in_port0: endpoint { - slave-mode; - remote-endpoint = <&etf_out_port>; - }; - }; - }; - }; - sram: sram@2e000000 { compatible = "arm,juno-sram-ns", "mmio-sram"; reg = <0x0 0x2e000000 0x0 0x8000>; diff --git a/arch/arm64/boot/dts/arm/juno-cs-r0.dtsi b/arch/arm64/boot/dts/arm/juno-cs-r0.dtsi new file mode 100644 index 0000000..4e01b0e --- /dev/null +++ b/arch/arm64/boot/dts/arm/juno-cs-r0.dtsi @@ -0,0 +1,166 @@ + /* + * Juno trace infrastructure. + * Trace links and sinks and interconnections + * from clusters. + * Connections for Juno r0. + */ + etf@20010000 { + compatible = "arm,coresight-tmc", "arm,primecell"; + reg = <0 0x20010000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* input port */ + port@0 { + reg = <0>; + etf_in_port: endpoint { + slave-mode; + remote-endpoint = <&main_funnel_out_port>; + }; + }; + + /* output port */ + port@1 { + reg = <0>; + etf_out_port: endpoint { + remote-endpoint = <&replicator_in_port0>; + }; + }; + }; + }; + + tpiu@20030000 { + compatible = "arm,coresight-tpiu", "arm,primecell"; + reg = <0 0x20030000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + port { + tpiu_in_port: endpoint { + slave-mode; + remote-endpoint = <&replicator_out_port0>; + }; + }; + }; + + main-funnel@20040000 { + compatible = "arm,coresight-funnel", "arm,primecell"; + reg = <0 0x20040000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* output port */ + port@0 { + reg = <0>; + main_funnel_out_port: endpoint { + remote-endpoint = <&etf_in_port>; + }; + }; + + /* input ports */ + port@1 { + reg = <0>; + main_funnel_in_port0: endpoint { + slave-mode; + remote-endpoint = <&cluster0_funnel_out_port>; + }; + }; + + port@2 { + reg = <1>; + main_funnel_in_port1: endpoint { + slave-mode; + remote-endpoint = <&cluster1_funnel_out_port>; + }; + }; + + port@3 { + reg = <2>; + main_funnel_in_port2: endpoint { + slave-mode; + remote-endpoint = <&stm_out_port>; + }; + }; + + + }; + }; + + etr@20070000 { + compatible = "arm,coresight-tmc", "arm,primecell"; + reg = <0 0x20070000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + port { + etr_in_port: endpoint { + slave-mode; + remote-endpoint = <&replicator_out_port1>; + }; + }; + }; + + coresight-replicator { + /* + * Non-configurable replicators don't show up on the + * AMBA bus. As such no need to add "arm,primecell". + */ + compatible = "arm,coresight-replicator"; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* replicator output ports */ + port@0 { + reg = <0>; + replicator_out_port0: endpoint { + remote-endpoint = <&tpiu_in_port>; + }; + }; + + port@1 { + reg = <1>; + replicator_out_port1: endpoint { + remote-endpoint = <&etr_in_port>; + }; + }; + + /* replicator input port */ + port@2 { + reg = <0>; + replicator_in_port0: endpoint { + slave-mode; + remote-endpoint = <&etf_out_port>; + }; + }; + }; + }; + + stm@20100000 { + compatible = "arm,coresight-stm", "arm,primecell"; + reg = <0 0x20100000 0 0x1000>, + <0 0x28000000 0 0x180000>; + reg-names = "stm-base", "stm-stimulus-base"; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + port { + stm_out_port: endpoint { + remote-endpoint = <&main_funnel_in_port2>; + }; + }; + }; diff --git a/arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi b/arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi new file mode 100644 index 0000000..6fe8b62 --- /dev/null +++ b/arch/arm64/boot/dts/arm/juno-cs-r1r2.dtsi @@ -0,0 +1,266 @@ + /* + * Juno trace infrastructure. + * Trace links and sinks and interconnections + * from clusters. + * Connections for Juno r1 and r2. + */ + etf0@20010000 { + compatible = "arm,coresight-tmc", "arm,primecell"; + reg = <0 0x20010000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* input port */ + port@0 { + reg = <0>; + etf0_in_port: endpoint { + slave-mode; + remote-endpoint = <&main_funnel_out_port>; + }; + }; + + /* output port */ + port@1 { + reg = <0>; + etf0_out_port: endpoint { + remote-endpoint = <&csys2_funnel_in_port0>; + }; + }; + }; + }; + + etf1@20140000 { + compatible = "arm,coresight-tmc", "arm,primecell"; + reg = <0 0x20140000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* input port */ + port@0 { + reg = <0>; + etf1_in_port: endpoint { + slave-mode; + remote-endpoint = + <&csys1_funnel_out_port>; + }; + }; + + /* output port */ + port@1 { + reg = <0>; + etf1_out_port: endpoint { + remote-endpoint = + <&csys2_funnel_in_port1>; + }; + }; + }; + }; + + csys1_funnel@20130000 { + compatible = "arm,coresight-funnel", "arm,primecell"; + reg = <0 0x20130000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* input port */ + port@0 { + reg = <0>; + csys1_funnel_out_port: endpoint { + remote-endpoint = + <&etf1_in_port>; + }; + }; + + /* output port */ + port@1 { + reg = <0>; + csys1_funnel_in_port0: endpoint { + slave-mode; + remote-endpoint = + <&stm_out_port>; + }; + }; + + }; + }; + + csys2_funnel@20150000 { + compatible = "arm,coresight-funnel", "arm,primecell"; + reg = <0 0x20150000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* output port */ + port@0 { + reg = <0>; + csys2_funnel_out_port: endpoint { + remote-endpoint = + <&replicator_in_port0>; + }; + }; + + /* input ports */ + port@1 { + reg = <0>; + csys2_funnel_in_port0: endpoint { + slave-mode; + remote-endpoint = <&etf0_out_port>; + }; + }; + + port@2 { + reg = <1>; + csys2_funnel_in_port1: endpoint { + slave-mode; + remote-endpoint = <&etf1_out_port>; + }; + }; + + }; + }; + + tpiu@20030000 { + compatible = "arm,coresight-tpiu", "arm,primecell"; + reg = <0 0x20030000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + port { + tpiu_in_port: endpoint { + slave-mode; + remote-endpoint = <&replicator_out_port0>; + }; + }; + }; + + /* + * This is labelled cssys0 funnel in the Juno r1/r2 TRM + * Retain the name from r0 to maintain compatibility with common + * juno-base.dtsi + */ + main-funnel@20040000 { + compatible = "arm,coresight-funnel", "arm,primecell"; + reg = <0 0x20040000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* output port */ + port@0 { + reg = <0>; + main_funnel_out_port: endpoint { + remote-endpoint = <&etf0_in_port>; + }; + }; + + /* input ports */ + port@1 { + reg = <0>; + main_funnel_in_port0: endpoint { + slave-mode; + remote-endpoint = <&cluster0_funnel_out_port>; + }; + }; + + port@2 { + reg = <1>; + main_funnel_in_port1: endpoint { + slave-mode; + remote-endpoint = <&cluster1_funnel_out_port>; + }; + }; + }; + }; + + etr@20070000 { + compatible = "arm,coresight-tmc", "arm,primecell"; + reg = <0 0x20070000 0 0x1000>; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + port { + etr_in_port: endpoint { + slave-mode; + remote-endpoint = <&replicator_out_port1>; + }; + }; + }; + + coresight-replicator { + /* + * Non-configurable replicators don't show up on the + * AMBA bus. As such no need to add "arm,primecell". + */ + compatible = "arm,coresight-replicator"; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + /* replicator output ports */ + port@0 { + reg = <0>; + replicator_out_port0: endpoint { + remote-endpoint = <&tpiu_in_port>; + }; + }; + + port@1 { + reg = <1>; + replicator_out_port1: endpoint { + remote-endpoint = <&etr_in_port>; + }; + }; + + /* replicator input port */ + port@2 { + reg = <0>; + replicator_in_port0: endpoint { + slave-mode; + remote-endpoint = <&csys2_funnel_out_port>; + }; + }; + }; + }; + + stm@20100000 { + compatible = "arm,coresight-stm", "arm,primecell"; + reg = <0 0x20100000 0 0x1000>, + <0 0x28000000 0 0x180000>; + reg-names = "stm-base", "stm-stimulus-base"; + + clocks = <&soc_smc50mhz>; + clock-names = "apb_pclk"; + power-domains = <&scpi_devpd 0>; + port { + stm_out_port: endpoint { + remote-endpoint = <&csys1_funnel_in_port0>; + }; + }; + }; diff --git a/arch/arm64/boot/dts/arm/juno-r1.dts b/arch/arm64/boot/dts/arm/juno-r1.dts index eec37fe..8813395 100644 --- a/arch/arm64/boot/dts/arm/juno-r1.dts +++ b/arch/arm64/boot/dts/arm/juno-r1.dts @@ -178,6 +178,7 @@ }; #include "juno-base.dtsi" + #include "juno-cs-r1r2.dtsi" }; &memtimer { diff --git a/arch/arm64/boot/dts/arm/juno-r2.dts b/arch/arm64/boot/dts/arm/juno-r2.dts index 28f40ec..fca3a17 100644 --- a/arch/arm64/boot/dts/arm/juno-r2.dts +++ b/arch/arm64/boot/dts/arm/juno-r2.dts @@ -178,6 +178,7 @@ }; #include "juno-base.dtsi" + #include "juno-cs-r1r2.dtsi" }; &memtimer { diff --git a/arch/arm64/boot/dts/arm/juno.dts b/arch/arm64/boot/dts/arm/juno.dts index ac5ceb7..c90c37b 100644 --- a/arch/arm64/boot/dts/arm/juno.dts +++ b/arch/arm64/boot/dts/arm/juno.dts @@ -178,6 +178,7 @@ }; #include "juno-base.dtsi" + #include "juno-cs-r0.dtsi" }; &etm0 { -- 2.7.4

7 years, 9 months

[PATCH] Add documentation on AutoFDO

by Sebastian Pop

The patch adds documentation to HOWTO.md on how to use CoreSight ETM to perform Feedback Directed Optimization. Sebastian Pop (1): HOWTO: add example of how to extract coverage files for autoFDO HOWTO.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) -- 2.6.3

7 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CoreSight January 2017