From: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [i-g-t] tests/intel/kms_ccs: Avoid i915 calls on XE device
Date: Mon, 30 Oct 2023 22:04:58 +0530 [thread overview]
Message-ID: <20231030163458.4101383-1-bhanuprakash.modem@intel.com> (raw)
For XE device, use XE specific APIs to create the BO.
Fixes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/812
Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
---
tests/intel/kms_ccs.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/tests/intel/kms_ccs.c b/tests/intel/kms_ccs.c
index 09b98fbec..64489b7a3 100644
--- a/tests/intel/kms_ccs.c
+++ b/tests/intel/kms_ccs.c
@@ -33,6 +33,7 @@
#include "i915/gem_create.h"
#include "xe/xe_ioctl.h"
+#include "xe/xe_query.h"
/**
* SUBTEST: %s-%s-%s
@@ -431,7 +432,10 @@ static void test_bad_ccs_plane(data_t *data, int width, int height, int ccs_plan
/* Put the CCS buffer on a different BO. */
if (data->flags & TEST_BAD_CCS_HANDLE) {
- bad_ccs_bo = gem_create(data->drm_fd, fb.size);
+ bad_ccs_bo = is_i915_device(data->drm_fd) ?
+ gem_create(data->drm_fd, fb.size) :
+ xe_bo_create_flags(data->drm_fd, 0, fb.size,
+ visible_vram_if_possible(data->drm_fd, 0));;
f.handles[ccs_plane] = bad_ccs_bo;
}
--
2.40.0
next reply other threads:[~2023-10-30 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 16:34 Bhanuprakash Modem [this message]
2023-10-30 20:54 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/intel/kms_ccs: Avoid i915 calls on XE device Patchwork
2023-10-30 22:22 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-10-31 1:04 ` [igt-dev] ✓ CI.xeBAT: success for tests/intel/kms_ccs: Avoid i915 calls on XE device (rev2) Patchwork
2023-10-31 1:07 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-11-01 9:42 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-02 11:45 ` [igt-dev] [i-g-t] tests/intel/kms_ccs: Avoid i915 calls on XE device Juha-Pekka Heikkila
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=20231030163458.4101383-1-bhanuprakash.modem@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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