From: Andreas Ruprecht <rupran@einserver.de>
To: josh@joshtriplett.org
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Linux Kernel Tinification - Research project and Tools
Date: Tue, 9 Sep 2014 21:02:45 +0200 [thread overview]
Message-ID: <CA+B2V-K_B0n9ZK_3CirdtU=v_z68KZAyYjp=mRLrPzjCF4nk3Q@mail.gmail.com> (raw)
Hi guys,
I just discovered the thread (reaching back to May) on the
ksummit-discuss mailing list and your (Josh's) talk topic at LinuxCon
Europe on Linux Kernel Tinification, and might have something
interesting to share.
I'm a member of the VAMOS/CADOS[0] project at the University of
Erlangen-Nürnberg, where we're working on different topics concerning
the analysis of Linux, particularily the kernel configuration system.
One of these projects is "Tailor"[1], where we developed a method of
generating an (almost) minimal kernel configuration, basically by
observing a "bigger" (might be distribution-provided) kernel and
solving a formula of feature constraints for a solution. Results for
this were published at various conferences (HotDep '12 [2], NDSS '13
[3]), and just next week, I will be at GPCE '14 in Vasteras, Sweden to
present our most recent work [4].
Probably the most important difference to note is that in earlier
versions, we used the ftrace function tracer to gain insights on the
control flow - so we did not need to patch the kernel -, whereas we
found that for embedded systems, we needed to patch tiny instructions
into conditional blocks to create usable results (ftrace was just too
much overhead).
Unfortunately, the code for patching the kernel has not yet been
integrated into our tool box, as the student developing it is just
about to finish his master's thesis, but if you are interested, we
could also make this available to you.
If you would like to try it out, please go ahead (instructions at
[1])! If there are problems, don't hesitate to contact me. I will also
be at Linux Plumbers Conference in Düsseldorf in October, if you'd
like to discuss this further in person.
Best regards,
Andreas Ruprecht
[0]: https://www4.cs.fau.de/Research/CADOS/
[1]: http://vamos.informatik.uni-erlangen.de/trac/undertaker/wiki/UndertakerTailor
[2]: https://www4.cs.fau.de/Publications/2012/tartler_12_hotdep.pdf
[3]: https://www4.cs.fau.de/Publications/2013/kurmus_13_ndss.pdf
[4]: https://www4.cs.fau.de/Publications/2014/ruprecht_14_gpce.pdf
reply other threads:[~2014-09-09 19:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+B2V-K_B0n9ZK_3CirdtU=v_z68KZAyYjp=mRLrPzjCF4nk3Q@mail.gmail.com' \
--to=rupran@einserver.de \
--cc=josh@joshtriplett.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox