From: Daniel Latypov <dlatypov@google.com>
To: brendanhiggins@google.com, davidgow@google.com
Cc: linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com,
corbet@lwn.net, linux-doc@vger.kernel.org,
Daniel Latypov <dlatypov@google.com>
Subject: [PATCH 2/3] Documentation: kunit: move mention of --jobs flag lower
Date: Fri, 3 Jun 2022 12:56:25 -0700 [thread overview]
Message-ID: <20220603195626.121922-2-dlatypov@google.com> (raw)
In-Reply-To: <20220603195626.121922-1-dlatypov@google.com>
Commit ad659ccb5412 ("kunit: tool: Default --jobs to number of CPUs")
changed the --jobs flag from a hard-coded value of 8 to basically
`nproc`.
Therefore, most users should probably not need to bother to tweak this
flag. Having it near the top of the page is more noise than anything.
Signed-off-by: Daniel Latypov <dlatypov@google.com>
---
Documentation/dev-tools/kunit/run_wrapper.rst | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/dev-tools/kunit/run_wrapper.rst b/Documentation/dev-tools/kunit/run_wrapper.rst
index 653985ce9cae..1fccf2e099f7 100644
--- a/Documentation/dev-tools/kunit/run_wrapper.rst
+++ b/Documentation/dev-tools/kunit/run_wrapper.rst
@@ -30,10 +30,9 @@ We may want to use the following options:
.. code-block::
- ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all
+ ./tools/testing/kunit/kunit.py run --timeout=30
- ``--timeout`` sets a maximum amount of time for tests to run.
-- ``--jobs`` sets the number of threads to build the kernel.
kunit_tool will generate a ``.kunitconfig`` with a default
configuration, if no other ``.kunitconfig`` file exists
@@ -237,6 +236,9 @@ command line arguments:
compiling a kernel (using ``build`` or ``run`` commands). For example:
to enable compiler warnings, we can pass ``--make_options W=1``.
+- ``--jobs``: The ``-j`` argument to ``make`` when building the kernel.
+ Defaults to the same value as ``nproc``.
+
- ``--alltests``: Builds a UML kernel with all config options enabled
using ``make allyesconfig``. This allows us to run as many tests as
possible.
--
2.36.1.255.ge46751e96f-goog
next prev parent reply other threads:[~2022-06-03 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 19:56 [PATCH 1/3] Documentation: kunit: remove duplicate kunit-tool.rst Daniel Latypov
2022-06-03 19:56 ` Daniel Latypov [this message]
2022-06-03 19:56 ` [PATCH 3/3] Documentation: kunit: rewrite section on .kunitconfig Daniel Latypov
2022-06-24 19:47 ` [PATCH 1/3] Documentation: kunit: remove duplicate kunit-tool.rst Jonathan Corbet
2022-06-24 19:58 ` Daniel Latypov
2022-06-24 22:36 ` Shuah Khan
2022-06-24 22:43 ` Jonathan Corbet
2022-06-24 22:51 ` Shuah Khan
2022-06-24 23:40 ` Daniel Latypov
2022-06-27 22:28 ` Jonathan Corbet
2022-06-29 16:45 ` Shuah Khan
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=20220603195626.121922-2-dlatypov@google.com \
--to=dlatypov@google.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).