From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Airlie <airlied@gmail.com>,
Jerome Glisse <j.glisse@gmail.com>,
Oded Gabbay <oded.gabbay@gmail.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: ongoing writecombine on ppc
Date: Fri, 02 Oct 2015 14:45:16 +1000 [thread overview]
Message-ID: <1443761116.2828.64.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAPM=9twpPBLBb6j1ee5_DDv5UqfTzCJh-63CHyDxRU4Xd0ny4g@mail.gmail.com>
On Fri, 2015-10-02 at 14:42 +1000, Dave Airlie wrote:
> I don't think we resolved this the last time we talked about it,
>
> but radeon writecombine maps fail hard on ppc, I think all the fixes
> either did something bad to AGP systems or weren't liked.
>
> My patch attached just fixes radeon, which is where I'm still seeing
> the issue.
Yes, you MUST NOT set the flags of system memory to anything other than
fully cachable on any cache coherent powerpc machine. This should be
bolted into the DRM core imho.
_wc is only suitable for MMIO.
Cheers,
Ben.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-02 5:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 4:42 ongoing writecombine on ppc Dave Airlie
2015-10-02 4:45 ` Benjamin Herrenschmidt [this message]
2015-10-02 4:47 ` Benjamin Herrenschmidt
2015-10-02 4:50 ` Benjamin Herrenschmidt
2015-10-02 4:53 ` Dave Airlie
2015-10-02 4:56 ` Benjamin Herrenschmidt
2016-01-21 15:24 ` Oded Gabbay
2016-01-21 15:39 ` Oded Gabbay
2016-01-21 17:10 ` Alex Deucher
2016-01-22 2:32 ` Michel Dänzer
2016-01-28 14:30 ` Oded Gabbay
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=1443761116.2828.64.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@gmail.com \
--cc=oded.gabbay@gmail.com \
/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.