From: Petteri Aimonen <jpa@git.mail.kapsi.fi>
To: Andy Lutomirski <luto@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>, Shuah Khan <shuah@kernel.org>,
Dave Hansen <dave.hansen@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch/x86: reset MXCSR to default in kernel_fpu_begin()
Date: Thu, 11 Jun 2020 10:36:08 +0300 [thread overview]
Message-ID: <20200611073607.GH17423@lakka.kapsi.fi> (raw)
In-Reply-To: <CALCETrURrz=L5f-HHF3kZtUqV0dw5hAEGqSxWTsOjoZvOKaccw@mail.gmail.com>
Hi,
> How about putting the file you frob in
> /sys/kernel/debug/selftest_helpers/something_or_other. The idea would
> be that /sys/kernel/debug/selftest_helpers would be a general place
> for kernel helpers needed to make selftests work.
Seems like this is the consensus for now.
Any opinions on whether the module should remove "selftest_helpers"
directory on unloading, or not?
1) Removing would break if other test modules will use the same dir.
2) Not removing will leave the directory dangling.
3) Remove only if empty is one option, though I'm unsure how to
cleanly check if debugfs directory is empty.
4) E.g. /sys/kernel/debug/x86/ is created centrally and a symbol is
exported for its dentry. But I'm not sure if it really makes sense
to add another exported symbol just for selftest_helpers.
--
Petteri
next prev parent reply other threads:[~2020-06-11 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 10:11 [PATCH] arch/x86: reset MXCSR to default in kernel_fpu_begin() Borislav Petkov
2020-06-02 10:29 ` Petteri Aimonen
2020-06-02 10:56 ` Borislav Petkov
2020-06-02 17:03 ` Andy Lutomirski
2020-06-02 17:27 ` Shuah Khan
2020-06-02 19:50 ` Andy Lutomirski
2020-06-02 20:25 ` Shuah Khan
2020-06-03 5:19 ` Petteri Aimonen
2020-06-11 14:38 ` Shuah Khan
2020-06-11 7:36 ` Petteri Aimonen [this message]
2020-06-11 9:18 ` Borislav Petkov
2020-06-11 14:19 ` Andy Lutomirski
2020-06-11 14:50 ` 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=20200611073607.GH17423@lakka.kapsi.fi \
--to=jpa@git.mail.kapsi.fi \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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;
as well as URLs for NNTP newsgroup(s).