public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mike Galbraith <bitbucket@online.de>,
	RT <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 3.[68]-rt: CONFIG_PROVE_LOCKING + CONFIG_DEBUG_FORCE_WEAK_PER_CPU = boot time swap_lock deadlock
Date: Fri, 26 Apr 2013 11:16:56 +0200	[thread overview]
Message-ID: <20130426091656.GD20927@linutronix.de> (raw)
In-Reply-To: <1366685096.9609.145.camel@gandalf.local.home>

* Steven Rostedt | 2013-04-22 22:44:56 [-0400]:

>When I built with CONFIG_DEBUG_FORCE_WEAK_PER_CPU it had issues with the
>swap lock. Can you try this patch? What you showed looks different, but
>did that happen with the updates you made?

Steven, could you please resend it with a sign-off-by and maybe a little
description? It seems to fix the same problen in v3.8.

>-- Steve

Sebastian

  parent reply	other threads:[~2013-04-26  9:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 11:07 3.[68]-rt: CONFIG_PROVE_LOCKING + CONFIG_DEBUG_FORCE_WEAK_PER_CPU = boot time swap_lock deadlock Mike Galbraith
2013-04-23  2:44 ` Steven Rostedt
2013-04-23  2:47   ` Steven Rostedt
2013-04-23  3:13     ` Mike Galbraith
2013-04-23 16:00       ` Steven Rostedt
2013-04-23 19:06         ` Mike Galbraith
2013-04-24  5:47         ` Mike Galbraith
2013-04-23  3:08   ` Mike Galbraith
2013-04-26  9:16   ` Sebastian Andrzej Siewior [this message]
2013-04-26 12:13     ` Steven Rostedt
2013-04-26 13:38       ` Sebastian Andrzej Siewior
2013-04-26 13:52         ` Steven Rostedt
2013-04-26 14:04           ` Sebastian Andrzej Siewior
2013-04-26 14:15             ` Steven Rostedt
2013-04-26 14:49               ` Sebastian Andrzej Siewior

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=20130426091656.GD20927@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=bitbucket@online.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.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