From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 2/3] drm/xe: Move TLB invalidation reset before HW reset
Date: Thu, 11 Jan 2024 12:24:53 +0100 [thread overview]
Message-ID: <c357339d-e62f-425d-b70e-73b7bc828d0e@intel.com> (raw)
In-Reply-To: <20240109230149.1399302-3-matthew.brost@intel.com>
On 10.01.2024 00:01, Matthew Brost wrote:
> This is a software reset which can be done immediately after stopping
> the UC.
IMO there is too tight relation between TLB invalidation code and CT
internals (TLB code uses internal CT locks) but since this is not new:
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt.c b/drivers/gpu/drm/xe/xe_gt.c
> index 3af2adec1295..c647f41b2751 100644
> --- a/drivers/gpu/drm/xe/xe_gt.c
> +++ b/drivers/gpu/drm/xe/xe_gt.c
> @@ -619,12 +619,12 @@ static int gt_reset(struct xe_gt *gt)
> if (err)
> goto err_out;
>
> + xe_gt_tlb_invalidation_reset(gt);
> +
> err = do_gt_reset(gt);
> if (err)
> goto err_out;
>
> - xe_gt_tlb_invalidation_reset(gt);
> -
> err = do_gt_restart(gt);
> if (err)
> goto err_out;
next prev parent reply other threads:[~2024-01-11 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 23:01 [PATCH v2 0/3] GuC CT tweaks Matthew Brost
2024-01-09 23:01 ` [PATCH v2 1/3] drm/xe/guc: Add more GuC CT states Matthew Brost
2024-01-11 11:01 ` Michal Wajdeczko
2024-01-12 17:50 ` Matthew Brost
2024-01-09 23:01 ` [PATCH v2 2/3] drm/xe: Move TLB invalidation reset before HW reset Matthew Brost
2024-01-11 11:24 ` Michal Wajdeczko [this message]
2024-01-09 23:01 ` [PATCH v2 3/3] drm/xe/guc: Flush G2H handler when turning off CTs Matthew Brost
2024-01-11 12:29 ` Michal Wajdeczko
2024-01-10 1:00 ` ✓ CI.Patch_applied: success for GuC CT tweaks (rev2) Patchwork
2024-01-10 1:00 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-10 1:01 ` ✓ CI.KUnit: success " Patchwork
2024-01-10 1:08 ` ✓ CI.Build: " Patchwork
2024-01-10 1:09 ` ✓ CI.Hooks: " Patchwork
2024-01-10 1:10 ` ✓ CI.checksparse: " Patchwork
2024-01-10 1:46 ` ✓ CI.BAT: " 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=c357339d-e62f-425d-b70e-73b7bc828d0e@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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