From: Shuah Khan <skhan@linuxfoundation.org>
To: brendan.higgins@linux.dev, davidgow@google.com, rmoar@google.com,
corbet@lwn.net
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] doc: kunit: add information about cleaning source trees
Date: Tue, 29 Apr 2025 16:27:11 -0600 [thread overview]
Message-ID: <7104475f60568f6a580b03d84e61abe311d63e46.1745965121.git.skhan@linuxfoundation.org> (raw)
In-Reply-To: <cover.1745965121.git.skhan@linuxfoundation.org>
If kunit run happens in a tree in which a x86_64 kernel was built,
the source tree could be dirty.
"make ARCH=um mrproper" will not clean the x86_64 build artifacts.
Running "make ARCH=x86_64 mrproper" is necessary to clean them.
Add this information to the documentation.
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
---
Documentation/dev-tools/kunit/start.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Documentation/dev-tools/kunit/start.rst b/Documentation/dev-tools/kunit/start.rst
index a98235326bab..568e29aebd6e 100644
--- a/Documentation/dev-tools/kunit/start.rst
+++ b/Documentation/dev-tools/kunit/start.rst
@@ -39,6 +39,18 @@ can run kunit_tool:
``make ARCH=um mrproper``, just be aware that this will delete the
current configuration and all generated files.
+ You may see the following error if a prior build leaves behind
+ header files which 'make ARCH=um mrproper' fails to clean:
+
+ "undefined symbol sev_es_trampoline_start referenced ..."
+
+ This is special case scenario when a prior x86_64 build populates
+ the source tree with arch/x86/realmode/rm/pasyms.h. This header
+ will not be cleaned by 'make ARCH=um mrproper'
+
+ If you encouter this problem, run 'make ARCH=x86_64 mrproper' to
+ remove generated header files.
+
If everything worked correctly, you should see the following:
.. code-block::
--
2.47.2
next prev parent reply other threads:[~2025-04-29 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 22:27 [PATCH 0/2] Update kunit doc and tool with tips to build errors Shuah Khan
2025-04-29 22:27 ` Shuah Khan [this message]
2025-04-29 22:29 ` [PATCH 1/2] doc: kunit: add information about cleaning source trees Randy Dunlap
2025-04-29 23:33 ` Shuah Khan
2025-04-29 22:27 ` [PATCH 2/2] kunit: add tips to clean source tree to build help message Shuah Khan
2025-04-29 22:49 ` Jonathan Corbet
2025-04-29 23:34 ` Shuah Khan
2025-04-30 3:54 ` David Gow
2025-04-30 21:25 ` Shuah Khan
2025-05-01 0:40 ` Shuah Khan
2025-04-30 5:18 ` Mauro Carvalho Chehab
2025-04-30 21:28 ` 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=7104475f60568f6a580b03d84e61abe311d63e46.1745965121.git.skhan@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=brendan.higgins@linux.dev \
--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 \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmoar@google.com \
--cc=workflows@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
all inboxes | Powered by JetHome®