linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Clark Williams <williams@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 4.0.4-rt1
Date: Tue, 26 May 2015 10:43:43 -0500	[thread overview]
Message-ID: <20150526104343.51fad474@sluggy> (raw)
In-Reply-To: <20150526111924.20836deb@gandalf.local.home>

On Tue, 26 May 2015 11:19:24 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:

> On Tue, 26 May 2015 08:48:02 -0500
> Clark Williams <williams@redhat.com> wrote:
> 
> 
> > Change the WARN_ON to WARN_ON_NORT
> 
> Do we have a WARN_ON_NORT? I see a WARN_ON_NONRT, but not a
> WARN_ON_NORT. Does this compile?
> 
> -- Steve

Sigh. Of course not. Reupdated patch (and yes this one compiles):

From: Clark Williams <williams@redhat.com>
Date: Thu, 21 May 2015 12:51:53 -0500
Subject: [PATCH] [rt] i915: bogus warning from i915 when running on PREEMPT_RT

The i915 driver has a 'WARN_ON(!in_interrupt())' in the display
handler, which whines constanly on the RT kernel (since the interrupt
is actually handled in a threaded handler and not actual interrupt
context).

Change the WARN_ON to WARN_ON_NORT

Signed-off-by: Clark Williams <williams@redhat.com>
---
 drivers/gpu/drm/i915/intel_display.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
index f75173c20f47..30b1d16caa0d 100644
--- a/drivers/gpu/drm/i915/intel_display.c
+++ b/drivers/gpu/drm/i915/intel_display.c
@@ -9745,7 +9745,7 @@ void intel_check_page_flip(struct drm_device *dev, int pipe)
 	struct drm_crtc *crtc = dev_priv->pipe_to_crtc_mapping[pipe];
 	struct intel_crtc *intel_crtc = to_intel_crtc(crtc);
 
-	WARN_ON(!in_interrupt());
+	WARN_ON_NONRT(!in_interrupt());
 
 	if (crtc == NULL)
 		return;
-- 
2.1.0


  reply	other threads:[~2015-05-26 15:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 21:39 [ANNOUNCE] 4.0.4-rt1 Sebastian Andrzej Siewior
2015-05-19 22:33 ` Carsten Emde
2015-05-19 22:51   ` Pavel Vasilyev
2015-05-20  7:12   ` Sebastian Andrzej Siewior
2015-05-20 13:18   ` Daniel Wagner
2015-05-19 22:48 ` Pavel Vasilyev
2015-05-20  3:14 ` Mike Galbraith
2015-05-20 10:06 ` Pavel Vasilyev
2015-06-11 12:09   ` Sebastian Andrzej Siewior
2015-05-23 11:57 ` Pavel Vasilyev
2015-06-11 12:08   ` Sebastian Andrzej Siewior
2015-05-24 20:59 ` Fernando Lopez-Lezcano
2015-06-11 12:22   ` [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement Sebastian Andrzej Siewior
2015-06-11 13:04     ` Mats Karrman
2015-06-11 13:14       ` [PATCH v2] " Sebastian Andrzej Siewior
2015-06-12  7:22         ` Vinod Koul
2015-06-12 10:37         ` Mark Brown
2015-05-26 13:34 ` [ANNOUNCE] 4.0.4-rt1 Clark Williams
2015-05-26 13:38   ` Steven Rostedt
2015-05-26 13:48     ` Clark Williams
2015-05-26 14:49       ` Mike Galbraith
2015-05-26 15:19       ` Steven Rostedt
2015-05-26 15:43         ` Clark Williams [this message]
2015-05-26 19:41           ` Fernando Lopez-Lezcano
2015-05-29  1:56             ` Fernando Lopez-Lezcano
2015-06-09 16:45               ` Fernando Lopez-Lezcano
2015-06-09 22:05                 ` Pavel Vasilyev
2015-06-10  2:41                   ` Mike Galbraith
2015-06-10  3:10                   ` Fernando Lopez-Lezcano
2015-06-09 22:10                 ` Pavel Vasilyev
2015-06-11 12:38               ` Sebastian Andrzej Siewior
2015-05-28  8:41           ` Joakim Hernberg
2015-06-11 12:34           ` Sebastian Andrzej Siewior
2015-05-27  9:44 ` Joakim Hernberg
2015-05-27 10:19   ` Jeremy Jongepier
2015-05-28  8:33     ` Joakim Hernberg
2015-05-27 15:50   ` Ralf Mardorf

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=20150526104343.51fad474@sluggy \
    --to=williams@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).