From: Michael Ellerman <mpe@ellerman.id.au>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: selftests: run all tests
Date: Tue, 23 Jan 2018 18:11:31 +1100 [thread overview]
Message-ID: <87372xoxr0.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180116115407.xqlu6bfvqcwoxszg@pd.tnic>
Borislav Petkov <bp@alien8.de> writes:
> On Tue, Jan 16, 2018 at 12:44:28PM +0100, Borislav Petkov wrote:
>> Ah, that was hidden in the included lib.mk, thanks.
>>
>> I wonder if we should make it more user-friendly by adding a help target
>> like for the main Makefile...
>
> One more point:
>
> What I do is copy the x86/ folder to a test box and run all tests there.
> If the lib.mk is not copied, run_tests is missing....
OK, that's not really supported I guess.
If you're happy building on your host system, you can do:
$ make -C tools/testing/selftests/ TARGETS=x86 install
And then you'll have:
$ find tools/testing/selftests/install/
tools/testing/selftests/install/
tools/testing/selftests/install/x86
tools/testing/selftests/install/x86/mpx-mini-test_64
tools/testing/selftests/install/x86/iopl_64
tools/testing/selftests/install/x86/sysret_rip_64
tools/testing/selftests/install/x86/protection_keys_64
tools/testing/selftests/install/x86/sysret_ss_attrs_64
tools/testing/selftests/install/x86/syscall_nt_64
tools/testing/selftests/install/x86/test_mremap_vdso_64
tools/testing/selftests/install/x86/ioperm_64
tools/testing/selftests/install/x86/ptrace_syscall_64
tools/testing/selftests/install/x86/sigreturn_64
tools/testing/selftests/install/x86/fsgsbase_64
tools/testing/selftests/install/x86/5lvl_64
tools/testing/selftests/install/x86/check_initial_reg_state_64
tools/testing/selftests/install/x86/ldt_gdt_64
tools/testing/selftests/install/x86/single_step_syscall_64
tools/testing/selftests/install/x86/test_vdso_64
tools/testing/selftests/install/run_kselftest.sh
You can rsync that wherever, and run it manually or with the
run_kselftest.sh script.
cheers
prev parent reply other threads:[~2018-01-23 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180115145942.s3dgy457xwhn6lwv@pd.tnic>
[not found] ` <87tvvmcp0u.fsf@concordia.ellerman.id.au>
2018-01-16 11:44 ` Borislav Petkov
2018-01-16 11:54 ` Borislav Petkov
2018-01-23 7:11 ` Michael Ellerman [this message]
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=87372xoxr0.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®