From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Carsten Emde <C.Emde@osadl.org>,
Steven Rostedt <rostedt@goodmis.org>,
Christoph Mathys <eraserix@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
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: Fri, 14 Jun 2013 18:04:40 +0200 [thread overview]
Message-ID: <51BB3F18.6030709@linutronix.de> (raw)
In-Reply-To: <51B46AC0.7050502@osadl.org>
On 06/09/2013 01:45 PM, Carsten Emde wrote:
> Invalidating and flushing all caches may introduce long latencies of up
> to several milliseconds. Do not execute it in PREEMPT_RT_FULL kernels,
> warn once instead and propose to pin all GPU renderering tasks to a
> single CPU, if possible.
>
> Original commit:
> 25ff1195f8a0b3724541ae7bbe331b4296de9c06 upstream.
>
> Original log:
> In order to fully serialize access to the fenced region and the update
> to the fence register we need to take extreme measures on SNB+, and
> manually flush writes to memory prior to writing the fence register in
> conjunction with the memory barriers placed around the register write.
>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Carsten Emde <C.Emde@osadl.org>
Oh boy.
Chris, I have a few questions:
- is the wbinvd() required even on the local CPU or just the remote?
According to bugzilla non-smp works fine. If so, you open code
wbinvd_on_all_cpus()
- is it possible to replace the wbinvd() with clflush() ?
- is the problem going away if every process doing graphics is pinned
to single CPU and the wbindv() call is avoided?
Sebastian
next prev parent reply other threads:[~2013-06-14 16:04 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
2013-06-14 16:04 ` Sebastian Andrzej Siewior [this message]
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=51BB3F18.6030709@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=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.