Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: "Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
	"Christian König" <christian.koenig@amd.com>,
	"ML dri-devel" <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v3 09/12] drm/ttm: Document and optimize ttm_bo_pipeline_gutting()
Date: Tue, 25 May 2021 15:37:27 +0200	[thread overview]
Message-ID: <30dc2d316b643a07babbb3a985b6ff2bbf533345.camel@linux.intel.com> (raw)
In-Reply-To: <CAM0jSHO59Kr534HC-i816yRMJ22-XNN-AHwdoSFtK5KBiD99=g@mail.gmail.com>

On Tue, 2021-05-25 at 12:00 +0100, Matthew Auld wrote:
> On Fri, 21 May 2021 at 16:33, Thomas Hellström
> <thomas.hellstrom@linux.intel.com> wrote:
> > 
> > If the bo is idle when calling ttm_bo_pipeline_gutting(), we
> > unnecessarily
> > create a ghost object and push it out to delayed destroy.
> > Fix this by adding a path for idle, and document the function.
> > 
> > Also avoid having the bo end up in a bad state vulnerable to user-
> > space
> > triggered kernel BUGs if the call to ttm_tt_create() fails.
> > 
> > Finally reuse ttm_bo_pipeline_gutting() in ttm_bo_evict().
> > 
> > Cc: Christian König <christian.koenig@amd.com>
> > Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> > ---
> >  drivers/gpu/drm/ttm/ttm_bo.c      | 20 ++++++------
> >  drivers/gpu/drm/ttm/ttm_bo_util.c | 52
> > ++++++++++++++++++++++++++++---
> >  drivers/gpu/drm/ttm/ttm_tt.c      |  5 +++
> >  include/drm/ttm/ttm_tt.h          | 10 ++++++
> >  4 files changed, 73 insertions(+), 14 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/ttm/ttm_bo.c
> > b/drivers/gpu/drm/ttm/ttm_bo.c
> > index ca1b098b6a56..a8fa3375b8aa 100644
> > --- a/drivers/gpu/drm/ttm/ttm_bo.c
> > +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> > @@ -501,10 +501,15 @@ static int ttm_bo_evict(struct
> > ttm_buffer_object *bo,
> >         bdev->funcs->evict_flags(bo, &placement);
> > 
> >         if (!placement.num_placement &&
> > !placement.num_busy_placement) {
> > -               ttm_bo_wait(bo, false, false);
> > +               ret = ttm_bo_wait(bo, true, false);
> > +               if (ret)
> > +                       return ret;
> > 
> > -               ttm_bo_cleanup_memtype_use(bo);
> > -               return ttm_tt_create(bo, false);
> > +               /*
> > +                * Since we've already synced, this frees backing
> > store
> > +                * immediately.
> > +                */
> > +               return ttm_bo_pipeline_gutting(bo);
> >         }
> > 
> >         ret = ttm_bo_mem_space(bo, &placement, &evict_mem, ctx);
> > @@ -974,13 +979,8 @@ int ttm_bo_validate(struct ttm_buffer_object
> > *bo,
> >         /*
> >          * Remove the backing store if no placement is given.
> >          */
> > -       if (!placement->num_placement && !placement-
> > >num_busy_placement) {
> > -               ret = ttm_bo_pipeline_gutting(bo);
> > -               if (ret)
> > -                       return ret;
> > -
> > -               return ttm_tt_create(bo, false);
> > -       }
> > +       if (!placement->num_placement && !placement-
> > >num_busy_placement)
> > +               return ttm_bo_pipeline_gutting(bo);
> > 
> >         /*
> >          * Check whether we need to move buffer.
> > diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
> > b/drivers/gpu/drm/ttm/ttm_bo_util.c
> > index 4a7d3d672f9a..7fa9b3a852eb 100644
> > --- a/drivers/gpu/drm/ttm/ttm_bo_util.c
> > +++ b/drivers/gpu/drm/ttm/ttm_bo_util.c
> > @@ -585,26 +585,70 @@ int ttm_bo_move_accel_cleanup(struct
> > ttm_buffer_object *bo,
> >  }
> >  EXPORT_SYMBOL(ttm_bo_move_accel_cleanup);
> > 
> > +/**
> > + * ttm_bo_pipeline_gutting - purge the contents of a bo
> > + * @bo: The buffer object
> > + *
> > + * Purge the contents of a bo, async if the bo is not idle.
> > + * After a successful call, the bo is left unpopulated in
> > + * system placement. The function may wait uninterruptible
> > + * for idle on OOM.
> > + *
> > + * Return: 0 if successful, negative error code on failure.
> > + */
> >  int ttm_bo_pipeline_gutting(struct ttm_buffer_object *bo)
> >  {
> >         static const struct ttm_place sys_mem = { .mem_type =
> > TTM_PL_SYSTEM };
> >         struct ttm_buffer_object *ghost;
> > +       struct ttm_tt *ttm;
> >         int ret;
> > 
> > -       ret = ttm_buffer_object_transfer(bo, &ghost);
> > +       /* If already idle, no need for ghost object dance. */
> > +       ret = ttm_bo_wait(bo, false, true);
> > +       if (ret != -EBUSY) {
> > +               if (!bo->ttm) {
> > +                       ret = ttm_tt_create(bo, true);
> 
> Why do we now unconditionally add clearing? Below also.

Here we've dropped the bo content and we add but do not populate a page
vector. Now if someone resurrects this object we obtain new pages and
those must be cleared, at least that's the intention.

/Thomas



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

  reply	other threads:[~2021-05-25 13:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 15:32 [Intel-gfx] [PATCH v3 00/12] drm/i915: Move LMEM (VRAM) management over to TTM Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 01/12] drm/i915: Untangle the vma pages_mutex Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 02/12] drm/i915: Don't free shared locks while shared Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 03/12] drm/i915: Fix i915_sg_page_sizes to record dma segments rather than physical pages Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 04/12] drm/i915/ttm Initialize the ttm device and memory managers Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 05/12] drm/i915/ttm: Embed a ttm buffer object in the i915 gem object Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 06/12] drm/ttm: Add a generic TTM memcpy move for page-based iomem Thomas Hellström
2021-05-25  9:18   ` Matthew Auld
2021-05-25  9:32     ` Thomas Hellström
2021-05-25  9:58       ` Matthew Auld
2021-05-25 10:07         ` Thomas Hellström
2021-05-25 15:48           ` Christian König
2021-05-26  7:39             ` Thomas Hellström
2021-05-26 10:45               ` Christian König
2021-05-26 10:57                 ` Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 07/12] drm, drm/i915: Move the memcpy_from_wc functionality to core drm Thomas Hellström
2021-05-24 16:45   ` Matthew Auld
2021-05-24 18:12     ` Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 08/12] drm/ttm: Use drm_memcpy_from_wc_dbm for TTM bo moves Thomas Hellström
2021-05-24 18:16   ` Matthew Auld
2021-05-24 18:47     ` Thomas Hellström
2021-05-26 12:48   ` Christian König
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 09/12] drm/ttm: Document and optimize ttm_bo_pipeline_gutting() Thomas Hellström
2021-05-25 11:00   ` Matthew Auld
2021-05-25 13:37     ` Thomas Hellström [this message]
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 10/12] drm/ttm, drm/amdgpu: Allow the driver some control over swapping Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 11/12] drm/i915/ttm: Introduce a TTM i915 gem object backend Thomas Hellström
2021-05-21 15:32 ` [Intel-gfx] [PATCH v3 12/12] drm/i915/lmem: Verify checks for lmem residency Thomas Hellström
2021-05-21 16:06 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Move LMEM (VRAM) management over to TTM (rev3) Patchwork
2021-05-21 16:09 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-05-21 16:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-05-24  0:10 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=30dc2d316b643a07babbb3a985b6ff2bbf533345.camel@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox