linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <greg@kroah.com>
To: Joel Fernandes <agnel.joel@gmail.com>
Cc: linux-rt-users@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kernelnewbies <kernelnewbies@nl.linux.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: RFC on fixing mutex spinning on owner
Date: Wed, 16 Mar 2016 16:35:30 -0700	[thread overview]
Message-ID: <20160316233530.GA8731@kroah.com> (raw)
In-Reply-To: <CAD=GYpbHjcsuQSnNPL4SCv-r=Me6oiH7dJ98a64udbakWLaUjQ@mail.gmail.com>

On Wed, Mar 16, 2016 at 04:22:17PM -0700, Joel Fernandes wrote:
> Hi,
> 
> On a fairly recent kernel and android userspace, I am seeing that with
> i915 driver is in a spin loop waiting for mutex owner to release it
> (mutex_spin_on_owner).

Why not provide a backtrace to the drm and i915 developers so that they
can work on this?  The mailing lists you sent this to can't do much
about this, sorry...

thanks,

greg k-h

  reply	other threads:[~2016-03-16 23:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 23:22 RFC on fixing mutex spinning on owner Joel Fernandes
2016-03-16 23:35 ` Greg Kroah-Hartman [this message]
2016-03-16 23:38   ` Joel Fernandes
2016-03-17  2:17     ` Steven Rostedt
2016-03-17  5:35       ` Joel Fernandes
2016-03-17 12:08         ` Steven Rostedt
2016-03-17  7:36       ` Peter Zijlstra
2016-03-17  8:05         ` Nicholas Mc Guire
2016-03-17 10:18           ` Peter Zijlstra
2016-03-17 11:16             ` Thomas Gleixner
2016-03-17 12:06               ` Steven Rostedt
2016-03-17 12:13                 ` Peter Zijlstra
2016-03-17 13:32                   ` Thomas Gleixner
2016-03-17 15:36                     ` Nicholas Mc Guire

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=20160316233530.GA8731@kroah.com \
    --to=greg@kroah.com \
    --cc=agnel.joel@gmail.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).