LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Menchaca <ben.menchaca@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: 83xx: Marking or Allocating Pages as Cache-Inhibited
Date: Thu, 5 Mar 2009 22:32:56 -0600	[thread overview]
Message-ID: <64ac01180903052032i75792fa6x864f91c511b3f228@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]

I am working on a Freescale 8314e design, and the embedded device is
configured as a PCI-e endpoint running a 2.6.27-5 kernel.  For context, we
have written a kernel module which, among other things, uses the RDMA/WDMA
engine in the PCI-e IP block.  On the host side, these DMAs are coherent.
However, on the embedded side, things are quite a bit less rosy; we must
manually flush/invalidate cache lines for WDMA/RDMAs to occur successfully.
After speaking with (several) FAEs at Freescale, we believe there is a
configuration issue that is the cause, but we have yet to have anyone
successfully point to it.

Disabling the data cache altogether resolves the issue entirely, but of
course, also completely tanks performance.  As a temporary workaround, I
would like to simply mark the pages (obtained currently via
dma_alloc_coherent) involved as cache-inhibited.  I have attempted to do
this via some snippets remaining in fec.c (va_to_pte, uncache_pte to set
_PAGE_NO_CACHE, flush_tlb_page, then unmap_pte), but this is almost
certainly braindead; va_to_pte is not a part of the 83xx source, as far as I
can tell; 8xx only.

A quick pointer in the correct direction for marking pages as
cache-inhibited on a 2.6.27-5 kernel would be appreciated, or if my approach
to a workaround is flawed, a pointer to the correct way would be great.

Ben Menchaca

[-- Attachment #2: Type: text/html, Size: 1394 bytes --]

             reply	other threads:[~2009-03-06  4:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  4:32 Ben Menchaca [this message]
2009-03-06  5:22 ` 83xx: Marking or Allocating Pages as Cache-Inhibited Liu Dave-R63238
2009-03-06  5:27   ` Liu Dave-R63238
2009-03-06  5:38     ` Ben Menchaca
2009-03-06  5:40       ` Liu Dave-R63238
2009-03-06  6:10         ` Ben Menchaca
2009-03-06  6:30           ` Liu Dave-R63238
2009-03-06 16:12             ` Ben Menchaca
2009-03-06 16:30               ` Ben Menchaca
2009-03-09  2:30                 ` Liu Dave-R63238
2009-03-09  2:56                 ` Liu Dave-R63238
2009-03-09  3:27                   ` Ben Menchaca
2009-03-07 21:51               ` Benjamin Herrenschmidt
2009-03-08  3:15                 ` Ben Menchaca
2009-03-06  5:49       ` Liu Dave-R63238
2009-03-08 15:19         ` Timur Tabi
2009-03-09  2:33           ` Liu Dave-R63238

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=64ac01180903052032i75792fa6x864f91c511b3f228@mail.gmail.com \
    --to=ben.menchaca@gmail.com \
    --cc=linuxppc-dev@ozlabs.org \
    /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