From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: ankitprasad.r.sharma@intel.com, intel-gfx@lists.freedesktop.org
Cc: akash.goel@intel.com, shashidhar.hiremath@intel.com
Subject: Re: [PATCH 2/4] drm/i915: Support for creating Stolen memory backed objects
Date: Wed, 01 Jul 2015 17:20:27 +0100 [thread overview]
Message-ID: <5594134B.5000702@linux.intel.com> (raw)
In-Reply-To: <1435742747-3782-3-git-send-email-ankitprasad.r.sharma@intel.com>
On 07/01/2015 10:25 AM, ankitprasad.r.sharma@intel.com wrote:
> From: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
>
> Extend the drm_i915_gem_create structure to add support for
> creating Stolen memory backed objects. Added a new flag through
> which user can specify the preference to allocate the object from
> stolen memory, which if set, an attempt will be made to allocate
> the object from stolen memory subject to the availability of
> free space in the stolen region.
>
> v2: Rebased to the latest drm-intel-nightly (Ankit)
>
> testcase: igt/gem_stolen
>
> Signed-off-by: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
> ---
> drivers/gpu/drm/i915/i915_dma.c | 3 +++
> drivers/gpu/drm/i915/i915_gem.c | 31 +++++++++++++++++++++++++++----
> include/uapi/drm/i915_drm.h | 15 +++++++++++++++
> 3 files changed, 45 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
> index c5349fa..6045749 100644
> --- a/drivers/gpu/drm/i915/i915_dma.c
> +++ b/drivers/gpu/drm/i915/i915_dma.c
> @@ -167,6 +167,9 @@ static int i915_getparam(struct drm_device *dev, void *data,
> value = i915.enable_hangcheck &&
> intel_has_gpu_reset(dev);
> break;
> + case I915_PARAM_CREATE_VERSION:
> + value = 1;
> + break;
> default:
> DRM_DEBUG("Unknown parameter %d\n", param->param);
> return -EINVAL;
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index a2a4a27..4acf331 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -391,7 +391,8 @@ static int
> i915_gem_create(struct drm_file *file,
> struct drm_device *dev,
> uint64_t size,
> - uint32_t *handle_p)
> + uint32_t *handle_p,
> + uint32_t flags)
> {
> struct drm_i915_gem_object *obj;
> int ret;
> @@ -401,8 +402,29 @@ i915_gem_create(struct drm_file *file,
> if (size == 0)
> return -EINVAL;
>
> + if (flags & ~(I915_CREATE_PLACEMENT_STOLEN))
> + return -EINVAL;
> +
> /* Allocate the new object */
> - obj = i915_gem_alloc_object(dev, size);
> + if (flags & I915_CREATE_PLACEMENT_STOLEN) {
> + mutex_lock(&dev->struct_mutex);
> + obj = i915_gem_object_create_stolen(dev, size);
One more thing here, size is u64 in this function but
i915_gem_object_create_stolen takes u32. Is compiler not noticing this?
(And i915_gem_alloc_object is size_t for a complete win!) :D
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-01 16:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 9:25 [PATCH v4 0/4] Support for creating/using Stolen memory backed objects ankitprasad.r.sharma
2015-07-01 9:25 ` [PATCH 1/4] drm/i915: Clearing buffer objects via blitter engine ankitprasad.r.sharma
2015-07-01 14:54 ` Tvrtko Ursulin
2015-07-01 16:30 ` Chris Wilson
2015-07-02 9:30 ` Tvrtko Ursulin
2015-07-02 9:50 ` Chris Wilson
2015-07-07 7:42 ` Ankitprasad Sharma
2015-07-07 8:46 ` Chris Wilson
2015-07-07 8:52 ` Ankitprasad Sharma
2015-07-01 9:25 ` [PATCH 2/4] drm/i915: Support for creating Stolen memory backed objects ankitprasad.r.sharma
2015-07-01 15:06 ` Tvrtko Ursulin
2015-07-01 16:19 ` Chris Wilson
2015-07-02 9:37 ` Tvrtko Ursulin
2015-07-02 9:43 ` Chris Wilson
2015-07-01 16:20 ` Tvrtko Ursulin [this message]
2015-07-01 9:25 ` [PATCH 3/4] drm/i915: Add support for stealing purgable stolen pages ankitprasad.r.sharma
2015-07-01 16:17 ` Tvrtko Ursulin
2015-07-01 9:25 ` [PATCH 4/4] drm/i915: Support for pread/pwrite from/to non shmem backed objects ankitprasad.r.sharma
2015-07-01 9:54 ` Chris Wilson
2015-07-02 10:42 ` Tvrtko Ursulin
2015-07-02 11:00 ` Chris Wilson
2015-07-02 11:27 ` Tvrtko Ursulin
2015-07-02 11:58 ` Chris Wilson
2015-07-03 5:07 ` shuang.he
-- strict thread matches above, loose matches on Subject: below --
2015-09-15 8:33 [PATCH v6 0/4] Support for creating/using Stolen memory " ankitprasad.r.sharma
2015-09-15 8:33 ` [PATCH 2/4] drm/i915: Support for creating " ankitprasad.r.sharma
2015-09-15 9:49 ` Chris Wilson
2015-09-20 14:07 ` Ankitprasad Sharma
2015-09-23 9:26 ` Daniel Vetter
2015-09-15 14:11 ` Tvrtko Ursulin
2015-07-22 13:51 [PATCH v5 0/4] Support for creating/using " ankitprasad.r.sharma
2015-07-22 13:51 ` [PATCH 2/4] drm/i915: Support for creating " ankitprasad.r.sharma
2015-07-22 15:14 ` Tvrtko Ursulin
2015-07-22 15:27 ` Chris Wilson
2015-05-06 10:15 [PATCH v3 0/4] Support for creating/using " ankitprasad.r.sharma
2015-05-06 10:16 ` [PATCH 2/4] drm/i915: Support for creating " ankitprasad.r.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=5594134B.5000702@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=akash.goel@intel.com \
--cc=ankitprasad.r.sharma@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 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.