All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
Cc: intel-gfx@lists.freedesktop.org, akash.goel@intel.com,
	shashidhar.hiremath@intel.com
Subject: Re: [PATCH 2/6] drm/i915: Support for creating Stolen memory backed objects
Date: Fri, 11 Dec 2015 12:19:45 +0000	[thread overview]
Message-ID: <566ABF61.70703@linux.intel.com> (raw)
In-Reply-To: <1449832964.12247.151.camel@ankitprasad-desktop>


On 11/12/15 11:22, Ankitprasad Sharma wrote:
> On Wed, 2015-12-09 at 14:06 +0000, Tvrtko Ursulin wrote:
>> Hi,
>>
>> On 09/12/15 12:46, 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)
>>>
>>> v3: Changed versioning of GEM_CREATE param, added new comments (Tvrtko)
>>>
>>> v4: Changed size from 32b to 64b to prevent userspace overflow (Tvrtko)
>>> Corrected function arguments ordering (Chris)
>>>
>>> v5: Corrected function name (Chris)
>>>
>>> Testcase: igt/gem_stolen
>>>
>>> Signed-off-by: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
>>> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> ---
>>>    drivers/gpu/drm/i915/i915_dma.c        |  3 +++
>>>    drivers/gpu/drm/i915/i915_drv.h        |  2 +-
>>>    drivers/gpu/drm/i915/i915_gem.c        | 30 +++++++++++++++++++++++++++---
>>>    drivers/gpu/drm/i915/i915_gem_stolen.c |  4 ++--
>>>    include/uapi/drm/i915_drm.h            | 16 ++++++++++++++++
>>>    5 files changed, 49 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_dma.c b/drivers/gpu/drm/i915/i915_dma.c
>>> index ffcb9c6..6927c7e 100644
>>> --- a/drivers/gpu/drm/i915/i915_dma.c
>>> +++ b/drivers/gpu/drm/i915/i915_dma.c
>>> @@ -170,6 +170,9 @@ static int i915_getparam(struct drm_device *dev, void *data,
>>>    	case I915_PARAM_HAS_RESOURCE_STREAMER:
>>>    		value = HAS_RESOURCE_STREAMER(dev);
>>>    		break;
>>> +	case I915_PARAM_CREATE_VERSION:
>>> +		value = 2;
>>> +		break;
>>>    	default:
>>>    		DRM_DEBUG("Unknown parameter %d\n", param->param);
>>>    		return -EINVAL;
>>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>>> index 8e554d3..d45274e 100644
>>> --- a/drivers/gpu/drm/i915/i915_drv.h
>>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>>> @@ -3213,7 +3213,7 @@ void i915_gem_stolen_remove_node(struct drm_i915_private *dev_priv,
>>>    int i915_gem_init_stolen(struct drm_device *dev);
>>>    void i915_gem_cleanup_stolen(struct drm_device *dev);
>>>    struct drm_i915_gem_object *
>>> -i915_gem_object_create_stolen(struct drm_device *dev, u32 size);
>>> +i915_gem_object_create_stolen(struct drm_device *dev, u64 size);
>>>    struct drm_i915_gem_object *
>>>    i915_gem_object_create_stolen_for_preallocated(struct drm_device *dev,
>>>    					       u32 stolen_offset,
>>> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
>>> index d57e850..296e63f 100644
>>> --- a/drivers/gpu/drm/i915/i915_gem.c
>>> +++ b/drivers/gpu/drm/i915/i915_gem.c
>>> @@ -375,6 +375,7 @@ static int
>>>    i915_gem_create(struct drm_file *file,
>>>    		struct drm_device *dev,
>>>    		uint64_t size,
>>> +		uint32_t flags,
>>>    		uint32_t *handle_p)
>>>    {
>>>    	struct drm_i915_gem_object *obj;
>>> @@ -385,8 +386,31 @@ i915_gem_create(struct drm_file *file,
>>>    	if (size == 0)
>>>    		return -EINVAL;
>>>
>>> +	if (flags & __I915_CREATE_UNKNOWN_FLAGS)
>>> +		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);
>>> +		if (!obj) {
>>> +			mutex_unlock(&dev->struct_mutex);
>>> +			return -ENOMEM;
>>> +		}
>>> +
>>> +		/* Always clear fresh buffers before handing to userspace */
>>> +		ret = i915_gem_object_clear(obj);
>>> +		if (ret) {
>>> +			drm_gem_object_unreference(&obj->base);
>>> +			mutex_unlock(&dev->struct_mutex);
>>> +			return ret;
>>> +		}
>>> +
>>> +		mutex_unlock(&dev->struct_mutex);
>>> +	} else {
>>> +		obj = i915_gem_alloc_object(dev, size);
>>> +	}
>>> +
>>>    	if (obj == NULL)
>>>    		return -ENOMEM;
>>>
>>> @@ -409,7 +433,7 @@ i915_gem_dumb_create(struct drm_file *file,
>>>    	args->pitch = ALIGN(args->width * DIV_ROUND_UP(args->bpp, 8), 64);
>>>    	args->size = args->pitch * args->height;
>>>    	return i915_gem_create(file, dev,
>>> -			       args->size, &args->handle);
>>> +			       args->size, 0, &args->handle);
>>>    }
>>>
>>>    /**
>>> @@ -422,7 +446,7 @@ i915_gem_create_ioctl(struct drm_device *dev, void *data,
>>>    	struct drm_i915_gem_create *args = data;
>>>
>>>    	return i915_gem_create(file, dev,
>>> -			       args->size, &args->handle);
>>> +			       args->size, args->flags, &args->handle);
>>>    }
>>>
>>>    static inline int
>>> diff --git a/drivers/gpu/drm/i915/i915_gem_stolen.c b/drivers/gpu/drm/i915/i915_gem_stolen.c
>>> index 598ed2f..b98a3bf 100644
>>> --- a/drivers/gpu/drm/i915/i915_gem_stolen.c
>>> +++ b/drivers/gpu/drm/i915/i915_gem_stolen.c
>>> @@ -583,7 +583,7 @@ cleanup:
>>>    }
>>>
>>>    struct drm_i915_gem_object *
>>> -i915_gem_object_create_stolen(struct drm_device *dev, u32 size)
>>> +i915_gem_object_create_stolen(struct drm_device *dev, u64 size)
>>>    {
>>>    	struct drm_i915_private *dev_priv = dev->dev_private;
>>>    	struct drm_i915_gem_object *obj;
>>> @@ -593,7 +593,7 @@ i915_gem_object_create_stolen(struct drm_device *dev, u32 size)
>>>    	if (!drm_mm_initialized(&dev_priv->mm.stolen))
>>>    		return NULL;
>>>
>>> -	DRM_DEBUG_KMS("creating stolen object: size=%x\n", size);
>>> +	DRM_DEBUG_KMS("creating stolen object: size=%llx\n", size);
>>>    	if (size == 0)
>>>    		return NULL;
>>>
>>> diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
>>> index 67cebe6..8e7e3a4 100644
>>> --- a/include/uapi/drm/i915_drm.h
>>> +++ b/include/uapi/drm/i915_drm.h
>>> @@ -356,6 +356,7 @@ typedef struct drm_i915_irq_wait {
>>>    #define I915_PARAM_EU_TOTAL		 34
>>>    #define I915_PARAM_HAS_GPU_RESET	 35
>>>    #define I915_PARAM_HAS_RESOURCE_STREAMER 36
>>> +#define I915_PARAM_CREATE_VERSION	 37
>>>
>>>    typedef struct drm_i915_getparam {
>>>    	__s32 param;
>>> @@ -455,6 +456,21 @@ struct drm_i915_gem_create {
>>>    	 */
>>>    	__u32 handle;
>>>    	__u32 pad;
>>> +	/**
>>> +	 * Requested flags (currently used for placement
>>> +	 * (which memory domain))
>>> +	 *
>>> +	 * You can request that the object be created from special memory
>>> +	 * rather than regular system pages using this parameter. Such
>>> +	 * irregular objects may have certain restrictions (such as CPU
>>> +	 * access to a stolen object is verboten).
>>> +	 *
>>> +	 * This can be used in the future for other purposes too
>>> +	 * e.g. specifying tiling/caching/madvise
>>> +	 */
>>> +	__u32 flags;
>>> +#define I915_CREATE_PLACEMENT_STOLEN 	(1<<0) /* Cannot use CPU mmaps */
>>> +#define __I915_CREATE_UNKNOWN_FLAGS	-(I915_CREATE_PLACEMENT_STOLEN << 1)
>>
>> I've asked in another reply, now that userspace can create a stolen
>> object, what happens if it tries to use it for a batch buffer?
>>
>> Can it end up in the relocate_entry_cpu with a batch buffer allocated
>> from stolen, which would then call i915_gem_object_get_page and crash?
> Thanks for pointing it out.
> Yes, this is definitely a possibility, if we allocate batchbuffers from
> the stolen region. I have started working on that, to do
> relocate_entry_stolen() if the object is allocated from stolen.

Or perhaps it would be OK to just fail the execbuf?

Just thinking to simplify things. Is it required (or expected) that 
users will need or want to create batch buffers from stolen?

Regards,

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

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

Thread overview: 46+ 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 [this message]
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
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 2/6] drm/i915: Support for creating " ankitprasad.r.sharma
2015-11-11 11:41   ` Chris Wilson
2015-12-07 13:43   ` Tvrtko Ursulin
2015-12-10  8:40     ` Daniel Vetter
2015-10-08  6:24 [PATCH v8 0/6] Support for creating/using " ankitprasad.r.sharma
2015-10-08  6:24 ` [PATCH 2/6] 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=566ABF61.70703@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.