From: Borislav Petkov <bp@alien8.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Andy Lutomirski <luto@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>,
Peter Zijlstra <peterz@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Milosz Wasilewski <milosz.wasilewski@linaro.org>
Subject: Re: [RFC] selftests/x86: Add test_vsyscall
Date: Tue, 9 Jan 2018 12:51:42 +0100 [thread overview]
Message-ID: <20180109115136.sberq4wk2w63b73j@pd.tnic> (raw)
In-Reply-To: <CA+G9fYvZSew8Sg=Xh0u_KDLapjPYnz+PnFOJe5UZ0opa9=VH=Q@mail.gmail.com>
On Tue, Jan 09, 2018 at 05:15:15PM +0530, Naresh Kamboju wrote:
> We do not want to change the kernel command lines dynamically on
> the test bench. It will be hard to test this case in automated setup.
> Because with a given setup we run all selftests in a single go.
Those cmdline parameters are already upstream, without that test patch.
If you wanna test all, you'd have to change the cmdline or rebuilt the
kernel three times with each of those set, alternatingly:
CONFIG_LEGACY_VSYSCALL_NATIVE
CONFIG_LEGACY_VSYSCALL_EMULATE
CONFIG_LEGACY_VSYSCALL_NONE
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-01-09 11:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 5:38 Andy Lutomirski
2018-01-05 12:33 ` Borislav Petkov
2018-01-05 17:53 ` Andy Lutomirski
2018-01-05 18:23 ` Borislav Petkov
2018-01-05 18:47 ` Andy Lutomirski
2018-01-05 19:05 ` Borislav Petkov
2018-01-05 13:40 ` Borislav Petkov
2018-01-05 18:01 ` Andy Lutomirski
2018-01-05 18:30 ` Borislav Petkov
2018-01-05 18:45 ` Andy Lutomirski
2018-01-05 19:10 ` Borislav Petkov
2018-01-05 19:22 ` Andy Lutomirski
2018-01-05 19:28 ` Borislav Petkov
2018-01-05 20:10 ` Andy Lutomirski
2018-01-09 11:45 ` Naresh Kamboju
2018-01-09 11:51 ` Borislav Petkov [this message]
2018-01-09 21:25 ` Shuah Khan
2018-01-09 21:27 ` Andy Lutomirski
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=20180109115136.sberq4wk2w63b73j@pd.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=milosz.wasilewski@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.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®