mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "André Almeida" <andrealmeid@collabora.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Darren Hart <dvhart@infradead.org>,
	linux-kernel@vger.kernel.org
Cc: kernel@collabora.com, linux-kselftest@vger.kernel.org,
	shuah@kernel.org, "André Almeida" <andrealmeid@collabora.com>
Subject: [PATCH 0/2] selftests: futex: Improve timeout testing
Date: Tue, 27 Apr 2021 10:53:26 -0300	[thread overview]
Message-ID: <20210427135328.11013-1-andrealmeid@collabora.com> (raw)

This small series expands futex timeout selftests by checking if all
operations that allows timeouts works as expected. When some version of
Thomas' series "futex: Bugfixes and FUTEX_LOCK_PI2"[0] get merged, I'll
add the new rules to the timeout test. This test should be used to check
for regressions when modifying the timeout path or changing the
interface.

Additionally, fix a bug in the Makefile that can be found when compiling
selftests with new operations, like the one defined at [0] or from the
futex2 patchset.

[0] https://lore.kernel.org/lkml/20210422194417.866740847@linutronix.de/

André Almeida (2):
  selftests: futex: Correctly include headers dirs
  selftests: futex: Expand timeout test

 .../selftests/futex/functional/Makefile       |   3 +-
 .../futex/functional/futex_wait_timeout.c     | 126 +++++++++++++++---
 2 files changed, 112 insertions(+), 17 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-04-27 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 13:53 André Almeida [this message]
2021-04-27 13:53 ` [PATCH 1/2] selftests: futex: Correctly include headers dirs André Almeida
2021-05-12 18:50   ` [tip: locking/core] " tip-bot2 for André Almeida
2021-04-27 13:53 ` [PATCH 2/2] selftests: futex: Expand timeout test André Almeida
2021-05-12 18:50   ` [tip: locking/core] " tip-bot2 for André Almeida

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=20210427135328.11013-1-andrealmeid@collabora.com \
    --to=andrealmeid@collabora.com \
    --cc=dvhart@infradead.org \
    --cc=kernel@collabora.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    /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®