From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
intel-xe@lists.freedesktop.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org
Cc: thomas.hellstrom@linux.intel.com, sumit.semwal@linaro.org,
christian.koenig@amd.com
Subject: Re: [PATCH v2 2/2] drm/xe: Invalidate media_gt TLBs in PT code
Date: Fri, 30 Aug 2024 11:09:44 +0100 [thread overview]
Message-ID: <f1ee5ce0-39dc-4c1d-a587-7326df879dee@intel.com> (raw)
In-Reply-To: <20240826170144.2492062-3-matthew.brost@intel.com>
On 26/08/2024 18:01, Matthew Brost wrote:
> Testing on LNL has shown media GT's TLBs need to be invalidated via the
> GuC, update PT code appropriately.
>
> v2:
> - Do dma_fence_get before first call of invalidation_fence_init (Himal)
> - No need to check for valid chain fence (Himal)
> v3:
> - Use dma-fence-array
>
> Fixes: 3330361543fc ("drm/xe/lnl: Add LNL platform definition")
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2024-08-30 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 17:01 [PATCH v2 0/2] Split out dma fence array and invalidate media_gt TLBs in PT code Matthew Brost
2024-08-26 17:01 ` [PATCH v2 1/2] dma-buf: Split out dma fence array create into alloc and arm functions Matthew Brost
2024-08-26 17:57 ` Christian König
2024-08-26 19:23 ` Matthew Brost
2024-08-27 6:37 ` Christian König
2024-08-27 16:10 ` Matthew Brost
2024-08-30 18:42 ` Matthew Brost
2024-08-26 17:01 ` [PATCH v2 2/2] drm/xe: Invalidate media_gt TLBs in PT code Matthew Brost
2024-08-26 17:57 ` Christian König
2024-08-30 10:09 ` Matthew Auld [this message]
2024-08-26 18:03 ` ✓ CI.Patch_applied: success for Split out dma fence array and invalidate media_gt TLBs in PT code (rev2) Patchwork
2024-08-26 18:04 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-26 18:06 ` ✓ CI.KUnit: success " Patchwork
2024-08-26 18:20 ` ✓ CI.Build: " Patchwork
2024-08-26 18:22 ` ✓ CI.Hooks: " Patchwork
2024-08-26 18:23 ` ✗ CI.checksparse: warning " Patchwork
2024-08-26 18:50 ` ✓ CI.BAT: success " Patchwork
2024-08-26 23:58 ` ✗ CI.FULL: 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=f1ee5ce0-39dc-4c1d-a587-7326df879dee@intel.com \
--to=matthew.auld@intel.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-media@vger.kernel.org \
--cc=matthew.brost@intel.com \
--cc=sumit.semwal@linaro.org \
--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