Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org, akash.goel@intel.com,
	shashidhar.hiremath@intel.com
Subject: Re: [PATCH 5/6] drm/i915: Support for pread/pwrite from/to non shmem backed objects
Date: Thu, 10 Dec 2015 16:42:56 +0530	[thread overview]
Message-ID: <1449745976.12247.84.camel@ankitprasad-desktop> (raw)
In-Reply-To: <5668838C.6060101@intel.com>

On Wed, 2015-12-09 at 19:39 +0000, Dave Gordon wrote:
> On 09/12/15 16:15, Tvrtko Ursulin wrote:
> >
> > Hi,
> >
> > On 09/12/15 12:46, ankitprasad.r.sharma@intel.com wrote:
> >> From: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
> >>
> >> This patch adds support for extending the pread/pwrite functionality
> >> for objects not backed by shmem. The access will be made through
> >> gtt interface. This will cover objects backed by stolen memory as well
> >> as other non-shmem backed objects.
> >>
> >> v2: Drop locks around slow_user_access, prefault the pages before
> >> access (Chris)
> >>
> >> v3: Rebased to the latest drm-intel-nightly (Ankit)
> >>
> >> v4: Moved page base & offset calculations outside the copy loop,
> >> corrected data types for size and offset variables, corrected if-else
> >> braces format (Tvrtko/kerneldocs)
> >>
> >> v5: Enabled pread/pwrite for all non-shmem backed objects including
> >> without tiling restrictions (Ankit)
> >>
> >> v6: Using pwrite_fast for non-shmem backed objects as well (Chris)
> >>
> >> v7: Updated commit message, Renamed i915_gem_gtt_read to
> >> i915_gem_gtt_copy,
> >> added pwrite slow path for non-shmem backed objects (Chris/Tvrtko)
> >>
> >> v8: Updated v7 commit message, mutex unlock around pwrite slow path for
> >> non-shmem backed objects (Tvrtko)
> >>
> >> Testcase: igt/gem_stolen
> >>
> >> Signed-off-by: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
> >> ---
> >>   drivers/gpu/drm/i915/i915_gem.c | 151
> >> +++++++++++++++++++++++++++++++++-------
> >>   1 file changed, 127 insertions(+), 24 deletions(-)
> >>
> >> diff --git a/drivers/gpu/drm/i915/i915_gem.c
> >> b/drivers/gpu/drm/i915/i915_gem.c
> >> index ed97de6..68ed67a 100644
> >> --- a/drivers/gpu/drm/i915/i915_gem.c
> >> +++ b/drivers/gpu/drm/i915/i915_gem.c
> >> @@ -614,6 +614,99 @@ shmem_pread_slow(struct page *page, int
> >> shmem_page_offset, int page_length,
> >>       return ret ? - EFAULT : 0;
> >>   }
> >>
> >> +static inline uint64_t
> >> +slow_user_access(struct io_mapping *mapping,
> >> +         uint64_t page_base, int page_offset,
> >> +         char __user *user_data,
> >> +         int length, bool pwrite)
> >> +{
> >> +    void __iomem *vaddr_inatomic;
> >> +    void *vaddr;
> >> +    uint64_t unwritten;
> >> +
> >> +    vaddr_inatomic = io_mapping_map_wc(mapping, page_base);
> >> +    /* We can use the cpu mem copy function because this is X86. */
> >> +    vaddr = (void __force *)vaddr_inatomic + page_offset;
> >> +    if (pwrite)
> >> +        unwritten = __copy_from_user(vaddr, user_data, length);
> >> +    else
> >> +        unwritten = __copy_to_user(user_data, vaddr, length);
> >> +
> >> +    io_mapping_unmap(vaddr_inatomic);
> >> +    return unwritten;
> >> +}
> >> +
> >> +static int
> >> +i915_gem_gtt_copy(struct drm_device *dev,
> >> +           struct drm_i915_gem_object *obj, uint64_t size,
> >> +           uint64_t data_offset, uint64_t data_ptr)
> >> +{
> >> +    struct drm_i915_private *dev_priv = dev->dev_private;
> >> +    char __user *user_data;
> >> +    uint64_t remain;
> >> +    uint64_t offset, page_base;
> >> +    int page_offset, page_length, ret = 0;
> >> +
> >> +    ret = i915_gem_obj_ggtt_pin(obj, 0, PIN_MAPPABLE);
> >> +    if (ret)
> >> +        goto out;
> >> +
> >> +    ret = i915_gem_object_set_to_gtt_domain(obj, false);
> >> +    if (ret)
> >> +        goto out_unpin;
> >> +
> >> +    ret = i915_gem_object_put_fence(obj);
> >> +    if (ret)
> >> +        goto out_unpin;
> >> +
> >> +    user_data = to_user_ptr(data_ptr);
> >> +    remain = size;
> >> +    offset = i915_gem_obj_ggtt_offset(obj) + data_offset;
> >> +
> >> +    mutex_unlock(&dev->struct_mutex);
> >> +    if (likely(!i915.prefault_disable))
> >> +        ret = fault_in_multipages_writeable(user_data, remain);
> >> +
> >> +    /*
> >> +     * page_offset = offset within page
> >> +     * page_base = page offset within aperture
> >> +     */
> >> +    page_offset = offset_in_page(offset);
> >> +    page_base = offset & PAGE_MASK;
> >> +
> >> +    while (remain > 0) {
> >> +        /* page_length = bytes to copy for this page */
> >> +        page_length = remain;
> >> +        if ((page_offset + remain) > PAGE_SIZE)
> >> +            page_length = PAGE_SIZE - page_offset;
> >> +
> >> +        /* This is a slow read/write as it tries to read from
> >> +         * and write to user memory which may result into page
> >> +         * faults
> >> +         */
> >> +        ret = slow_user_access(dev_priv->gtt.mappable, page_base,
> >> +                       page_offset, user_data,
> >> +                       page_length, false);
> >> +
> >> +        if (ret) {
> >> +            ret = -EFAULT;
> >> +            break;
> >> +        }
> >> +
> >> +        remain -= page_length;
> >> +        user_data += page_length;
> >> +        page_base += page_length;
> >> +        page_offset = 0;
> >> +    }
> >> +
> >> +    mutex_lock(&dev->struct_mutex);
> >> +
> >> +out_unpin:
> >> +    i915_gem_object_ggtt_unpin(obj);
> >> +out:
> >> +    return ret;
> >> +}
> >> +
> >>   static int
> >>   i915_gem_shmem_pread(struct drm_device *dev,
> >>                struct drm_i915_gem_object *obj,
> >> @@ -737,17 +830,14 @@ i915_gem_pread_ioctl(struct drm_device *dev,
> >> void *data,
> >>           goto out;
> >>       }
> >>
> >> -    /* prime objects have no backing filp to GEM pread/pwrite
> >> -     * pages from.
> >> -     */
> >> -    if (!obj->base.filp) {
> >> -        ret = -EINVAL;
> >> -        goto out;
> >> -    }
> >> -
> >>       trace_i915_gem_object_pread(obj, args->offset, args->size);
> >>
> >> -    ret = i915_gem_shmem_pread(dev, obj, args, file);
> >> +    /* pread for non shmem backed objects */
> >> +    if (!obj->base.filp && obj->tiling_mode == I915_TILING_NONE)
> >> +        ret = i915_gem_gtt_copy(dev, obj, args->size,
> >> +                    args->offset, args->data_ptr);
> >> +    else
> >> +        ret = i915_gem_shmem_pread(dev, obj, args, file);
> >
> > Hm, it will end up calling i915_gem_shmem_pread for non-shmem backed
> > objects if tiling is set. Sounds wrong to me unless I am missing something?
> 
> Which GEM objects have obj->base.filp set? Is it ONLY regular gtt-type 
> objects? What about (phys, stolen, userptr, dmabuf, ...?) Which of these 
> is the alternate path going to work with?
Only shmem backed objects have obj->base.filp set, filp pointing to the
shmem file. For all other non-shmem backed objects (stolen, userptr,
dmabuf) we use the alternate path.

-Ankit

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-10 11:32 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 12:46 [PATCH v10 0/6] Support for creating/using Stolen memory backed objects ankitprasad.r.sharma
2015-12-09 12:46 ` [PATCH 1/6] drm/i915: Clearing buffer objects via CPU/GTT ankitprasad.r.sharma
2015-12-09 13:26   ` Dave Gordon
2015-12-10 10:02     ` Ankitprasad Sharma
2015-12-09 13:30   ` Tvrtko Ursulin
2015-12-09 13:57   ` Tvrtko Ursulin
2015-12-10 10:23     ` Ankitprasad Sharma
2015-12-09 13:57   ` Chris Wilson
2015-12-10 10:27     ` Ankitprasad Sharma
2015-12-09 12:46 ` [PATCH 2/6] drm/i915: Support for creating Stolen memory backed objects ankitprasad.r.sharma
2015-12-09 14:06   ` Tvrtko Ursulin
2015-12-11 11:22     ` Ankitprasad Sharma
2015-12-11 12:19       ` Tvrtko Ursulin
2015-12-11 12:49         ` Dave Gordon
2015-12-11 18:13           ` Daniel Vetter
2015-12-09 12:46 ` [PATCH 3/6] drm/i915: Propagating correct error codes to the userspace ankitprasad.r.sharma
2015-12-09 15:10   ` Tvrtko Ursulin
2015-12-09 12:46 ` [PATCH 4/6] drm/i915: Add support for stealing purgable stolen pages ankitprasad.r.sharma
2015-12-09 15:40   ` Tvrtko Ursulin
2015-12-09 12:46 ` [PATCH 5/6] drm/i915: Support for pread/pwrite from/to non shmem backed objects ankitprasad.r.sharma
2015-12-09 16:15   ` Tvrtko Ursulin
2015-12-09 19:39     ` Dave Gordon
2015-12-10 11:12       ` Ankitprasad Sharma [this message]
2015-12-10 18:18         ` Dave Gordon
2015-12-11  5:22           ` Ankitprasad Sharma
2015-12-11 18:15       ` Daniel Vetter
2015-12-15 16:22         ` Dave Gordon
2015-12-10 10:54     ` Ankitprasad Sharma
2015-12-10 11:00       ` Ankitprasad Sharma
2015-12-09 12:46 ` [PATCH 6/6] drm/i915: Migrate stolen objects before hibernation ankitprasad.r.sharma
2015-12-09 17:25   ` Tvrtko Ursulin
2015-12-09 19:24     ` Ville Syrjälä
2015-12-10 13:17     ` Ankitprasad Sharma
2015-12-09 19:35   ` Dave Gordon
2015-12-10  9:43   ` Tvrtko Ursulin
2015-12-10 13:17     ` Ankitprasad Sharma
2015-12-10 14:15       ` Tvrtko Ursulin
2015-12-10 18:00         ` Dave Gordon
2015-12-11  5:19           ` Ankitprasad Sharma
2015-12-11  5:16         ` Ankitprasad Sharma
2015-12-11 12:33           ` Tvrtko Ursulin
  -- strict thread matches above, loose matches on Subject: below --
2015-11-11 10:36 [PATCH v9 0/6] Support for creating/using Stolen memory backed objects ankitprasad.r.sharma
2015-11-11 10:36 ` [PATCH 5/6] drm/i915: Support for pread/pwrite from/to non shmem " ankitprasad.r.sharma
2015-11-13 17:23   ` Tvrtko Ursulin
2015-11-20  9:30     ` Ankitprasad Sharma
2015-10-08  6:24 [PATCH v8 0/6] Support for creating/using Stolen memory " ankitprasad.r.sharma
2015-10-08  6:24 ` [PATCH 5/6] drm/i915: Support for pread/pwrite from/to non shmem " ankitprasad.r.sharma
2015-10-08 13:56   ` Tvrtko Ursulin
2015-10-28 11:18     ` Ankitprasad Sharma

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=1449745976.12247.84.camel@ankitprasad-desktop \
    --to=ankitprasad.r.sharma@intel.com \
    --cc=akash.goel@intel.com \
    --cc=david.s.gordon@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shashidhar.hiremath@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox