From: Mathieu Acher <mathieu.acher@irisa.fr>
To: info@kernelci.org
Subject: TUXML, Kernel CI, and OSS 2019
Date: Sun, 27 Oct 2019 17:45:48 +0100 [thread overview]
Message-ID: <45f883ef-6ff2-46cd-b14d-cc42a451014c@Spark> (raw)
In-Reply-To: 32627a96-3d76-4436-8529-f48425caf1ab@Spark
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Dear colleagues,
We are researchers at Inria (France) working on software configurable systems in general.
Recently we have made lots of effort with Linux: we have basically build 95K+ configurations using ranconfig.
Our attempt is quite similar to KernelCI, the platform you’ve developed.
We have developed some techniques to identify what (combinations of) options lead to a failure (a non-trivial problem!), with two main applications in mind: (1) configuration bug location/understanding (2) preventing configurations’ build that will anyway lead to a failure. We mainly use randconfig.
More details can be found here:
https://hal.inria.fr/hal-02147012
We have also made some efforts about predicting kernel sizes:
https://hal.inria.fr/hal-02314830
It would be very nice to know more about your infrastructure, your strategy for sampling configurations, and basically your insights. We can also chat a bit about our approach and potential complementarity.
Would you be available for discussing?
I guess some of you will be at OSS in Lyon.
I’m giving a talk on Wednesday
https://sched.co/TLKI and I’m here until Thursday (included)
Best regards,
Dr. Mathieu ACHER, Associate Professor
Univ Rennes, Inria, CNRS, IRISA, France (DiverSE team)
http://www.mathieuacher.com/
[-- Attachment #2: Type: text/html, Size: 2754 bytes --]
parent reply other threads:[~2019-10-27 16:45 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <32627a96-3d76-4436-8529-f48425caf1ab@Spark>]
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=45f883ef-6ff2-46cd-b14d-cc42a451014c@Spark \
--to=mathieu.acher@irisa.fr \
--cc=info@kernelci.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