| Age | Commit message (Collapse) | Author |
|---|
|
The default build directory needed manual adjustment when the
driver was to be built. Change it to use the Debian build path
so this driver can be built immediately for the native Debian
system without any changes.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
The leds application runs on the host and is used to simulate
PCI hardware with 3 LEDs. See the README for information about
how to build and use it.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
The amount of instructions should be the same regardless what
method you use (1 or 2) but the cache misses will be very
different. Looking at these statistics side by side clearly
illustrate the problem.
Update the README to also include the instruction count.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
This demo should (hopefully serve) as a basis for overlaying pcap
and ftrace data within trace compass.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
they should be converted to a 'Kernel API' slideset.
Signed-off-by: Manuel Traut <manut@linutronix.de>
|
|
this module can be used to show the usage of klist
Signed-off-by: Manuel Traut <manut@linutronix.de>
|
|
To show that processes become zombies if you don't wait.
Also show that init becomes the father of your zombies if the original father
dies.
Signed-off-by: Manuel Traut <manut@linutronix.de>
|
|
it demonstrates that memory is only allocated if used.
Signed-off-by: Manuel Traut <manut@linutronix.de>
|
|
The text docs are general references showing how to build, link,
and verify dynamic libraries and executables. They are not specific
to any build system.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
It is good to have Makefile and autotool versions for compare. But
the Makefiles should not be intentially horrible. Clean them up to
the level that we teach in the training.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
one example by doing it manually with an ugly Makefile,
another one by using autotools.
Signed-off-by: Manuel Traut <manut@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
mention some other usage of perf to track done the problem
[Reformatted by jogness]
Signed-off-by: Manuel Traut <manut@linutronix.de>
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
I include this start script in /home/prebuilt so that schulung
participants can easily start the vexpress board.
NOTE: It expects to be run from the build directory, typically
/home/devel/yocto/build/vexpress
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
The meta-schulung.bundle now includes separate branches depending
on the poky release. This was necessary because thud introduced
a new busybox dependency (virtual/crypt).
One nice feature of this splitting is that it is very easy to
see how the layer changes over poky versions by diffing the
branches.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
The yocto training requires a lot of data to be
prebuilt/downloaded (about 15GB). These scripts can be used
to automatically download/prebuild all that data and create
the various layer tarballs.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Supporting x86 allows us to quickly show the hello driver in
action directly from the x86 trainer image. It also shows how
platform devices can be added on architectures that do not
support device trees.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
In the comments, the bitbake commands for menuconfig and diffconfig
were incorrect.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
It is nice to have a finished layer for trainers to use as a
reference when helping participants to create their own layer.
However, there are files that are modified multiple times during
the creation process.
For this reason a git bundle is added so that trainers have a
step-by-step procedure for guiding participants during layer
creation. Each commit is a step, documented for the trainer.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Describes the main targets, files, and procedure dealing with building
kernels.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
It's much simpler to have syscall names instead of numbers in traces.
Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
|
|
The "ln" tool is needed for the basic schulung. Add it to the
command reference handout.
Since adding something to the left column creates empty space in
the right column, use that to add a reference to ctrl+r (searching
the shell history). This is a feature that is always asked about
during the schulung.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
An older version of this file was in the devel/jogness branch. We
do not want trainers digging around in the devel/jogness branch.
And since this file is still considered useful, put the latest
version in the master branch.
NOTE: This needs to be converted to LaTeX at some point!
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
It is much easier to use tcf-agent with eclipse and cross-remote
debugging. Since local plugin-mirrors and yocto instructions are
now available, update the documents to reflect this.
Using the old method (with ssh) probably still works, but is
definitely more work to get setup on the target.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Rather than manually determining and setting the uprobes, use perf
to do it. This allows for the README to become a generic script
that can run out-of-the-box to create the trace.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
These scripts are provided to participants after the training to
allow them to quickly/easily reproduce the many steps of creating
a simple root filesystem from scratch.
These scripts also serve as an excellent reference for trainers
to follow during the live excercises.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
These are notes that may be helpful for trainers when preparing
for a schulung.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
In case it is run on a system where PIE is not the default,
explicitly set for the binary to be built as PIE.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
|
|
The rtex tool only demonstrates prefaultingn to avoid runtime
page faults. It makes more sense to call it pgflt.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Different tools have been used by various trainers as demos. Put
all these into master so they are available to all trainers.
ipc_pipe: ipc demo using pipes
ipc_shm: ipc demo using shared memory
libduma: source and instructions for compiling libduma
matrix: demo of good and bad cache access
mtrace: patch and infos for using mtrace with ASLR
rtex: demo of handling page faults
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
Simple drivers for use in the Linux Advanced schulung were only
available in the devel/jogness branch. Push them to master so
they are easily accessible to any trainer.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
|
|
|
