All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
Cc: dri-devel@lists.freedesktop.org,
	Brian King <brking@linux.vnet.ibm.com>,
	Jerome Glisse <jglisse@redhat.com>,
	Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>
Subject: Re: [PATCH] drm/radeon: Disable writeback by default on ppc
Date: Mon, 25 Nov 2013 10:15:47 +1100	[thread overview]
Message-ID: <1385334947.4882.153.camel@pasglop> (raw)
In-Reply-To: <527CEA7D.4060704@linux.vnet.ibm.com>

On Fri, 2013-11-08 at 11:43 -0200, Kleber Sacilotto de Souza wrote:
> On 11/07/2013 08:29 PM, Benjamin Herrenschmidt wrote:
> > On Mon, 2013-06-17 at 18:57 -0400, Alex Deucher wrote:
> >
> >> Weird.  I wonder if there is an issue with cache snoops on PPC.  We
> >> currently use the gart in cached mode (GPU snoops CPU cache) with
> >> cached pages.  I wonder if we need to use uncached pages on PPC.
> >
> > There is no such issue and no known bugs with DMA writes on those
> > PCIe host bridges (and they do get hammered pretty bad here).
> >
> > This needs further investigation by the lab/hw guys to find out what's
> > actually happening on the bus and the host bridge.
> >
> > Thadeu, Kleber: Jerome suggested writing a test case in userspace that
> > continuously writes to a spare scratch register (thus triggering the
> > corresponding writeback DMA) and checks the memory location to compare
> > the writeback value (using a debugfs file for example, or mmap).
> >
> 
> I can look into that.

Any news ?

Ben.

> 
> Thanks,
> 
> Kleber
> 
> > Can you guys do something like that ? Then we need the analyzer on
> > and/or the lab guys to look at the fabric trace & PHB trace.
> >
> > Ben.
> >
> >
> 
> 

  reply	other threads:[~2013-11-24 23:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17 14:06 [PATCH] drm/radeon: Disable writeback by default on ppc Adam Jackson
2013-06-17 15:04 ` Alex Deucher
2013-06-17 16:07   ` Adam Jackson
2013-06-17 22:57     ` Alex Deucher
2013-11-07 22:29       ` Benjamin Herrenschmidt
2013-11-08 13:43         ` Kleber Sacilotto de Souza
2013-11-24 23:15           ` Benjamin Herrenschmidt [this message]
2013-11-26  0:11             ` Kleber Sacilotto de Souza
2013-12-04 22:16               ` Kleber Sacilotto de Souza
2013-12-04 23:56                 ` Alex Deucher
2013-12-05  0:05                   ` Alex Deucher
2013-12-05  1:39                     ` Benjamin Herrenschmidt
2013-12-05  2:29                       ` Michel Dänzer
2013-12-05  4:06                         ` Benjamin Herrenschmidt
2013-12-05 14:42                           ` Alex Deucher
2013-12-06 13:58                             ` Kleber Sacilotto de Souza
2013-12-06 15:59                               ` Alex Deucher
2013-12-10  0:48                                 ` Alex Deucher
2013-12-10  2:20                                   ` Michel Dänzer
2013-12-10 15:04                                     ` Alex Deucher
2013-12-10 15:12                                       ` Alex Deucher
2014-01-02 20:54                                         ` Kleber Sacilotto de Souza
2014-01-02 22:48                                           ` Alex Deucher

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=1385334947.4882.153.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=brking@linux.vnet.ibm.com \
    --cc=cascardo@linux.vnet.ibm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=klebers@linux.vnet.ibm.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.