From: Pengfei Xu <pengfei.xu@intel.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
shuah@kernel.org,
linux-kselftest <linux-kselftest@vger.kernel.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
jithu.joseph@intel.com, Pengfei Xu <pengfei.xu@intel.com>,
ashok.raj@intel.com, sathyanarayanan.kuppuswamy@intel.com
Subject: [PATCH v2 0/4] add tests to verify IFS (In Field Scan) driver functionality
Date: Fri, 31 May 2024 15:53:46 +0800 [thread overview]
Message-ID: <cover.1717137348.git.pengfei.xu@intel.com> (raw)
To verify IFS (In Field Scan [1]) driver functionality, add the following 6
test cases:
1. Verify that IFS sysfs entries are created after loading the IFS module
2. Check if loading an invalid IFS test image fails and loading a valid
one succeeds
3. Perform IFS scan test on each CPU using all the available image files
4. Perform IFS scan with first test image file on a random CPU for 3
rounds
5. Perform IFS ARRAY BIST(Board Integrated System Test) test on each CPU
6. Perform IFS ARRAY BIST test on a random CPU for 3 rounds
These are not exhaustive, but some minimal test runs to check various
parts of the driver. Some negative tests are also included.
[1] https://docs.kernel.org/arch/x86/ifs.html
Pengfei Xu (4):
selftests: ifs: verify test interfaces are created by the driver
selftests: ifs: verify test image loading functionality
selftests: ifs: verify IFS scan test functionality
selftests: ifs: verify IFS ARRAY BIST functionality
MAINTAINERS | 1 +
tools/testing/selftests/Makefile | 1 +
.../drivers/platform/x86/intel/ifs/Makefile | 6 +
.../platform/x86/intel/ifs/test_ifs.sh | 494 ++++++++++++++++++
4 files changed, 502 insertions(+)
create mode 100644 tools/testing/selftests/drivers/platform/x86/intel/ifs/Makefile
create mode 100755 tools/testing/selftests/drivers/platform/x86/intel/ifs/test_ifs.sh
---
Changes:
v1 to v2:
- Rebase to v6.10 cycle kernel and resolve some code conflicts
- Improved checking of IFS ARRAY_BIST support by leveraging sysfs entry
methods (suggested by Ashok)
--
2.43.0
next reply other threads:[~2024-05-31 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 7:53 Pengfei Xu [this message]
2024-05-31 7:53 ` [PATCH v2 1/4] selftests: ifs: verify test interfaces are created by the driver Pengfei Xu
2024-05-31 7:53 ` [PATCH v2 2/4] selftests: ifs: verify test image loading functionality Pengfei Xu
2024-05-31 7:53 ` [PATCH v2 3/4] selftests: ifs: verify IFS scan test functionality Pengfei Xu
2024-05-31 7:53 ` [PATCH v2 4/4] selftests: ifs: verify IFS ARRAY BIST functionality Pengfei Xu
2024-06-19 0:53 ` [PATCH v2 0/4] add tests to verify IFS (In Field Scan) driver functionality Pengfei Xu
2024-07-11 1:42 ` Joseph, Jithu
2024-07-11 19:30 ` 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=cover.1717137348.git.pengfei.xu@intel.com \
--to=pengfei.xu@intel.com \
--cc=ashok.raj@intel.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@intel.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.