13–15 Nov 2023
America/New_York timezone

Session

Kernel Testing & Dependability MC

13 Nov 2023, 09:30

Presentation materials

  1. Sasha Levin, Shuah Khan
    13/11/2023, 09:30
  2. philip li
    13/11/2023, 09:40

    There're a lot of focused testing effort across Linux kernel community to guarantee the quality of kernel from build to runtime. Nowadays, not only the test process has moved towards formalization but also the test coverage has been increased to discover more issues in an earlier time. On the other side, some issues are still escaped to mainline.

    In this talk, we will dive into the build...

    Go to contribution page
  3. Rae Moar
    13/11/2023, 10:05

    Current kernel testing frameworks save basic test information including test names, results, and even some diagnostic data. But to what extent should frameworks store supplemental test information? This could include test speed, module name, file path, and even parameters for parameterized tests.

    Storing this information could greatly improve the kernel developer experience by allowing test...

    Go to contribution page
  4. David Gow (Google)
    13/11/2023, 10:30

    Unit testing common library code is (relatively) easy, but drivers often deal with a lot of global state, both in code and in hardware. New features like static stubbing go some way towards making this easier, but a lot of work still goes into making "fake devices".

    There are still many open questions, however:
    - Are the existing tools helping? Is there something obviously missing?
    - Are...

    Go to contribution page
  5. Sasha Levin
    13/11/2023, 11:30

    The bar on the quality of code that fixes embargoed issues is pretty low: usually the case is that the code is only tested by the author, and possibly a handful of other folks who are part of working on the fix.

    This session is a discussion to help draft a proposal for a testing story that could be presented to HW vendors that with to publish embargoed code without going through the...

    Go to contribution page
  6. Laura Nao, Nicolas Prado (Collabora)
    13/11/2023, 12:00

    Regressions that cause a device to no longer be probed by a driver can have a
    big impact on the platform's functionality, and despite being relatively common
    there isn't currently any generic way to detect them.

    By enabling the community to catch device probe regressions in a way that
    doesn't require additional work for every new platform, and that can catch
    issues from config changes...

    Go to contribution page
  7. Gustavo Padovan (Collabora), Ricardo Cañuelo
    13/11/2023, 12:25

    The current CI systems for the kernel offer basic and low-level
    regression detection and handling capabilities based on test results, but they do that in their own specific way. We wonder if we can find more common ways of tackling the problem through post-processing the data provided by the different CI systems. We could then extract additional "hidden" information, look at failure trends,...

    Go to contribution page
Building timetable...