Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/5] drm/i915: audit bo->resource usage v3
Date: Wed, 25 Jan 2023 11:07:31 +0100	[thread overview]
Message-ID: <418a6bca-7a61-86d8-7f6a-229d1e12c0fd@gmail.com> (raw)
In-Reply-To: <CAM0jSHNKkAS1+dYJdHk23+Uyoz02G1VPFLpKLxX2HqRe7L2HCA@mail.gmail.com>



Am 25.01.23 um 10:56 schrieb Matthew Auld:
> On Tue, 24 Jan 2023 at 17:15, Matthew Auld
> <matthew.william.auld@gmail.com> wrote:
>> On Tue, 24 Jan 2023 at 13:48, Matthew Auld
>> <matthew.william.auld@gmail.com> wrote:
>>> On Tue, 24 Jan 2023 at 12:57, Christian König
>>> <ckoenig.leichtzumerken@gmail.com> wrote:
>>>> From: Christian König <ckoenig.leichtzumerken@gmail.com>
>>>>
>>>> Make sure we can at least move and alloc TT objects without backing store.
>>>>
>>>> v2: clear the tt object even when no resource is allocated.
>>>> v3: add Matthews changes for i915 as well.
>>>>
>>>> Signed-off-by: Christian König <christian.koenig@amd.com>
>>> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>> Ofc that assumes intel-gfx CI is now happy with the series.
> There are still some nasty failures it seems (in the extended test
> list). But it looks like the series is already merged. Can we quickly
> revert and try again?

Ah, crap. I thought everything would be fine after the CI gave it's go.

Which patch is causing the fallout?

Christian.

  reply	other threads:[~2023-01-25 10:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 12:57 [Intel-gfx] [PATCH 1/5] drm/i915: audit bo->resource usage v3 Christian König
2023-01-24 12:57 ` [Intel-gfx] [PATCH 2/5] drm/ttm: stop allocating dummy resources during BO creation Christian König
2023-01-24 13:49   ` Matthew Auld
2023-01-24 12:57 ` [Intel-gfx] [PATCH 3/5] drm/ttm: stop allocating a dummy resource for pipelined gutting Christian König
2023-01-24 13:50   ` Matthew Auld
2023-01-24 12:57 ` [Intel-gfx] [PATCH 4/5] drm/ttm: prevent moving of pinned BOs Christian König
2023-01-24 14:01   ` Matthew Auld
2023-01-24 12:57 ` [Intel-gfx] [PATCH 5/5] drm/ttm: replace busy placement with flags v2 Christian König
2023-01-24 17:11   ` Matthew Auld
2023-01-25 11:31   ` kernel test robot
2023-01-24 13:48 ` [Intel-gfx] [PATCH 1/5] drm/i915: audit bo->resource usage v3 Matthew Auld
2023-01-24 17:15   ` Matthew Auld
2023-01-25  9:56     ` Matthew Auld
2023-01-25 10:07       ` Christian König [this message]
2023-01-25 10:21         ` Matthew Auld
2023-01-25 11:35           ` Christian König
2023-01-25 12:53             ` Matthew Auld
2023-01-25 14:20               ` Christian König
2023-01-25 15:46                 ` Matthew Auld
2023-01-24 19:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] " Patchwork
2023-01-24 19:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-01-24 22:48 ` [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=418a6bca-7a61-86d8-7f6a-229d1e12c0fd@gmail.com \
    --to=ckoenig.leichtzumerken@gmail.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