From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Subject: [PATCH v4 4/5] drm/xe: Remove xe_lrc_create_seqno_fence()
Date: Mon, 27 May 2024 15:59:11 +0200 [thread overview]
Message-ID: <20240527135912.152156-5-thomas.hellstrom@linux.intel.com> (raw)
In-Reply-To: <20240527135912.152156-1-thomas.hellstrom@linux.intel.com>
It's not used anymore.
Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
drivers/gpu/drm/xe/xe_lrc.c | 11 -----------
drivers/gpu/drm/xe/xe_lrc.h | 1 -
2 files changed, 12 deletions(-)
diff --git a/drivers/gpu/drm/xe/xe_lrc.c b/drivers/gpu/drm/xe/xe_lrc.c
index c28796cfaa03..e91967070478 100644
--- a/drivers/gpu/drm/xe/xe_lrc.c
+++ b/drivers/gpu/drm/xe/xe_lrc.c
@@ -1072,17 +1072,6 @@ void xe_lrc_init_seqno_fence(struct xe_lrc *lrc, struct dma_fence *fence)
xe_hw_fence_init(fence, &lrc->fence_ctx, __xe_lrc_seqno_map(lrc));
}
-struct dma_fence *xe_lrc_create_seqno_fence(struct xe_lrc *lrc)
-{
- struct dma_fence *fence = xe_lrc_alloc_seqno_fence();
-
- if (IS_ERR(fence))
- return fence;
-
- xe_lrc_init_seqno_fence(lrc, fence);
- return fence;
-}
-
s32 xe_lrc_seqno(struct xe_lrc *lrc)
{
struct iosys_map map = __xe_lrc_seqno_map(lrc);
diff --git a/drivers/gpu/drm/xe/xe_lrc.h b/drivers/gpu/drm/xe/xe_lrc.h
index 7a8752fd8484..c2df6bfd1889 100644
--- a/drivers/gpu/drm/xe/xe_lrc.h
+++ b/drivers/gpu/drm/xe/xe_lrc.h
@@ -47,7 +47,6 @@ u32 xe_lrc_seqno_ggtt_addr(struct xe_lrc *lrc);
struct dma_fence *xe_lrc_alloc_seqno_fence(void);
void xe_lrc_free_seqno_fence(struct dma_fence *fence);
void xe_lrc_init_seqno_fence(struct xe_lrc *lrc, struct dma_fence *fence);
-struct dma_fence *xe_lrc_create_seqno_fence(struct xe_lrc *lrc);
s32 xe_lrc_seqno(struct xe_lrc *lrc);
u32 xe_lrc_start_seqno_ggtt_addr(struct xe_lrc *lrc);
--
2.44.0
next prev parent reply other threads:[~2024-05-27 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 13:59 [PATCH v4 0/5] drm/xe: Allow migrate vm gpu submissions from reclaim context Thomas Hellström
2024-05-27 13:59 ` [PATCH v4 1/5] drm/xe: Decouple job seqno and lrc seqno Thomas Hellström
2024-05-27 13:59 ` [PATCH v4 2/5] drm/xe: Split lrc seqno fence creation up Thomas Hellström
2024-05-27 13:59 ` [PATCH v4 3/5] drm/xe: Don't initialize fences at xe_sched_job_create() Thomas Hellström
2024-05-27 13:59 ` Thomas Hellström [this message]
2024-05-27 13:59 ` [PATCH v4 5/5] drm/xe: Move job creation out of the struct xe_migrate::job_mutex Thomas Hellström
2024-05-27 14:05 ` ✓ CI.Patch_applied: success for drm/xe: Allow migrate vm gpu submissions from reclaim context Patchwork
2024-05-27 14:06 ` ✓ CI.checkpatch: " Patchwork
2024-05-27 14:07 ` ✓ CI.KUnit: " Patchwork
2024-05-27 14:18 ` ✓ CI.Build: " Patchwork
2024-05-27 14:19 ` ✗ CI.Hooks: failure " Patchwork
2024-05-27 14:20 ` ✓ CI.checksparse: success " Patchwork
2024-05-27 14:43 ` ✓ CI.BAT: " Patchwork
2024-05-27 15:35 ` ✗ CI.FULL: failure " Patchwork
2024-05-27 15:53 ` Thomas Hellström
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=20240527135912.152156-5-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@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