All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Longerbeam <steve_longerbeam@mentor.com>
To: DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Skip cache sync for GEM CMA objects?
Date: Wed, 8 Jul 2015 14:51:01 -0700	[thread overview]
Message-ID: <559D9B45.1020306@mentor.com> (raw)

Hi all,

GEM CMA uses dma_alloc_writecombine() when allocating the CMA objects.
So IINM the GEM buffers are cache coherent. So is there any reason why
DMA_ATTR_SKIP_CPU_SYNC is not passed to dma_map_sg() when GEM CMA
prepares the buffer for dma on behalf of the dma-buf user? Is this just an
oversight or is there something I have missed?

Thanks,
Steve

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-07-08 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 21:51 Steve Longerbeam [this message]
2015-07-09 17:42 ` [RFC PATCH] drm: use dma_map_sg_attrs for GEM CMA objects Steve Longerbeam
  -- strict thread matches above, loose matches on Subject: below --
2015-07-08 21:51 Skip cache sync for GEM CMA objects? Steve Longerbeam

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=559D9B45.1020306@mentor.com \
    --to=steve_longerbeam@mentor.com \
    --cc=dri-devel@lists.freedesktop.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 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.