<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>31691914 - kunit: Introduce autorun option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#31691914</link>
        <description>kunit: Introduce autorun optionThe new option controls tests run on boot or module load. With the newdebugfs &quot;run&quot; dentry allowing to run tests on demand, an ability to disableautomatic tests run becomes a useful option in case of intrusive tests.The option is set to true by default to preserve the existent behavior. Itcan be overridden by either the corresponding module option or by thecorresponding config build option.Link: https://lore.kernel.org/r/173015245931.4747.16419517391658830640.stgit@skinsburskii-cloud-desktop.internal.cloudapp.netSigned-off-by: Stanislav Kinsburskii &lt;skinsburskii@linux.microsoft.com&gt;Reviewed-by: Rae Moar &lt;rmoar@google.com&gt;Acked-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 28 Oct 2024 21:54:52 +0000</pubDate>
        <dc:creator>Stanislav Kinsburskii &lt;skinsburskii@linux.microsoft.com&gt;</dc:creator>
    </item>
<item>
        <title>4b513a02 - kunit: test: Move fault tests behind KUNIT_FAULT_TEST Kconfig option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#4b513a02</link>
        <description>kunit: test: Move fault tests behind KUNIT_FAULT_TEST Kconfig optionThe NULL dereference tests in kunit_fault deliberately trigger a kernelBUG(), and therefore print the associated stack trace, even when thetest passes. This is both annoying (as it bloats the test output), andcan confuse some test harnesses, which assume any BUG() is a failure.Allow these tests to be specifically disabled (without disabling allof KUnit&apos;s other tests), by placing them behind theCONFIG_KUNIT_FAULT_TEST Kconfig option. This is enabled by default, butcan be set to &apos;n&apos; to disable the test. An empty &apos;kunit_fault&apos; suite isleft behind, which will automatically be marked &apos;skipped&apos;.As the fault tests already were disabled under UML (as they weren&apos;tcompatible with its fault handling), we can simply adapt thoseconditions, and add a dependency on !UML for our new option.Suggested-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Link: https://lore.kernel.org/all/928249cc-e027-4f7f-b43f-502f99a1ea63@roeck-us.net/Fixes: 82b0beff3497 (&quot;kunit: Add tests for fault&quot;)Signed-off-by: David Gow &lt;davidgow@google.com&gt;Reviewed-by: Micka&#235;l Sala&#252;n &lt;mic@digikod.net&gt;Reviewed-by: Rae Moar &lt;rmoar@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Tue, 23 Apr 2024 09:08:06 +0000</pubDate>
        <dc:creator>David Gow &lt;davidgow@google.com&gt;</dc:creator>
    </item>
<item>
        <title>b67abaad - kunit: Allow kunit test modules to use test filtering</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#b67abaad</link>
        <description>kunit: Allow kunit test modules to use test filteringExternal tools, e.g., Intel GPU tools (IGT), support execution ofindividual selftests provided by kernel modules.  That could be alsoapplicable to kunit test modules if they provided test filtering.  Buttest filtering is now possible only when kunit code is built into thekernel.  Moreover, a filter can be specified only at boot time, thenreboot is required each time a different filter is needed.Build the test filtering code also when kunit is configured as a module,expose test filtering functions to other kunit source files, and use themin kunit module notifier callback functions.  Userspace can then reloadthe kunit module with a value of the filter_glob parameter tuned to aspecific kunit test module every time it wants to limit the scope of testsexecuted on that module load.  Make the kunit.filter* parameters visiblein sysfs for user convenience.v5: Refresh on tpp of attributes filtering fixv4: Refresh on top of newly applied attributes patches and changes    introdced by new versions of other patches submitted in series with    this one.v3: Fix CONFIG_GLOB, required by filtering functions, not selected when    building as a module (lkp@intel.com).v2: Fix new name of a structure moved to kunit namespace not updated    across all uses (lkp@intel.com).Signed-off-by: Janusz Krzysztofik &lt;janusz.krzysztofik@linux.intel.com&gt;Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 07 Aug 2023 10:23:56 +0000</pubDate>
        <dc:creator>Janusz Krzysztofik &lt;janusz.krzysztofik@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>d20a6ba5 - kunit: add kunit.enable to enable/disable KUnit test</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#d20a6ba5</link>
        <description>kunit: add kunit.enable to enable/disable KUnit testThis patch adds the kunit.enable module parameter that will need to beset to true in addition to KUNIT being enabled for KUnit tests to run.The default value is true giving backwards compatibility. However, forthe production+testing use case the new config optionKUNIT_DEFAULT_ENABLED can be set to N requiring the tester to opt-inby passing kunit.enable=1 to the kernel.Signed-off-by: Joe Fradley &lt;joefradley@google.com&gt;Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Tue, 23 Aug 2022 14:24:54 +0000</pubDate>
        <dc:creator>Joe Fradley &lt;joefradley@google.com&gt;</dc:creator>
    </item>
<item>
        <title>5d31f71e - kunit: add kunit.filter_glob cmdline option to filter suites</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#5d31f71e</link>
        <description>kunit: add kunit.filter_glob cmdline option to filter suitesE.g. specifying this would run suites with &quot;list&quot; in their name.  kunit.filter_glob=list*Note: the executor prints out a TAP header that includes the number ofsuites we intend to run.So unless we want to report empty results for filtered-out suites, weneed to do the filtering here in the executor.It&apos;s also probably better in the executor since we most likely don&apos;twant any filtering to apply to tests built as modules.This code does add a CONFIG_GLOB=y dependency for CONFIG_KUNIT=y.But the code seems light enough that it shouldn&apos;t be an issue.For now, we only filter on suite names so we don&apos;t have to create copiesof the suites themselves, just the array (of arrays) holding them.The name is rather generic since in the future, we could considerextending it to a syntax like:  kunit.filter_glob=&lt;suite_glob&gt;.&lt;test_glob&gt;E.g. to run all the del list tests  kunit.filter_glob=list-kunit-test.*del*But at the moment, it&apos;s far easier to manually comment out test cases intest files as opposed to messing with sets of Kconfig entries to selectspecific suites.So even just doing this makes using kunit far less annoying.Signed-off-by: Daniel Latypov &lt;dlatypov@google.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Sat, 06 Feb 2021 00:08:52 +0000</pubDate>
        <dc:creator>Daniel Latypov &lt;dlatypov@google.com&gt;</dc:creator>
    </item>
<item>
        <title>beaed42c - kunit: default KUNIT_* fragments to KUNIT_ALL_TESTS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#beaed42c</link>
        <description>kunit: default KUNIT_* fragments to KUNIT_ALL_TESTSThis makes it easier to enable all KUnit fragments.Adding &apos;if !KUNIT_ALL_TESTS&apos; so individual tests can not be turned off.Therefore if KUNIT_ALL_TESTS is enabled that will hide the prompt inmenuconfig.Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 11 May 2020 13:14:25 +0000</pubDate>
        <dc:creator>Anders Roxell &lt;anders.roxell@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>92238b31 - kunit: Kconfig: enable a KUNIT_ALL_TESTS fragment</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#92238b31</link>
        <description>kunit: Kconfig: enable a KUNIT_ALL_TESTS fragmentMake it easier to enable all KUnit fragments.  This is useful for kerneldevs or testers, so its easy to get all KUnit tests enabled and if newgets added they will be enabled as well.  Fragments that has to bebuiltin will be missed if CONFIG_KUNIT_ALL_TESTS is set as a module.Signed-off-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 11 May 2020 13:14:20 +0000</pubDate>
        <dc:creator>Anders Roxell &lt;anders.roxell@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>e2219db2 - kunit: add debugfs /sys/kernel/debug/kunit/&lt;suite&gt;/results display</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#e2219db2</link>
        <description>kunit: add debugfs /sys/kernel/debug/kunit/&lt;suite&gt;/results displayadd debugfs support for displaying kunit test suite results; this isespecially useful for module-loaded tests to allow disentangling oftest result display from other dmesg events.  debugfs support isprovided if CONFIG_KUNIT_DEBUGFS=y.As well as printk()ing messages, we append them to a per-test log.Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Frank Rowand &lt;frank.rowand@sony.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Thu, 26 Mar 2020 14:25:07 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>9fe124bf - kunit: allow kunit to be loaded as a module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#9fe124bf</link>
        <description>kunit: allow kunit to be loaded as a moduleMaking kunit itself buildable as a module allows for &quot;always-on&quot;kunit configuration; specifying CONFIG_KUNIT=m means the moduleis built but only used when loaded.  Kunit test modules will loadkunit.ko as an implicit dependency, so simply running&quot;modprobe my-kunit-tests&quot; will load the tests along with the kunitmodule and run them.Co-developed-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 06 Jan 2020 22:28:22 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>c475c77d - kunit: allow kunit tests to be loaded as a module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#c475c77d</link>
        <description>kunit: allow kunit tests to be loaded as a moduleAs tests are added to kunit, it will become less feasible to executeall built tests together.  By supporting modular tests we providea simple way to do selective execution on a running system; specifyingCONFIG_KUNIT=yCONFIG_KUNIT_EXAMPLE_TEST=m...means we can simply &quot;insmod example-test.ko&quot; to run the tests.To achieve this we need to do the following:o export the required symbols in kunito string-stream tests utilize non-exported symbols so for now we skip  building them when CONFIG_KUNIT_TEST=m.o drivers/base/power/qos-test.c contains a few unexported interface  references, namely freq_qos_read_value() and freq_constraints_init().  Both of these could be potentially defined as static inline functions  in include/linux/pm_qos.h, but for now we simply avoid supporting  module build for that test suite.o support a new way of declaring test suites.  Because a module cannot  do multiple late_initcall()s, we provide a kunit_test_suites() macro  to declare multiple suites within the same module at once.o some test module names would have been too general (&quot;test-test&quot;  and &quot;example-test&quot; for kunit tests, &quot;inode-test&quot; for ext4 tests);  rename these as appropriate (&quot;kunit-test&quot;, &quot;kunit-example-test&quot;  and &quot;ext4-inode-test&quot; respectively).Also define kunit_test_suite() via kunit_test_suites()as callers in other trees may need the old definition.Co-developed-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Knut Omang &lt;knut.omang@oracle.com&gt;Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Reviewed-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Acked-by: Theodore Ts&apos;o &lt;tytso@mit.edu&gt; # for ext4 bitsAcked-by: David Gow &lt;davidgow@google.com&gt; # For list-testReported-by: kbuild test robot &lt;lkp@intel.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 06 Jan 2020 22:28:20 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>d8e2a76b - kunit: test: add initial tests</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#d8e2a76b</link>
        <description>kunit: test: add initial testsAdd a test for string stream along with a simpler example.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Reviewed-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 23 Sep 2019 09:02:37 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
<item>
        <title>914cc63e - kunit: test: add KUnit test runner core</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/lib/kunit/Kconfig#914cc63e</link>
        <description>kunit: test: add KUnit test runner coreAdd core facilities for defining unit tests; this provides a common wayto define test cases, functions that execute code which is under testand determine whether the code under test behaves as expected; this alsoprovides a way to group together related test cases in test suites (herewe call them test_modules).Just define test cases and how to execute them for now; settingexpectations on code will be defined later.Signed-off-by: Brendan Higgins &lt;brendanhiggins@google.com&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Reviewed-by: Luis Chamberlain &lt;mcgrof@kernel.org&gt;Reviewed-by: Stephen Boyd &lt;sboyd@kernel.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/lib/kunit/Kconfig</description>
        <pubDate>Mon, 23 Sep 2019 09:02:31 +0000</pubDate>
        <dc:creator>Brendan Higgins &lt;brendanhiggins@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
