From: Gabriele Paoloni <gpaoloni@redhat.com>
To: shuah@kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org, gregkh@linuxfoundation.org
Cc: linux-mm@kvack.org, safety-architecture@lists.elisa.tech,
acarmina@redhat.com, kstewart@linuxfoundation.org,
chuckwolber@gmail.com, Gabriele Paoloni <gpaoloni@redhat.com>
Subject: [RFC PATCH v2 0/3] Add testable code specifications
Date: Wed, 10 Sep 2025 18:59:57 +0200 [thread overview]
Message-ID: <20250910170000.6475-1-gpaoloni@redhat.com> (raw)
[1] was an initial proposal defining testable code specifications for
some functions in /drivers/char/mem.c.
However a Guideline to write such specifications was missing and test
cases tracing to such specifications were missing.
This patchset represents a next step and is organised as follows:
- patch 1/3 contains the Guideline for writing code specifications
- patch 2/3 contains examples of code specfications defined for some
functions of drivers/char/mem.c
- patch 3/3 contains examples of selftests that map to some code
specifications of patch 2/3
[1] https://lore.kernel.org/all/20250821170419.70668-1-gpaoloni@redhat.com/
---
Changes from v1:
1) Added a Guideline to write code specifications in the Linux Kernel
Documentation
2) Addressed Greg KH comments in /drivers/char/mem.c
3) Added example of test cases mapping to the code specifications in
/drivers/char/mem.c
---
Alessandro Carminati (1):
selftests/devmem: initial testset
Gabriele Paoloni (2):
Documentation: add guidelines for writing testable code specifications
/dev/mem: Add initial documentation of memory_open() and mem_fops
.../doc-guide/code-specifications.rst | 208 +++++++
Documentation/doc-guide/index.rst | 1 +
drivers/char/mem.c | 231 ++++++-
tools/testing/selftests/Makefile | 1 +
tools/testing/selftests/devmem/Makefile | 13 +
tools/testing/selftests/devmem/debug.c | 25 +
tools/testing/selftests/devmem/debug.h | 14 +
tools/testing/selftests/devmem/devmem.c | 200 ++++++
tools/testing/selftests/devmem/ram_map.c | 250 ++++++++
tools/testing/selftests/devmem/ram_map.h | 38 ++
tools/testing/selftests/devmem/secret.c | 46 ++
tools/testing/selftests/devmem/secret.h | 13 +
tools/testing/selftests/devmem/tests.c | 569 ++++++++++++++++++
tools/testing/selftests/devmem/tests.h | 45 ++
tools/testing/selftests/devmem/utils.c | 379 ++++++++++++
tools/testing/selftests/devmem/utils.h | 119 ++++
16 files changed, 2146 insertions(+), 6 deletions(-)
create mode 100644 Documentation/doc-guide/code-specifications.rst
create mode 100644 tools/testing/selftests/devmem/Makefile
create mode 100644 tools/testing/selftests/devmem/debug.c
create mode 100644 tools/testing/selftests/devmem/debug.h
create mode 100644 tools/testing/selftests/devmem/devmem.c
create mode 100644 tools/testing/selftests/devmem/ram_map.c
create mode 100644 tools/testing/selftests/devmem/ram_map.h
create mode 100644 tools/testing/selftests/devmem/secret.c
create mode 100644 tools/testing/selftests/devmem/secret.h
create mode 100644 tools/testing/selftests/devmem/tests.c
create mode 100644 tools/testing/selftests/devmem/tests.h
create mode 100644 tools/testing/selftests/devmem/utils.c
create mode 100644 tools/testing/selftests/devmem/utils.h
--
2.48.1
next reply other threads:[~2025-09-10 17:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 16:59 Gabriele Paoloni [this message]
2025-09-10 16:59 ` [RFC v2 PATCH 1/3] Documentation: add guidelines for writing testable code specifications Gabriele Paoloni
2025-09-15 22:33 ` Jonathan Corbet
2025-09-17 15:24 ` Gabriele Paoloni
2025-10-20 19:35 ` David Hildenbrand
2025-10-20 20:54 ` Chuck Wolber
2025-10-20 21:02 ` Chuck Wolber
2025-10-21 15:37 ` David Hildenbrand
2025-10-21 16:27 ` Gabriele Paoloni
2025-10-21 16:34 ` David Hildenbrand
2025-10-21 16:43 ` Gabriele Paoloni
2025-09-10 16:59 ` [RFC v2 PATCH 2/3] /dev/mem: Add initial documentation of memory_open() and mem_fops Gabriele Paoloni
2025-09-15 22:39 ` Jonathan Corbet
2025-09-16 7:29 ` Chuck Wolber
2025-09-17 15:38 ` Gabriele Paoloni
2025-09-10 17:00 ` [RFC v2 PATCH 3/3] selftests/devmem: initial testset Gabriele Paoloni
2025-10-21 7:35 ` Greg KH
2025-10-21 17:40 ` Alessandro Carminati
2025-10-21 7:35 ` [RFC PATCH v2 0/3] Add testable code specifications Greg KH
2025-10-21 9:42 ` Gabriele Paoloni
2025-10-21 16:46 ` Greg KH
2025-10-22 14:06 ` Gabriele Paoloni
2025-10-22 17:13 ` Greg KH
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=20250910170000.6475-1-gpaoloni@redhat.com \
--to=gpaoloni@redhat.com \
--cc=acarmina@redhat.com \
--cc=chuckwolber@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=safety-architecture@lists.elisa.tech \
--cc=shuah@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).