From: Ramalingam C <ramalingam.c@intel.com>
To: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"Hellstrom Thomas" <thomas.hellstrom@intel.com>,
"Matthew Auld" <matthew.auld@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v7 3/9] drm/i915/gt: Optimize the migration and clear loop
Date: Tue, 5 Apr 2022 15:40:41 +0530 [thread overview]
Message-ID: <20220405101040.GA17740@intel.com> (raw)
In-Reply-To: <YkMIXjJoMobhv21A@bvivekan-mobl.gar.corp.intel.com>
On 2022-03-29 at 18:53:42 +0530, Balasubramani Vivekanandan wrote:
> On 29.03.2022 00:37, Ramalingam C wrote:
> > Move the static calculations out of the loops for copy and clear.
> >
> > Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
> > Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/gt/intel_migrate.c | 44 ++++++++++++-------------
> > 1 file changed, 21 insertions(+), 23 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c b/drivers/gpu/drm/i915/gt/intel_migrate.c
> > index 17dd372a47d1..ec9a9e7cb388 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_migrate.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_migrate.c
> > @@ -526,6 +526,7 @@ intel_context_migrate_copy(struct intel_context *ce,
> > struct i915_request **out)
> > {
> > struct sgt_dma it_src = sg_sgt(src), it_dst = sg_sgt(dst);
> > + u32 src_offset, dst_offset;
> > struct i915_request *rq;
> > int err;
> >
> > @@ -534,8 +535,20 @@ intel_context_migrate_copy(struct intel_context *ce,
> >
> > GEM_BUG_ON(ce->ring->size < SZ_64K);
> >
> > + src_offset = 0;
> > + dst_offset = CHUNK_SZ;
> > + if (HAS_64K_PAGES(ce->engine->i915)) {
> > + GEM_BUG_ON(!src_is_lmem && !dst_is_lmem);
> > +
> > + src_offset = 0;
> > + dst_offset = 0;
> > + if (src_is_lmem)
> > + src_offset = CHUNK_SZ;
> > + if (dst_is_lmem)
> > + dst_offset = 2 * CHUNK_SZ;
> > + }
> > +
> > do {
> > - u32 src_offset, dst_offset;
> > int len;
> >
> > rq = i915_request_create(ce);
> > @@ -563,19 +576,6 @@ intel_context_migrate_copy(struct intel_context *ce,
> > if (err)
> > goto out_rq;
> >
> > - src_offset = 0;
> > - dst_offset = CHUNK_SZ;
> > - if (HAS_64K_PAGES(ce->engine->i915)) {
> > - GEM_BUG_ON(!src_is_lmem && !dst_is_lmem);
> > -
> > - src_offset = 0;
> > - dst_offset = 0;
> > - if (src_is_lmem)
> > - src_offset = CHUNK_SZ;
> > - if (dst_is_lmem)
> > - dst_offset = 2 * CHUNK_SZ;
> > - }
> > -
> > len = emit_pte(rq, &it_src, src_cache_level, src_is_lmem,
> > src_offset, CHUNK_SZ);
> > if (len <= 0) {
> > @@ -585,12 +585,10 @@ intel_context_migrate_copy(struct intel_context *ce,
> >
> > err = emit_pte(rq, &it_dst, dst_cache_level, dst_is_lmem,
> > dst_offset, len);
> > - if (err < 0)
> > - goto out_rq;
> > - if (err < len) {
> > + if (err < len)
> > err = -EINVAL;
> > + if (err < 0)
> > goto out_rq;
> > - }
> With this change, for the case 0 < err < len, now the code does not
> reach `goto out_rq`.
With this change, flow will land into out_rq for all err < len.
But just now i am noticing we are overwriding all error code with
-EINVAL. I will fix that.
Ram.
> Is it the expected behavior? If yes, can you please add some details
> regarding this change in the commit description.
>
> Regards,
> Bala
> >
> > err = rq->engine->emit_flush(rq, EMIT_INVALIDATE);
> > if (err)
> > @@ -691,6 +689,7 @@ intel_context_migrate_clear(struct intel_context *ce,
> > {
> > struct sgt_dma it = sg_sgt(sg);
> > struct i915_request *rq;
> > + u32 offset;
> > int err;
> >
> > GEM_BUG_ON(ce->vm != ce->engine->gt->migrate.context->vm);
> > @@ -698,8 +697,11 @@ intel_context_migrate_clear(struct intel_context *ce,
> >
> > GEM_BUG_ON(ce->ring->size < SZ_64K);
> >
> > + offset = 0;
> > + if (HAS_64K_PAGES(ce->engine->i915) && is_lmem)
> > + offset = CHUNK_SZ;
> > +
> > do {
> > - u32 offset;
> > int len;
> >
> > rq = i915_request_create(ce);
> > @@ -727,10 +729,6 @@ intel_context_migrate_clear(struct intel_context *ce,
> > if (err)
> > goto out_rq;
> >
> > - offset = 0;
> > - if (HAS_64K_PAGES(ce->engine->i915) && is_lmem)
> > - offset = CHUNK_SZ;
> > -
> > len = emit_pte(rq, &it, cache_level, is_lmem, offset, CHUNK_SZ);
> > if (len <= 0) {
> > err = len;
> > --
> > 2.20.1
> >
next prev parent reply other threads:[~2022-04-05 10:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 19:07 [Intel-gfx] [PATCH v7 0/9] drm/i915/ttm: Evict and restore of compressed object Ramalingam C
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 1/9] drm/i915/gt: use engine instance directly for offset Ramalingam C
2022-03-29 6:27 ` Hellstrom, Thomas
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 2/9] drm/i915/gt: Use XY_FAST_COLOR_BLT to clear obj on graphics ver 12+ Ramalingam C
2022-03-29 6:25 ` Thomas Hellström
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 3/9] drm/i915/gt: Optimize the migration and clear loop Ramalingam C
2022-03-29 13:23 ` Balasubramani Vivekanandan
2022-04-05 10:10 ` Ramalingam C [this message]
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 4/9] drm/i915/gt: Clear compress metadata for Flat-ccs objects Ramalingam C
2022-03-29 6:52 ` Thomas Hellström
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 5/9] drm/i915/selftest_migrate: Consider the possible roundup of size Ramalingam C
2022-03-29 6:53 ` Thomas Hellström (Intel)
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 6/9] drm/i915/selftest_migrate: Check CCS meta data clear Ramalingam C
2022-03-29 6:56 ` Thomas Hellström
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 7/9] drm/ttm: Add a parameter to add extra pages into ttm_tt Ramalingam C
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 8/9] drm/i915/gem: Add extra pages in ttm_tt for ccs data Ramalingam C
2022-03-28 19:07 ` [Intel-gfx] [PATCH v7 9/9] drm/i915/migrate: Evict and restore the flatccs capable lmem obj Ramalingam C
2022-03-29 8:13 ` Thomas Hellström
2022-03-29 0:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/ttm: Evict and restore of compressed object (rev5) Patchwork
2022-03-29 0:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-29 0:45 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-04-01 12:37 [Intel-gfx] [PATCH v7 0/9] drm/i915/ttm: Evict and restore of compressed object Ramalingam C
2022-04-01 12:37 ` [Intel-gfx] [PATCH v7 3/9] drm/i915/gt: Optimize the migration and clear loop Ramalingam C
2022-04-05 9:43 ` Balasubramani Vivekanandan
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=20220405101040.GA17740@intel.com \
--to=ramalingam.c@intel.com \
--cc=balasubramani.vivekanandan@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@intel.com \
--cc=thomas.hellstrom@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox