From: "Kristian Høgsberg" <krh@bitplanet.net>
To: "Song, Ruiling" <ruiling.song@intel.com>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [RFC libdrm] intel: Add support for softpin
Date: Sun, 13 Dec 2015 21:33:32 -0800 [thread overview]
Message-ID: <CAOeoa-evaHdkO4gSYHb3DPNH_Q41yRST7_TybeV-uGuc6x3bjw@mail.gmail.com> (raw)
In-Reply-To: <148B1B7A67D1C24B9EF0BE42EA4977064E408D75@shsmsx102.ccr.corp.intel.com>
On Sun, Dec 13, 2015 at 7:17 PM, Song, Ruiling <ruiling.song@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx [mailto:intel-gfx-bounces@lists.freedesktop.org] On Behalf
>> Of Micha? Winiarski
>> Sent: Wednesday, September 9, 2015 10:07 PM
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Ben Widawsky <ben@bwidawsk.net>; dri-devel@lists.freedesktop.org;
>> mesa-dev@lists.freedesktop.org
>> Subject: [Intel-gfx] [RFC libdrm] intel: Add support for softpin
>>
>> Softpin allows userspace to take greater control of GPU virtual address
>> space and eliminates the need of relocations. It can also be used to
>> mirror addresses between GPU and CPU (shared virtual memory).
>> Calls to drm_intel_bo_emit_reloc are still required to build the list of
>> drm_i915_gem_exec_objects at exec time, but no entries in relocs are
>> created. Self-relocs don't make any sense for softpinned objects and can
>> indicate a programming errors, thus are forbidden. Softpinned objects
>> are marked by asterisk in debug dumps.
>>
>> Cc: Thomas Daniel <thomas.daniel@intel.com>
>> Cc: Kristian Høgsberg <krh@bitplanet.net>
>> Cc: Zou Nanhai <nanhai.zou@intel.com>
>> Cc: Michel Thierry <michel.thierry@intel.com>
>> Cc: Ben Widawsky <ben@bwidawsk.net>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
>> ---
>> include/drm/i915_drm.h | 4 +-
>> intel/intel_bufmgr.c | 9 +++
>> intel/intel_bufmgr.h | 1 +
>> intel/intel_bufmgr_gem.c | 176
>> ++++++++++++++++++++++++++++++++++++++++------
>> intel/intel_bufmgr_priv.h | 7 ++
>> 5 files changed, 173 insertions(+), 24 deletions(-)
>
> Will anybody help to push the patch to libdrm? Beignet highly depend on this to implement ocl2.0 svm.
Is the kernel patch upstream?
> Thanks!
> Ruiling
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-14 5:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 14:07 [RFC libdrm] intel: Softpin support Michał Winiarski
2015-09-09 14:07 ` [PATCH 1/2] drm/i915/gtt: Allow adventurous users to select enable_ppgtt=3 Michał Winiarski
2015-09-09 14:07 ` [PATCH v6 2/2] drm/i915: Add soft-pinning API for execbuffer Michał Winiarski
2015-09-09 14:25 ` Chris Wilson
2015-11-04 10:32 ` Yang, Rong R
2015-11-04 10:46 ` Daniel, Thomas
2015-09-09 14:07 ` [RFC libdrm] intel: Add support for softpin Michał Winiarski
2015-12-14 3:17 ` Song, Ruiling
2015-12-14 5:33 ` Kristian Høgsberg [this message]
2015-12-14 7:24 ` Song, Ruiling
2015-12-14 8:28 ` Daniel Vetter
2015-12-14 8:41 ` Song, Ruiling
2015-12-14 9:04 ` [Intel-gfx] " Daniel Vetter
2015-12-14 11:45 ` Emil Velikov
2015-12-14 18:25 ` [Intel-gfx] " Kristian Høgsberg
2015-12-14 18:36 ` Kristian Høgsberg
2015-12-14 20:09 ` Kristian Høgsberg
2015-12-16 3:29 ` [Intel-gfx] " Song, Ruiling
2016-01-25 9:30 ` Chris Wilson
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=CAOeoa-evaHdkO4gSYHb3DPNH_Q41yRST7_TybeV-uGuc6x3bjw@mail.gmail.com \
--to=krh@bitplanet.net \
--cc=ben@bwidawsk.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mesa-dev@lists.freedesktop.org \
--cc=ruiling.song@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;
as well as URLs for NNTP newsgroup(s).