[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1581094694-6513-3-git-send-email-alan.maguire@oracle.com>
Date: Fri, 7 Feb 2020 16:58:14 +0000
From: Alan Maguire <alan.maguire@...cle.com>
To: brendanhiggins@...gle.com, gregkh@...uxfoundation.org,
shuah@...nel.org
Cc: linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
corbet@....net, davidgow@...gle.com, frowand.list@...il.com
Subject: [PATCH v3 kunit-next 2/2] kunit: update documentation to describe debugfs representation
Documentation should describe debugfs layout and semantics.
Signed-off-by: Alan Maguire <alan.maguire@...cle.com>
---
Documentation/dev-tools/kunit/usage.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/dev-tools/kunit/usage.rst b/Documentation/dev-tools/kunit/usage.rst
index 7cd56a1..b2b958a 100644
--- a/Documentation/dev-tools/kunit/usage.rst
+++ b/Documentation/dev-tools/kunit/usage.rst
@@ -590,3 +590,15 @@ able to run one test case per invocation.
.. TODO(brendanhiggins@...gle.com): Add an actual example of an architecture
dependent KUnit test.
+
+KUnit debugfs representation
+============================
+When kunit test suites are initialized, they create an associated directory
+in /sys/kernel/debug/kunit/<test-suite>. The directory contains one file
+
+- results: "cat results" displays results of last test run
+
+The debugfs representation is primarily of use when kunit test suites are
+run in a native environment, either as modules or builtin. Having a way
+to display results like this is valuable as otherwise results can be
+intermixed with other events in dmesg output.
--
1.8.3.1
Powered by blists - more mailing lists