mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Darren Hart <darren@dvhart.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip 0/2] futex: Fault/error injection capabilities
Date: Mon, 13 Jul 2015 02:41:50 -0700	[thread overview]
Message-ID: <1436780510.27924.71.camel@stgolabs.net> (raw)
In-Reply-To: <1435645562-975-1-git-send-email-dave@stgolabs.net>

Ingo, any thoughts about this?

Thanks.

On Mon, 2015-06-29 at 23:26 -0700, Davidlohr Bueso wrote:
> Hello,
> 
> I've been wanting this for a while to improve overall futex
> testing. I must say that I checked rather late when I was
> nearly finished with patch 2 if something similar for futexes
> had already been proposed. Sure enough, in 2009 this was discussed[1].
> 
> Coincidently, I also took the natural approach of making use of
> our fault-injection machinery. I have no idea if perf nowadays does
> such things, and if it does not, I honestly don't have the bandwidth
> to do it Ingo's preferred way -- when there is nothing wrong with
> this approach, imho (0 overhead). Anyway, here's a working patch.
> 
> Patch 1 is merely a trivial add-on.
> 
> [1]: https://lwn.net/Articles/364742/
> 
> Thanks!
> 
> Davidlohr Bueso (2):
>   futex: Enhance comments in futex_lock_pi() for blocking paths
>   futex: Fault/error injection capabilities
> 
>  Documentation/fault-injection/fault-injection.txt |  11 +++
>  kernel/futex.c                                    | 100 +++++++++++++++++++++-
>  lib/Kconfig.debug                                 |   7 ++
>  3 files changed, 114 insertions(+), 4 deletions(-)
> 



  parent reply	other threads:[~2015-07-13  9:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  6:26 Davidlohr Bueso
2015-06-30  6:26 ` [PATCH 1/2] futex: Enhance comments in futex_lock_pi() for blocking paths Davidlohr Bueso
2015-07-20 10:57   ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2015-07-20 21:24     ` Darren Hart
2015-07-20 21:59       ` Davidlohr Bueso
2015-07-20 22:02         ` Darren Hart
2015-06-30  6:26 ` [PATCH 2/2] futex: Fault/error injection capabilities Davidlohr Bueso
2015-07-20 10:57   ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2015-07-20 14:35     ` Dave Jones
2015-07-13  9:41 ` Davidlohr Bueso [this message]
2015-07-16 12:55   ` [PATCH -tip 0/2] " Thomas Gleixner

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=1436780510.27924.71.camel@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=darren@dvhart.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.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®