manut/vorlesung/schulung_tools, branch schulungUnnamed repository; edit this file 'description' to name the repository.
https://git.mecka.net/manut/vorlesung/atom?h=schulung2019-04-26T08:54:00Zlayer-building/yocto: update scripts for 2.6.12019-04-26T08:54:00ZJohn Ognessjohn.ogness@linutronix.de2019-04-26T08:54:00Zurn:sha1:762fab1d5f677ef42a4467e492a724540483eb7b
Use the latest thud stable and also cleanup the scripts a bit so
that it is easier to update the version in the future.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
schulung_tools/yocto-own-layer: add u-boot howto2019-04-25T08:22:55ZJohn Ognessjohn.ogness@linutronix.de2019-04-25T08:20:03Zurn:sha1:602c17ae7dc2d3af68c0105fbc61873181906553
meta-schulung does not include building u-boot. However, building/running
u-boot with qemu is quite easy. Add a mini howto with the steps to help
the trainer quickly demonstrate u-boot.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
meta-schulung: add app much sooner2019-04-18T08:02:14ZJohn Ognessjohn.ogness@linutronix.de2019-04-18T08:02:14Zurn:sha1:2e0994908c82cdce757a56a35adc34b75fc64c7a
Add the application after creating the layer. This allows the
participants to see the minimal efforts needed to create their
own applications. The layer can be used with any machine (for
example, the qemux86 machine that the participants had already
been working with).
Signed-off-by: John Ogness <john.ogness@linutronix.de>
sleep_wake: update with more details, new events2019-04-03T11:25:00ZJohn Ognessjohn.ogness@linutronix.de2019-04-03T11:25:00Zurn:sha1:d86b8ab490be3d252b2960e77157c89f502fa4fe
There were an unnecessary number of events that were captured.
Only capture the ones that are truly interesting. And add the
irq vector.
Also, add some description to the significance of the events.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
schulung_tools: scheduling_tests: disable rt throttling2019-03-28T14:23:25ZJohn Ognessjohn.ogness@linutronix.de2019-03-28T14:23:25Zurn:sha1:b8f92e275f24599253d4a66c3d3d2ebd70c1eb93
On a machine with few CPUs, these tests could trigger RT
throttling.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
schulung_tools: add sleep_wake demo2019-03-28T14:15:48ZJohn Ognessjohn.ogness@linutronix.de2019-03-28T14:15:48Zurn:sha1:115114f896fbb1a89467ea07476d2b6d1b18f1b8
A very simple demo that shows the full chain of events from
sys_nanosleep_enter to sys_nanosleep_exit. (For the IRQ
calculations use expires= and now= from the hrtimer events.)
Signed-off-by: John Ogness <john.ogness@linutronix.de>
schulung_tools: rename/modify malloc to avoid system()2019-03-28T14:11:34ZJohn Ognessjohn.ogness@linutronix.de2019-03-28T14:11:34Zurn:sha1:e1e6511cd68b646234dcc8f5f86b25b7ea48a720
A more complex but cleaner implementation of retrieving/printing
the stats has been implemented. The implementation is put into
a separate stats.c file so that the main program (malloc.) can
be easily reviewed to see what the program is doing.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
schulung_tools: add scheduling tests2019-03-28T13:08:28ZJohn Ognessjohn.ogness@linutronix.de2019-03-28T13:07:10Zurn:sha1:a39de4609225129c19df931d556b1d032d806403
This is a set of tests to compare the scheduling using various
policies and priorities.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
notes: initrd: use a better name for the cpio file2019-03-04T14:04:39ZJohn Ognessjohn.ogness@linutronix.de2019-03-04T14:04:39Zurn:sha1:1c18bd7b0c9d56d6bf6a60418fb62fd3e0cb3699
It is an initramfs, not an initrd. So name it so.
Signed-off-by: John Ogness <john.ogness@linutronix.de>
notes: initrd: add information about /init and /dev/console2019-02-28T16:23:57ZJohn Ognessjohn.ogness@linutronix.de2019-02-28T16:23:57Zurn:sha1:374f8fb4d4f767d655b253045d8978a5858d6cf9
Signed-off-by: John Ogness <john.ogness@linutronix.de>