From: sourab.gupta@intel.com Subject: [PATCH 0/3] Increase the utilization of Stolen area on VLV Date: Fri, 7 Mar 2014 15:29:24 +0530 Message-ID: <1394186367-20339-1-git-send-email-sourab.gupta@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id 88C6EFACE4 for ; Fri, 7 Mar 2014 01:59:06 -0800 (PST) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces@lists.freedesktop.org Errors-To: intel-gfx-bounces@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org Cc: Daniel Vetter , Sourab Gupta , Chris Wilson List-Id: intel-gfx@lists.freedesktop.org From: Sourab Gupta These patches are mainly for increasing the utilization of stolen memory area on VLV. Although similar patches were submitted earlier, this time truncation is handled based on Chris and Daniel's input. Chris's patch handles the truncation of purgeable stolen objects. The allocation from stolen area will be done based on user's input. We have exposed a new libdrm flag which user can use while creating an object to convey driver that direct cpu access to buffer is not required. Based on this flag, driver can decide to allocate the backing storage for this object from stolen mem area. If we run out of stolen memory when trying to allocate an object, we can try to reap enough purgeable objects to free up enough contiguous free space for the allocation. Chris Wilson (1): drm/i915: Truncation logic for Stolen mem objects Sourab Gupta (2): drm/i915: Added a new 'I915_CPU_MAP_NOT_NEEDED' flag to gem_create ioctl. drm/i915: Memory node free handling on truncation of stolen obj drivers/gpu/drm/i915/i915_gem.c | 17 +++-- drivers/gpu/drm/i915/i915_gem_stolen.c | 112 ++++++++++++++++++++++++++++++-- include/uapi/drm/i915_drm.h | 3 +- 3 files changed, 119 insertions(+), 13 deletions(-) -- 1.7.9.5