dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Ben Widawsky <ben@bwidawsk.net>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 5/5] drm/vgem: properly implement mmap
Date: Thu, 9 Feb 2012 11:20:03 +0100	[thread overview]
Message-ID: <20120209102003.GC4450@phenom.ffwll.local> (raw)
In-Reply-To: <e0d58a$36t6ug@orsmga002.jf.intel.com>

On Wed, Feb 08, 2012 at 11:36:22PM +0000, Chris Wilson wrote:
> On Thu,  9 Feb 2012 00:19:31 +0100, Ben Widawsky <ben@bwidawsk.net> wrote:
> > Mostly copied from i915 gtt mmaps, this will properly fault in pages as
> > the user tries to use them. The only thing of note are that no
> > prefaulting occurs, so perhaps some kind of madvise will happen later if
> > needed.
> 
> What's the goal here? Why not copy the simpler (from the driver
> perspective) CPU mmaps? I presume that this will be required for dmabuf
> in some form?

Yeah, for proper instead of hacked-up dma_buf mmap support I expect that
the expoerter needs to provide some sort of vm_insert_pfn_from_dma_buf
function. We need this so that non-coherent dma_buf objects can fake
coherency and also to allow (eventually) eviction. For that the exporter
needs to be able to handle page-faults, so I've figured we might want to
hack something together.

I know it's not a beauty, because drm isn't a fs yet ;-)
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  parent reply	other threads:[~2012-02-09 10:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 23:19 [RFCv2 PATCH 0/5] virtual GEM provider Ben Widawsky
2012-02-08 23:19 ` [PATCH 1/5] drm/vgem: " Ben Widawsky
2012-02-08 23:28   ` Chris Wilson
2012-02-16 13:52   ` Jakob Bornecrantz
2012-02-20 17:10     ` Ben Widawsky
2012-02-21 15:03       ` Adam Jackson
2012-02-21 15:34         ` Dave Airlie
2012-02-21 16:08           ` Adam Jackson
2012-02-21 17:41             ` Ben Widawsky
2012-02-08 23:19 ` [PATCH 2/5] drm/vgem: fops should be separate and constified Ben Widawsky
2012-02-08 23:19 ` [PATCH 3/5] drm/vgem: Add a drm_vgem_gem_object Ben Widawsky
2012-02-08 23:19 ` [PATCH 4/5] drm/vgem: getparam ioctl Ben Widawsky
2012-02-15 21:22   ` Adam Jackson
2012-02-16  7:23     ` Dave Airlie
2012-02-20 17:12       ` Ben Widawsky
2012-02-08 23:19 ` [PATCH 5/5] drm/vgem: properly implement mmap Ben Widawsky
2012-02-08 23:36   ` Chris Wilson
2012-02-09  9:18     ` Ben Widawsky
2012-02-09 10:20     ` Daniel Vetter [this message]
2012-02-14  2:18   ` Eric Anholt
2012-02-14  7:49     ` Dave Airlie
2012-02-14  0:14 ` [RFCv2 PATCH 0/5] virtual GEM provider Adam Jackson

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=20120209102003.GC4450@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox