From: Ramalingam C <ramalingam.c@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: align dumb buffer stride to page_sz of the region
Date: Wed, 5 Feb 2020 19:17:09 +0530 [thread overview]
Message-ID: <20200205134709.GA11696@intel.com> (raw)
In-Reply-To: <158090431136.3271.388032583428389433@skylake-alporthouse-com>
On 2020-02-05 at 12:05:11 +0000, Chris Wilson wrote:
> Quoting Ramalingam C (2020-02-05 12:02:50)
> > On 2020-02-05 at 11:43:35 +0000, Chris Wilson wrote:
> > > Quoting Ramalingam C (2020-02-05 11:40:19)
> > > > If stride of the dumb buffer requested is greater than the primary
> > > > plane's max stride, then we align the stride to the page size. But the
> > > > page size was hard coded for 4096.
> > > >
> > > > With the lmem addition, lets align the stride to the page size of the
> > > > memory region that will be used for dumb buffer.
> > > >
> > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> > > > cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > > ---
> > > > drivers/gpu/drm/i915/i915_gem.c | 20 +++++++++-----------
> > > > 1 file changed, 9 insertions(+), 11 deletions(-)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> > > > index a712e60b016a..0f01396ca24e 100644
> > > > --- a/drivers/gpu/drm/i915/i915_gem.c
> > > > +++ b/drivers/gpu/drm/i915/i915_gem.c
> > > > @@ -239,8 +239,9 @@ i915_gem_dumb_create(struct drm_file *file,
> > > > struct drm_device *dev,
> > > > struct drm_mode_create_dumb *args)
> > > > {
> > > > - enum intel_memory_type mem_type;
> > > > int cpp = DIV_ROUND_UP(args->bpp, 8);
> > > > + enum intel_memory_type mem_type;
> > > > + struct intel_memory_region *mr;
> > > > u32 format;
> > > >
> > > > switch (cpp) {
> > > > @@ -260,24 +261,21 @@ i915_gem_dumb_create(struct drm_file *file,
> > > > /* have to work out size/pitch and return them */
> > > > args->pitch = ALIGN(args->width * cpp, 64);
> > > >
> > > > + mem_type = INTEL_MEMORY_SYSTEM;
> > > > + if (HAS_LMEM(to_i915(dev)))
> > > > + mem_type = INTEL_MEMORY_LOCAL;
> > > > + mr = intel_memory_region_by_type(to_i915(dev), mem_type);
> > > > +
> > > > /* align stride to page size so that we can remap */
> > > > if (args->pitch > intel_plane_fb_max_stride(to_i915(dev), format,
> > > > DRM_FORMAT_MOD_LINEAR))
> > > > - args->pitch = ALIGN(args->pitch, 4096);
> > > > + args->pitch = ALIGN(args->pitch, mr->min_page_size);
> > >
> > > That should be ggtt-page size, different semantics, right?
> > Chris,
> >
> > Sicne the purpose(remapping stride) is not clear, couldn't understand
> > which page size this is. I assumed this is of hw page size.
> >
> > Btw, there is no issues found with 4096 on lmem too. May be this is
> > unwanted change, unless they meant hw page size here and luckily we are
> > not hitting the issue. I am not sure though.
>
> It for doing tricks with I915_GGTT_VIEW_REMAPPED (intel_remap_pages) so
> that a large framebuffer can be cut into CRTC-sized chunks and not go
> over the HW limits.
Sure. I will discard this change. Thanks for explaining that to me.
-Ram.
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-05 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 11:40 [Intel-gfx] [PATCH] drm/i915: align dumb buffer stride to page_sz of the region Ramalingam C
2020-02-05 11:43 ` Chris Wilson
2020-02-05 12:02 ` Ramalingam C
2020-02-05 12:05 ` Chris Wilson
2020-02-05 13:47 ` Ramalingam C [this message]
2020-02-05 16:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-08 2:02 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=20200205134709.GA11696@intel.com \
--to=ramalingam.c@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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.