From: Shuah Khan <skhan@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: thomas.lendacky@amd.com, David Gow <davidgow@google.com>,
"x86@kernel.org" <x86@kernel.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: sev_es_trampoline_start undefined symbol referenced errors during kunit run
Date: Tue, 15 Apr 2025 13:06:49 -0600 [thread overview]
Message-ID: <8b08e040-fee7-4344-8ba6-bbbd4f73e318@linuxfoundation.org> (raw)
In-Reply-To: <20250415180128.GJZ_6e-B3yFuwmqWWS@fat_crate.local>
On 4/15/25 12:01, Borislav Petkov wrote:
> On Tue, Apr 15, 2025 at 08:25:09AM -0600, Shuah Khan wrote:
>> ./tools/testing/kunit/kunit.py run --arch x86_64
>> or
>> ./tools/testing/kunit/kunit.py run --alltests --arch x86_64
>>
>> The tree I see this every single time I do my tree testing.
>
> Doesn't reproduce here:
>
> # ./tools/testing/kunit/kunit.py run --arch x86_64 > log.00 2>&1
> # ./tools/testing/kunit/kunit.py run --alltests --arch x86_64 > log.01 2>&1
> # grep -i error log.*
> log.00:[19:04:52] [PASSED] error_pointer
> log.01:[19:44:06] [PASSED] error_pointer
>
Does your arch/x86/realmode/rm/pasyms.h has reference to sev_es_trampoline_start?
The one in my tree has it.
arch/x86/realmode/rm/pasyms.h:pa_sev_es_trampoline_start = sev_es_trampoline_start
thanks,
-- Shuah
next prev parent reply other threads:[~2025-04-15 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 22:28 sev_es_trampoline_start undefined symbol referenced errors during kunit run Shuah Khan
2025-04-14 23:00 ` Borislav Petkov
2025-04-15 8:54 ` David Gow
2025-04-15 14:25 ` Shuah Khan
2025-04-15 18:01 ` Borislav Petkov
2025-04-15 19:06 ` Shuah Khan [this message]
2025-04-15 22:17 ` Borislav Petkov
2025-04-15 22:29 ` Shuah Khan
2025-04-16 0:32 ` David Gow
2025-04-16 1:09 ` Shuah Khan
2025-04-16 9:18 ` Borislav Petkov
2025-04-16 0:54 ` 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=8b08e040-fee7-4344-8ba6-bbbd4f73e318@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@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