linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Gray <bgray@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Benjamin Gray <bgray@linux.ibm.com>
Subject: [PATCH v1 0/4] Improve ptrace selftest usability
Date: Tue, 25 Jul 2023 10:58:37 +1000	[thread overview]
Message-ID: <20230725005841.28854-1-bgray@linux.ibm.com> (raw)

While trying to test changes to the breakpoint implementation in the kernel, I
tried to run the ptrace tests and met many unexplained skips and failures.

This series addresses the pain points of trying to run these tests and learn
what they are doing.

Benjamin Gray (4):
  Documentation/powerpc: Fix ptrace request names
  selftests/powerpc/ptrace: Explain why tests are skipped
  selftests/powerpc/ptrace: Fix typo in pid_max search error
  selftests/powerpc/ptrace: Declare test temporary variables as volatile

 Documentation/powerpc/ptrace.rst              |  8 +++---
 .../testing/selftests/powerpc/ptrace/child.h  |  4 +--
 .../selftests/powerpc/ptrace/core-pkey.c      |  2 +-
 .../selftests/powerpc/ptrace/perf-hwbreak.c   |  2 +-
 .../selftests/powerpc/ptrace/ptrace-hwbreak.c | 26 +++++++++----------
 .../powerpc/ptrace/ptrace-perf-hwbreak.c      |  6 ++---
 .../selftests/powerpc/ptrace/ptrace-pkey.c    |  2 +-
 .../selftests/powerpc/ptrace/ptrace-tar.c     |  2 +-
 .../selftests/powerpc/ptrace/ptrace-tm-gpr.c  |  4 +--
 .../powerpc/ptrace/ptrace-tm-spd-gpr.c        |  4 +--
 .../powerpc/ptrace/ptrace-tm-spd-tar.c        |  4 +--
 .../powerpc/ptrace/ptrace-tm-spd-vsx.c        |  4 +--
 .../selftests/powerpc/ptrace/ptrace-tm-spr.c  |  4 +--
 .../selftests/powerpc/ptrace/ptrace-tm-tar.c  |  4 +--
 .../selftests/powerpc/ptrace/ptrace-tm-vsx.c  |  4 +--
 .../selftests/powerpc/ptrace/ptrace-vsx.c     |  2 +-
 16 files changed, 41 insertions(+), 41 deletions(-)

--
2.41.0

             reply	other threads:[~2023-07-25  1:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  0:58 Benjamin Gray [this message]
2023-07-25  0:58 ` [PATCH v1 1/4] Documentation/powerpc: Fix ptrace request names Benjamin Gray
2023-07-25  0:58 ` [PATCH v1 2/4] selftests/powerpc/ptrace: Explain why tests are skipped Benjamin Gray
2023-07-25  0:58 ` [PATCH v1 3/4] selftests/powerpc/ptrace: Fix typo in pid_max search error Benjamin Gray
2023-07-25  0:58 ` [PATCH v1 4/4] selftests/powerpc/ptrace: Declare test temporary variables as volatile Benjamin Gray
2023-08-10  6:02 ` (subset) [PATCH v1 0/4] Improve ptrace selftest usability Michael Ellerman
2023-08-23 11:55 ` Michael Ellerman

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=20230725005841.28854-1-bgray@linux.ibm.com \
    --to=bgray@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.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).