From: Ramalingam C <ramalingam.c@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH v4 2/2] drm/i915: Create dumb buffer from LMEM
Date: Thu, 5 Dec 2019 18:29:29 +0530 [thread overview]
Message-ID: <20191205125849.GF25793@intel.com> (raw)
In-Reply-To: <CAM0jSHMP37vD_sz8HMiA7T2A_J08vD4VmvkC-L7WcyBoxTsCaA@mail.gmail.com>
On 2019-12-05 at 12:12:19 +0000, Matthew Auld wrote:
> On Mon, 2 Dec 2019 at 06:55, Ramalingam C <ramalingam.c@intel.com> wrote:
> >
> > When LMEM is supported, dumb buffer preferred to be created from LMEM.
> >
> > v2:
> > Parameters are reshuffled. [Chris]
> > v3:
> > s/region_id/mem_type
> > v4:
> > use the i915_gem_object_create_region [chris]
> >
> > Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> > cc: Matthew Auld <matthew.auld@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_gem.c | 14 +++++++++++---
> > 1 file changed, 11 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> > index 61395b03443e..34e480c8293e 100644
> > --- a/drivers/gpu/drm/i915/i915_gem.c
> > +++ b/drivers/gpu/drm/i915/i915_gem.c
> > @@ -44,6 +44,7 @@
> > #include "gem/i915_gem_clflush.h"
> > #include "gem/i915_gem_context.h"
> > #include "gem/i915_gem_ioctls.h"
> > +#include "gem/i915_gem_region.h"
> > #include "gem/i915_gem_pm.h"
> > #include "gt/intel_context.h"
> > #include "gt/intel_engine_user.h"
> > @@ -176,6 +177,7 @@ i915_gem_phys_pwrite(struct drm_i915_gem_object *obj,
> > static int
> > i915_gem_create(struct drm_file *file,
> > struct drm_i915_private *dev_priv,
> > + enum intel_memory_type mem_type,
> > u64 *size_p,
> > u32 *handle_p)
> > {
> > @@ -189,7 +191,8 @@ i915_gem_create(struct drm_file *file,
> > return -EINVAL;
> >
> > /* Allocate the new object */
> > - obj = i915_gem_object_create_shmem(dev_priv, size);
> > + obj = i915_gem_object_create_region(intel_memory_region_lookup(dev_priv,
> > + mem_type), size, 0);
>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
> But how should we go about testing this?
>
> We would still need to clear the object(maybe I915_BO_ALLOC_CLEARED?)
> in order to pass the IGTs.
Is this not cleared now? Tested this always clear on system memory not
yet on LMEM. Yes. we need to adjust the dumb buffer IGT to check whether
LMEM is supported? if so what is the max size that we could allocate as dumb
buffer etc.
-Ram.
> We also need to adjust dumb_buffer.c, since
> that uses get_avail_ram_mb() for always_clear, but maybe we need the
> query region uapi for that?
>
> > if (IS_ERR(obj))
> > return PTR_ERR(obj);
> >
> > @@ -209,6 +212,7 @@ i915_gem_dumb_create(struct drm_file *file,
> > struct drm_device *dev,
> > struct drm_mode_create_dumb *args)
> > {
> > + enum intel_memory_type mem_type = INTEL_MEMORY_SYSTEM;
> > int cpp = DIV_ROUND_UP(args->bpp, 8);
> > u32 format;
> >
> > @@ -235,7 +239,11 @@ i915_gem_dumb_create(struct drm_file *file,
> > args->pitch = ALIGN(args->pitch, 4096);
> >
> > args->size = args->pitch * args->height;
> > - return i915_gem_create(file, to_i915(dev),
> > +
> > + if (HAS_LMEM(to_i915(dev)))
> > + mem_type = INTEL_MEMORY_LOCAL;
> > +
> > + return i915_gem_create(file, to_i915(dev), mem_type,
> > &args->size, &args->handle);
> > }
> >
> > @@ -254,7 +262,7 @@ i915_gem_create_ioctl(struct drm_device *dev, void *data,
> >
> > i915_gem_flush_free_objects(dev_priv);
> >
> > - return i915_gem_create(file, dev_priv,
> > + return i915_gem_create(file, dev_priv, INTEL_MEMORY_SYSTEM,
> > &args->size, &args->handle);
> > }
> >
> > --
> > 2.20.1
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-12-05 13:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 6:54 [PATCH v4 1/2] drm/i915: lookup for mem_region of a mem_type Ramalingam C
2019-12-02 6:54 ` [Intel-gfx] " Ramalingam C
2019-12-02 6:54 ` [PATCH v4 2/2] drm/i915: Create dumb buffer from LMEM Ramalingam C
2019-12-02 6:54 ` [Intel-gfx] " Ramalingam C
2019-12-05 12:12 ` Matthew Auld
2019-12-05 12:20 ` Chris Wilson
2019-12-05 13:02 ` Ramalingam C
2019-12-05 13:11 ` Chris Wilson
2019-12-09 11:57 ` Ramalingam C
2019-12-09 12:03 ` Chris Wilson
2019-12-09 12:05 ` Ramalingam C
2019-12-05 12:59 ` Ramalingam C [this message]
2019-12-02 7:01 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v4,1/2] drm/i915: lookup for mem_region of a mem_type Patchwork
2019-12-02 7:01 ` [Intel-gfx] " Patchwork
2019-12-02 7:31 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-12-02 7:31 ` [Intel-gfx] " Patchwork
2019-12-05 11:40 ` [Intel-gfx] [PATCH v4 1/2] " Matthew Auld
-- strict thread matches above, loose matches on Subject: below --
2019-11-06 16:08 Ramalingam C
2019-11-06 16:08 ` [Intel-gfx] [PATCH v4 2/2] drm/i915: Create dumb buffer from LMEM Ramalingam C
2019-11-06 16:08 ` Ramalingam C
2019-11-07 9:45 ` Chris Wilson
2019-11-07 9:45 ` 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=20191205125849.GF25793@intel.com \
--to=ramalingam.c@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=matthew.william.auld@gmail.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.