From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Christoph Mathys <eraserix@gmail.com>,
Carsten Emde <C.Emde@osadl.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH v2] drm/i915: Do not flush caches on RT, print a warning instead
Date: Tue, 11 Jun 2013 13:42:21 +0200 [thread overview]
Message-ID: <51B70D1D.2000709@linutronix.de> (raw)
In-Reply-To: <20130610222215.GA27391@windriver.com>
On 06/11/2013 12:22 AM, Paul Gortmaker wrote:
> This thread reminded me of the i915 compile warning I'd seen earlier
> today. Fixing the warning does actually change the code produced.
>
> I'll let you guys who have the actual hardware have the joy of reading
> the asm and deciding whether the change is significant or not...
This warning looks like the open-coded some of the functions which are
different on RT. In the v3.8 RT I removed the open-coded crap.
>
> Paul.
Sebastian
next prev parent reply other threads:[~2013-06-11 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 16:45 [ANNOUNCE] 3.6.11.4-rt36 Steven Rostedt
2013-05-27 7:38 ` Christoph Mathys
2013-05-27 9:12 ` Christoph Mathys
[not found] ` <CALqGcGop=cpgSvcdmwE6QOSjo-JHBDGYpe2qyy3cxULfamgy+w@mail.gmail.com>
2013-06-07 20:34 ` Steven Rostedt
2013-06-08 16:09 ` [PATCH] " Carsten Emde
2013-06-09 11:45 ` [PATCH v2] drm/i915: Do not flush caches on RT, print a warning instead Carsten Emde
2013-06-10 6:30 ` Christoph Mathys
2013-06-10 22:22 ` Paul Gortmaker
2013-06-11 11:42 ` Sebastian Andrzej Siewior [this message]
2013-06-14 16:04 ` Sebastian Andrzej Siewior
2013-06-14 20:32 ` Daniel Vetter
2013-07-04 7:09 ` [ANNOUNCE] 3.6.11.4-rt36 - Kernel Bug Lampersperger Andreas
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=51B70D1D.2000709@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=eraserix@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.