mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Shuah Khan <shuah@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	"Paul E. McKenney" <paulmck@kernel.org>, Willy Tarreau <w@1wt.eu>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mark Brown <broonie@kernel.org>
Subject: [PATCH v2 0/3] tools/nolibc: Support vprintf() so we can use kselftest.h with nolibc
Date: Thu, 06 Apr 2023 17:19:09 +0100	[thread overview]
Message-ID: <20230405-kselftest-nolibc-v2-0-2ac2495814b5@kernel.org> (raw)

At present the kselftest header can't be used with nolibc since it makes
use of vprintf() which is not available in nolibc.  Fortunately nolibc
has a vfprintf() so we can just wrap that in order to allow kselftests
to be built with nolibc and still use the standard kselftest headers
with a small change to prevent the inclusion of the standard libc
headers.  This allows us to avoid open coding of KTAP output for
selftests that need to use nolibc in order to test interfaces that are
controlled by libc, we've got several open coded examples of this in the
tree already.

As an example of using this the existing za-fork test is converted to
use kselftest.h.  The changes to kselftest and nolibc don't have any
interaction until they are used by a test so could be merged separately
if desired.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Changes in v2:
- Turns out nolibc has a vfprintf() already which we can use so do that.
- Link to v1: https://lore.kernel.org/r/20230405-kselftest-nolibc-v1-0-63fbcd70b202@kernel.org

---
Mark Brown (3):
      tools/nolibc/stdio: Implement vprintf()
      kselftest: Support nolibc
      kselftest/arm64: Convert za-fork to use kselftest.h

 tools/include/nolibc/stdio.h               |  6 ++
 tools/testing/selftests/arm64/fp/Makefile  |  2 +-
 tools/testing/selftests/arm64/fp/za-fork.c | 88 ++++++------------------------
 tools/testing/selftests/kselftest.h        |  2 +
 4 files changed, 25 insertions(+), 73 deletions(-)
---
base-commit: e8d018dd0257f744ca50a729e3d042cf2ec9da65
change-id: 20230405-kselftest-nolibc-cb2ce0446d09

Best regards,
-- 
Mark Brown <broonie@kernel.org>


             reply	other threads:[~2023-04-06 16:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 16:19 Mark Brown [this message]
2023-04-06 16:19 ` [PATCH v2 1/3] tools/nolibc/stdio: Implement vprintf() Mark Brown
2023-04-06 18:26   ` Willy Tarreau
2023-04-06 18:43     ` Paul E. McKenney
2023-04-10 18:30       ` Shuah Khan
2023-04-11 14:31         ` Mark Brown
2023-04-11 15:03           ` Will Deacon
2023-04-11 15:13             ` Mark Brown
2023-04-11 16:44               ` Paul E. McKenney
2023-04-11 18:54                 ` Shuah Khan
2023-04-11 21:06                   ` Will Deacon
2023-04-06 16:19 ` [PATCH v2 2/3] kselftest: Support nolibc Mark Brown
2023-04-06 16:19 ` [PATCH v2 3/3] kselftest/arm64: Convert za-fork to use kselftest.h Mark Brown

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=20230405-kselftest-nolibc-v2-0-2ac2495814b5@kernel.org \
    --to=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=shuah@kernel.org \
    --cc=w@1wt.eu \
    --cc=will@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®