summaryrefslogtreecommitdiff
path: root/tests/i915
AgeCommit message (Collapse)Author
2021-10-08lib: Typechecking minmaxChris Wilson
Add typechecking to the min/max macros and make their locals truly unique-ish to reduce the risk of shadowing. v2: small bug fix, write also height coordinate on rotation test. (jheikkil) v3: Fix up a couple of other max/max_t instances (Ashutosh) Signed-off-by: Juha-Pekka Heikkilä <juha-pekka.heikkila@intel.com> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com> Signed-off-by: Chris Wilson <chris.p.wilson@intel.com> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
2021-10-08tests/i915/gem_exec_nop: Update poll sequentialPriyanka Dandamudi
set_caching ioctl will get skipped for discrete and mmap__cpu gets used by default. Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com> Cc: Matthew Auld <matthew.auld@intel.com> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
2021-10-07tests/gem_userptr_blits: Remove LOCAL_Rodrigo Vivi
These UAPIs are upstreamed now. Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
2021-10-06tests/i915_pxp: Use ioctl_wrapper for DRM_IOCTL_PRIME_HANDLE_TO_FDAlan Previn
Replace private helper with call to ioctl_wrapper for DRM_IOCTL_PRIME_HANDLE_TO_FD. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Michael J. Ruhl <michael.j.ruhl@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/kms_psr2_su: Skip test when necessaryJosé Roberto de Souza
The whole test needs to skip in display 13 platforms as PSR2_SU_STATUS is not being updated anymore by HW. It was not reliable in older display versions and now it is 100% dead. For display 12 and newer platforms now we have PSR2 selective fetch enabled default, so software is doing all the tracking of the areas that needs updates but we still can't do that for frontbuffer rendering so we are doing full frame fetches for now what will cause this test to fail, so also skipping it for the frontbuffer subtest. Cc: Jeevan B <jeevan.b@intel.com> Cc: Swati Sharma <swati2.sharma@intel.com> Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com> Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
2021-10-06Revert "tests/kms_psr: Skip h/w tracking PSR2 tests for ADL-P"José Roberto de Souza
PSR2 is now working on Alderlake-P so we can revert this patch. This reverts commit b5c6b973e7f7d33e7521825e39ddd380e80af01a. Cc: Jeevan B <jeevan.b@intel.com> Cc: Swati Sharma <swati2.sharma@intel.com> Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com> Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
2021-10-06tests/i915_pxp: CRC validation for display tests.Karthik B S
Added subtests to validate pxp using CRC validation. Signed-off-by: Karthik B S <karthik.b.s@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Verify protected surfaces are dma buffer sharableAlan Previn
Verify we can export a protected surface from protected context A into protected context B (with different client driver handles) and protected rendering is successful even after prior file handle is closed (i.e. pxp specific refcounting works). Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Verify execution behavior with stale PXP assets through ↵Alan Previn
suspend-resume Add a subtest to repeat the same previous three scenarios when attempting to execute work with either stale PXP contexts or buffers but this time trigger the teardown event via an S3 suspend-resume power state cycle. NOTE: The end-to-end architecture requirement includes that any break in the links of the PXP sessions needs to trigger a full teardown and the application needs to be made aware of that allowing it to re-establish the end-to-end pipeline of buffers, contexts and renders again if it chooses to. This stricter behavior targets only contexts created with PXP enabled. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Verify execbuf ok with stale PXP buf in opt-out useAlan Previn
Add a check to verify that reusing a stale protected buffer in a gem_execbuff call, but using a regular (not- protected) context will succeed after a teardown event. Trigger the teardown via the pxp invalidation debugfs that simulates a HW teardown IRQ. This ensures that user space applications that choose not to opt-in for strict PXP teardown awareness (by using a regular context) won't suffer gem_execbuff failures if a protected buffer was among the assets used in any of its rendering operations. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Verify execbuf fails with stale PXP buffer after teardownAlan Previn
Add a check to verify that reusing a stale protected buffer in a gem_execbuff (with a protected context) after a teardown event fails with -ENOEXEC error. Trigger the teardown via the pxp invalidation debugfs that simulates a HW teardown IRQ. NOTE: The end-to-end architecture requirement includes that any break in the links of the PXP sessions needs to trigger a full teardown and the application needs to be made aware of that allowing it to re-establish the end-to-end pipeline of buffers, contexts and renders again if it chooses to. This stricter behavior targets only contexts created with PXP enabled. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Verify execbuf fails with stale PXP context after teardownAlan Previn
Add a subtest to verify that reusing a stale protected context in a gem_execbuff after a teardown fails with -EIO error because it's banned. Trigger the teardown via the pxp invalidation debugfs that simulates a HW teardown IRQ. NOTE: The end-to-end architecture requirement includes that any break in the links of the PXP sessions needs to trigger a full teardown and the application needs to be made aware of that allowing it to re-establish the end-to-end pipeline of buffers, contexts and renders again if it chooses to. This stricter behavior targets only contexts created with PXP enabled. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Verify PXP teardown occurred through suspend-resumeAlan Previn
During a suspend-resume cycle, the driver shall ensure the PXP session and keys are torn down and re-established. Verify that key change did occur by repeating the 3d rendercopy operation before and after the suspend-resume cycle and ensuring the encrypted output is different. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Add test where both src and dest are protectedAlan Previn
When both the source and destination surfaces are protected, the destination pixel result of the 3d copy operation would be the same as the source. By appending this test case to the end of the prior test (raw-src to protected-dest) and reusing the previous' test destination as the current source, we can prove that new-source was decrypted properly as we would see the difference in results: repeating the same render operation but with a src buffer that is protected in this case yields matching (but still encrypted) output rendered pixels. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Add subtest to copy raw source to protected destAlan Previn
Add subtest to 3d-copy raw source buffer (with known readible content) to a destination buffer marked as protected with a protected session using default session keys. The destination buffer is verified to be different from the source (when read via CPU) because its encrypted. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Perform a regular 3d copy as a control checkpointAlan Previn
As a control checkpoint, allocate buffers to be used as texture and render target in the 3d engine for a regular src to dest copy blit and verify buffer pixels. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-06tests/i915/gem_pxp: Add basic PXP testing of buffer and context allocAlan Previn
Test PXP capability support as well as the allocation of protected buffers and protected contexts. Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
2021-10-05lib/intel_bufops: Store gem bo sizeZbigniew Kempczyński
intel_buf is keeping its size which may differ to underlying gem bo size. Introduce keeping bo_size field which is used along with softpin mode - like in intel_bb. Patch also should remove previous discrepancy where intel_buf_bo_size() returned requested (not gem bo size). From now on user has an access to: 1. raw buffer size - intel_buf_size() - function returns how buffer data really takes in the memory 2. gem bo buffer size - intel_buf_bo_size() - function returns how big underlying gem object is Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-10-05lib/intel_bufops: Rename intel_buf_bo_size() -> intel_buf_size()Zbigniew Kempczyński
To avoid confusion with intel_buf_bo_size() which for some buffers can return size not equal to underlying gem bo size rename it to intel_buf_size(). Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-10-05tests/kms_invalid_mode: Allow the test on !i915Ville Syrjälä
The only i915 specific subtest is the max dotclock check, so let's add the i915 check there and switch from DRIVER_INTEL to DRIVER_ANY so that the other subtests can run everywhere. Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-05tests/kms_invalid_mode: Test clock==(U)INT_MAXVille Syrjälä
Test against some big clock values to make sure we can't trick the kernel into bypassing the validation via an integer overflows/etc. Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-05tests/kms_invalid_mode: Test various bogus timingsVille Syrjälä
Make sure the mode gets rejected when some part of the timings is bogus. v2: Add even more tests Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-05tests/kms_invalid_mode: Move bigjoiner handling into the proper placeVille Syrjälä
Since we're adding other subtests we don't want to muck around with the dotclock unconditionally in the main test code. Move the handling into the subtest specific adjust function. Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-05tests/kms_invalid_mode: Convert the max dotclock test into a subtestVille Syrjälä
We want to add different subtests to kms_invalid_mode. Convert the current max dotclock test into a subtest. v2: Drop igt_skip_on_simulation() (Karthik,Petri) Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-05tests/kms_invalid_dotclock: Rename to kms_invalid_modeVille Syrjälä
Let's add some more tests for invalid modes. To that end rename the current kms_invalid_dotclock to kms_invalid_mode so we have a place where to put these. Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-10-04tests/i915: use device_coherent mmapPriyanka Dandamudi
Update mmap__wc with mmap__device_coherent, as it works on discrete platforms, while still using an explicit WC mmap on integrated platforms. Below are the updated tests: gem_exec_capture gem_exec_nop perf_pmu prime_busy Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com> Cc: Matthew Auld <matthew.auld@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
2021-10-03lib: Partially revert 22643ce4014aAshutosh Dixit
In 22643ce4014a ("Return allocated size in gem_create_in_memory_regions() and friends") we modified __gem_create_in_memory_regions and gem_create_in_memory_regions to return the allocated size for buffer objects. However, this also unnecessarily complicates programming in the majority of cases where the allocated size is not needed. For example in several cases it requires tracking the requested and allocated sizes separately, the size used must be strictly uint64_t etc. In order to simplify things and provide greater flexibility, here we change 22643ce4014a to follow the same scheme followed in gem_create_ext (and in gem_create) where __gem_create_ext returns the allocated size but gem_create_ext doesn't. With this change, __gem_create_in_memory_regions returns the allocated size for situations where it is needed but in the majority of cases where the allocated size is not needed we can just use gem_create_in_memory_regions for casual use as before. v2: Store requested not allocated bo size in intel_buf->size (Zbigniew) Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-10-01tests/i915/i915_pm_dc: Changing sysfs open attribute to O_RDONLYJigar Bhatt
Opening /sys/module/drm_kms_helper/parameters/ in read only mode to avoid permission issue in dc9-dpms test. Signed-off-by: Jigar Bhatt <jigar.bhatt@intel.com> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
2021-09-29Return allocated size in gem_create_in_memory_regions() and friendsAshutosh Dixit
Often the allocated size is of interest and is different from the requested size. Therefore return allocated size for the object (by __gem_create_ext()) in gem_create_in_memory_regions() and friends. v2: Assign buf->size correctly in __intel_buf_init (Zbigniew) Cc: Andrzej Turko <andrzej.turko@linux.intel.com> Cc: Zbigniew Kempczynski <zbigniew.kempczynski@intel.com> Cc: John Harrison <John.C.Harrison@intel.com> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
2021-09-28tests/i915/i915_pm_dc: Fix DC9 testJigar Bhatt
Fixing DC9 test with reading prev_dc counter(DC5/DC6), comparing to actual counter values. Dumping i915_pm_runtime_status debugfs incase of failure. While executing test, it require to disable the kms connector polling to avoid runtime resume. This would require to save and restore the kms connector poll state. V1: Reading previous DC counter prev_dc = read_dc_counter(dc_target) before the dpms_off(). V2: Bit cleaner code.[Imre] dump the i915_pm_runtime_status debugfs file in case of test failure.[Anshuman] V3: Disabling the polling during DC9 test “echo 0 > /sys/module/drm_kms_helper/parameters/poll”.[Anshuman] V4: Passing right fd to igt_sysfs_get_boolean() function, moving save and get part of polling to setup_dc9_dpms(). V5: Use macro for "/sys/module/drm_kms_helper/parameters/poll". Add igt_require when opening sysfs. Add igt_install_exit_handler(reset_kms_poll) so it will restore actual sysfs kms polling status.[Anshuman] V6: Using if() condition instead of igt_require((sysfs_fd = open(KMS_POLL_PATH, O_WRONLY)) >= 0) [Petri] V7: KMS_HELPER "/sys/module/drm_kms_helper/parameters/ " for opening the sys_fd and then use it in igt_sysfs_get_boolean() along with "poll", attribute as per the API doc.[Anshuman] Signed-off-by: Jigar Bhatt <jigar.bhatt@intel.com> Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
2021-09-28tests/i915/i915_pm_dc: Refactoring pwr_dmn_info to debugfs_dumpJigar Bhatt
Refactoring pwr_dmn_info to debugfs_dump so other test can use it for dumping debugfs file.[Anshuman] Signed-off-by: Jigar Bhatt <jigar.bhatt@intel.com> Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
2021-09-26tests/i915/gem_cs_tlb: Drop gem_require_ring() checkAshutosh Dixit
80f48722f429 ("tests/i915/gem_cs_tlb: Convert to intel_ctx_t") passes a intel_ctx_t (initialized with intel_ctx_create_all_physical()) into run_on_ring(). However gem_require_ring() checks if the ring is available to context 0, not the intel_ctx_t which is passed in. This will cause the test to skip for all engines not available to context 0. Hence drop the gem_require_ring() check since we already know that the intel_ctx_t has all physical engines available to it. Cc: "Zbigniew Kempczynski <zbigniew.kempczynski@intel.com>" Fixes: 80f48722f429 ("tests/i915/gem_cs_tlb: Convert to intel_ctx_t") Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Arjun Melkaveri <arjun.melkaveri@intel.com>
2021-09-21tests/kms_big_fb: Use igt_has_drm_cap()Ville Syrjälä
Replace the hand rolled cap check with igt_has_drm_cap(). Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-09-21tests/kms_big_fb: Use igt_plane_has_rotation()Ville Syrjälä
Use igt_plane_has_rotation() instead of the manual "if there's no rotation prop -> only 0 dgree is supported" conclusion. And let's also get rid of the atomic vs. 0/270 degree rotation check. I think I added this to avoid the test failing since we can't do the TEST_ONLY probe withoiut atomic. With the unsupported rotations filtered out ahead of time we should never get into that situation. Reviewed-by: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
2021-09-16tests/kms: Move Intel specific kms tests to i915 directoryBhanuprakash Modem
As KMS tests on IGT are officially supported on multiple SoCs and there is an active development on it. So, KMS tests are meant to be generic and if we need to test few things specific to Intel, we can use igt_require_intel(). But if the whole test is Intel specific, then the best place for the test would be tests/i915. This patch will * Move all Intel specific kms tests to tests/i915 directory. * Update the tests those are generic but still open the driver as 'drm_open_driver_master(DRIVER_INTEL);'. V2: * Few more tests V3: * Remove cleanups (will submit separate patch later) * Move few more tests to i915 dir (Karthik) V4: * Move kms_big_joiner.c to i915 dir (Karthik) Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Mark Yacoub <markyacoub@chromium.org> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Vidya Srinivas <vidya.srinivas@intel.com> Cc: Karthik B S <karthik.b.s@intel.com> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com> Reviewed-by: Mark Yacoub <markyacoub@chromium.org> Reviewed-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> Reviewed-by: Karthik B S <karthik.b.s@intel.com>
2021-09-13i915/gem_render_copy: Add support for local memoryApoorva Singh
Add support for local memory region (Device memory) Signed-off-by: Apoorva Singh <apoorva1.singh@intel.com> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> Cc: Melkaveri, Arjun <arjun.melkaveri@intel.com> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
2021-09-08test/gem_exec_suspend: Enable the test for discrete GPUsThomas Hellström
Discrete GPUs don't support gem_set_caching() and uses a single, kernel provided caching mode, FIXED. Adjust the test accordingly. This makes the test run on DG1. v2: - Use igt_require() do determine which of the caching mode subtests to run. (Petri Latvala) - Pass the ctx parameter to igt_spin_new(), as it appears to be needed for the hang-SX subtests to run on DG1. Cc: Petri Latvala <petri.latvala@intel.com> Reviewed-by: Matthew Auld <matthew.auld@intel.com> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
2021-09-07i915/i915_fb_tiling: Check if device supports tilingVanshidhar Konda
Skip this test if the platform does not support setting tiling for frame buffer object. Signed-off-by: Vanshidhar Konda <vanshidhar.r.kondai@ntel.com> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Imre Deak <imre.deak@intel.com>
2021-08-30tests/i915/gem_exec_schedule: Resolve missing context for independent subtestArjun Melkaveri
Resolved missing context id in exec buf, and passing created context to igt spin . This change would fix test assertion in gem_execbuf for independent subtest v2: Passing original ctx id to gem_execbuf Signed-off-by: Arjun Melkaveri <arjun.melkaveri@intel.com> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-26tests/i915/gem_exec_nop: Resolve missing context id in sequential testArjun Melkaveri
Resolved missing context id in exec buf, for sequential test. This was due to context mutation changes that was implemeted in gem_exec_nop. Signed-off-by: Arjun Melkaveri <arjun.melkaveri@intel.com> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Acked-by: Ch Sai Gowtham <sai.gowtham.ch@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-25tests/gem_exec_params: Fix context within which batch is executedZbigniew Kempczyński
With new intel_ctx_t we're responsible to set execbuf rsvd1 (context) id field. As same field exists for exec object there's risk to mechanically set improper field and compiler won't complain. Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Cc: Jason Ekstrand <jason@jlekstrand.net> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-23i915/gem_gpgpu_fill: Add support for local memoryApoorva Singh
Add support for local memory region (Device memory) Signed-off-by: Apoorva Singh <apoorva1.singh@intel.com> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> Cc: Melkaveri, Arjun <arjun.melkaveri@intel.com> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
2021-08-23i915/gem_media_fill: Add support for local memoryApoorva Singh
Add support for local memory region (Device memory) Signed-off-by: Apoorva Singh <apoorva1.singh@intel.com> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com> Cc: Melkaveri, Arjun <arjun.melkaveri@intel.com> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
2021-08-20tests/i915/exec_balancer: Added Skip invalid-bondsMastan Katragadda
Added skip which ever gen12+ platforms not supporting bonding. Disable bonding on gen12+ platforms aside from ones already supported by the i915 - TGL, RKL, and ADL-S. Link: https://cgit.freedesktop.org/drm-tip/commit/?id=ce7e75c7ef1bf8ea3d947da8c674d2f40fd7d73 Changes since V1: - Updated skip assertion logic (Ashutosh) Signed-off-by: Mastan Katragadda <mastanx.katragadda@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-20tests/gem_shrink: Add allocator supportCh Sai Gowtham
Signed-off-by: Ch Sai Gowtham <sai.gowtham.ch@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
2021-08-20tests/gem_ctx_shared: Adopt to use allocatorZbigniew Kempczyński
For newer gens we're not able to rely on relocations. Adopt to use offsets acquired from the allocator. Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-18tests/gem_exec_schedule: Adopt to use allocatorZbigniew Kempczyński
Alter tests to cover reloc and no-reloc (softpin) modes. v2: fix pi-* subtests v3: addressing review comments (Ashutosh) Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-18tests/gem_exec_fence: Adopt to use allocatorZbigniew Kempczyński
For newer gens we're not able to rely on relocations. Adopt to use offsets acquired from the allocator. Three subtests are not covered here, there are: - syncobj-timeline-chain-engines - syncobj-stationary-timeline-chain-engines - syncobj-backward-timeline-chain-engines Due to sophisticated manner of the three tests mentioned above they will be subject of separate patch. At the moment CI depends on reloc version only so this doesn't introduce regression there and decreases coverage gap on no-reloc discrete runs. Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Signed-off-by: Andrzej Turko <andrzej.turko@linux.intel.com> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-17tests/gem_exec_big: Move check of pressumed offset out of no-reloc scopeZbigniew Kempczyński
Missed during addressing last review - we don't want to process checking of pressumed offset on no-reloc path. Move this out of no-reloc scope. Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
2021-08-17tests/gem_exec_capture: Remove unnecessary multiprocess stop() callZbigniew Kempczyński
I've incidentally missed this during review and line calling intel_allocator_multiprocess_stop() left before merge. Remove this as source of confusion - for igt_fork() we can use standalone allocator within child for some cases (reopen driver or work within new created context). Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com> Cc: Petri Latvala <petri.latvala@intel.com> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-02 05:48:31 +0000