From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] igt/kms_rotation_crc: Add a subtest to validate Y-tiled obj + Y fb modifier
Date: Tue, 20 Oct 2015 10:10:20 +0100 [thread overview]
Message-ID: <562604FC.4060407@linux.intel.com> (raw)
In-Reply-To: <20151019181438.6c4ed7aa@vkasired-desk2.amr.corp.intel.com>
On 20/10/15 02:14, Vivek Kasireddy wrote:
> Hi Tvrtko,
>
> On Mon, 19 Oct 2015 11:20:05 +0100
> Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
>
>>
>> Hi,
>>
>> On 17/10/15 03:47, Vivek Kasireddy wrote:
>>> The main goal of this subtest is to verify whether flipping a
>>> framebuffer with a Y fb modifier (90/270 degree rotation) and
>>> an associated Y-tiled object works or not.
>>>
>>> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>> Signed-off-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
>>> ---
>>> tests/kms_rotation_crc.c | 83
>>> ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 83
>>> insertions(+)
>>>
>>> diff --git a/tests/kms_rotation_crc.c b/tests/kms_rotation_crc.c
>>> index cc9847e..bb9aecb 100644
>>> --- a/tests/kms_rotation_crc.c
>>> +++ b/tests/kms_rotation_crc.c
>>> @@ -264,6 +264,83 @@ static void test_plane_rotation(data_t *data,
>>> enum igt_plane plane_type) igt_require_f(valid_tests, "no valid
>>> crtc/connector combinations found\n"); }
>>>
>>> +static void test_plane_rotation_ytiled_obj(data_t *data, enum
>>> igt_plane plane_type) +{
>>> + igt_display_t *display = &data->display;
>>> + uint64_t tiling = LOCAL_I915_FORMAT_MOD_Y_TILED;
>>> + uint32_t format = DRM_FORMAT_XRGB8888;
>>> + int bpp = igt_drm_format_to_bpp(format);
>>> + enum igt_commit_style commit = COMMIT_LEGACY;
>>> + int fd = data->gfx_fd;
>>> + int valid_tests = 0;
>>> + igt_output_t *output;
>>> + int ret;
>>> +
>>> + if (plane_type == IGT_PLANE_PRIMARY || plane_type ==
>>> IGT_PLANE_CURSOR) {
>>> + igt_require(data->display.has_universal_planes);
>>> + commit = COMMIT_UNIVERSAL;
>>> + }
>>> +
>>> + for_each_connected_output(display, output) {
>>> + igt_plane_t *plane;
>>> + drmModeModeInfo *mode =
>>> igt_output_get_mode(output);
>>> + unsigned int w = mode->hdisplay;
>>> + unsigned int h = mode->vdisplay;
>>> + unsigned int stride, size;
>>> + uint32_t gem_handle;
>>> +
>>> + for (stride = 512; stride < (w * bpp / 8); stride
>>> *= 2)
>>> + ;
>>> + for (size = 1024*1024; size < stride * h; size *=
>>> 2)
>>> + ;
>>> +
>>> + gem_handle = gem_create(fd, size);
>>> + ret = __gem_set_tiling(fd, gem_handle,
>>> I915_TILING_Y, stride);
>>> + igt_assert(ret == 0);
>>> +
>>> + do_or_die(__kms_addfb(fd, gem_handle, w, h, stride,
>>> + format, tiling,
>>> LOCAL_DRM_MODE_FB_MODIFIERS,
>>> + &data->fb.fb_id));
>>> +
>>> + data->fb.width = w;
>>> + data->fb.height = h;
>>> + data->fb.gem_handle = gem_handle;
>>> + data->fb.stride = stride;
>>> + data->fb.size = size;
>>> + data->fb.tiling = tiling;
>>> + data->fb.drm_format = format;
>>> +
>>> + plane = igt_output_get_plane(output, plane_type);
>>> + igt_require(igt_plane_supports_rotation(plane));
>>> +
>>> + igt_plane_set_fb(plane, NULL);
>>> + igt_display_commit(display);
>>> +
>>> + igt_plane_set_rotation(plane, data->rotation);
>>> + paint_squares(data, mode, IGT_ROTATION_0, plane);
>>> + igt_plane_set_fb(plane, &data->fb);
>>> +
>>> + drmModeObjectSetProperty(fd,
>>> plane->drm_plane->plane_id,
>>> + DRM_MODE_OBJECT_PLANE,
>>> + plane->rotation_property,
>>> + plane->rotation);
>>> + ret = igt_display_try_commit2(display, commit);
>>> + igt_assert(ret == 0);
>>
>> This manages to trigger the WARN? How come since paint_squares above
>> will have created the normal VMA?
>
> Yes, this does trigger the WARN regardless of whether paint_squares is
> called or not. I am going to have to find out why the normal VMA was
> not created when paint_squares was called. And, this subtest does not
> restore the console cleanly which is something I also have to fix.
Could be that normal VMA is not created in the Cairo rendering path for
Y tiled buffers. Since the final rendering is done via a blit and if you
have PPGTT that would do it I think.
If PPGTT is always true for gen9 then this could work.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-20 9:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 10:59 [PATCH i-g-t 1/3] lib/igt_fb: Allow specifiying object tiling when creating frame buffers Tvrtko Ursulin
2015-10-16 10:59 ` [PATCH i-g-t 2/3] lib/igt_kms: Set new rotation property before displaying Tvrtko Ursulin
2015-10-16 10:59 ` [PATCH i-g-t 3/3] kms_rotation_crc: Test case for rotated VMA first with legacy tiling Tvrtko Ursulin
2015-10-16 12:03 ` [PATCH i-g-t 1/3] lib/igt_fb: Allow specifiying object tiling when creating frame buffers Ville Syrjälä
2015-10-16 12:19 ` Tvrtko Ursulin
2015-10-16 12:29 ` Ville Syrjälä
2015-10-16 12:54 ` Tvrtko Ursulin
2015-10-16 13:01 ` Ville Syrjälä
2015-10-16 13:06 ` Tvrtko Ursulin
2015-10-17 2:47 ` [PATCH] igt/kms_rotation_crc: Add a subtest to validate Y-tiled obj + Y fb modifier Vivek Kasireddy
2015-10-19 10:20 ` Tvrtko Ursulin
2015-10-20 1:14 ` Vivek Kasireddy
2015-10-20 9:10 ` Tvrtko Ursulin [this message]
2015-10-21 1:41 ` Vivek Kasireddy
2015-10-22 1:24 ` [PATCH] igt/kms_rotation_crc: Add a subtest to validate Y-tiled obj + Y fb modifier (v2) Vivek Kasireddy
2015-10-22 9:56 ` Tvrtko Ursulin
2015-10-23 1:34 ` [PATCH] igt/kms_rotation_crc: Add a subtest to validate Y-tiled obj + Y fb modifier (v3) Vivek Kasireddy
2015-10-23 8:51 ` Tvrtko Ursulin
2015-10-23 11:35 ` Daniel Vetter
2015-10-24 1:03 ` Vivek Kasireddy
2015-10-27 10:37 ` Tvrtko Ursulin
2015-10-29 1:48 ` [PATCH] igt/kms_rotation_crc: Add a subtest to validate Y-tiled obj + Y fb modifier (v4) Vivek Kasireddy
2015-10-29 10:33 ` Tvrtko Ursulin
2015-10-30 1:44 ` [PATCH] igt/kms_rotation_crc: Add a subtest to validate Y-tiled obj + Y fb modifier (v5) Vivek Kasireddy
2015-10-30 10:22 ` Tvrtko Ursulin
2015-10-31 1:45 ` Vivek Kasireddy
2015-11-02 9:41 ` Tvrtko Ursulin
2015-11-02 13:36 ` [PATCH] igt/kms_rotation_crc: Add a subtest to validate Y-tiled obj + Y fb modifier (v3) Thomas Wood
2015-11-03 1:25 ` [PATCH] igt/kms_rotation_crc: Add a new subtest to exhaustively test for fence leaks Vivek Kasireddy
2015-11-03 10:02 ` Tvrtko Ursulin
2015-11-04 2:25 ` [PATCH] igt/kms_rotation_crc: Add a new subtest to exhaustively test for fence leaks (v2) Vivek Kasireddy
2015-11-04 10:07 ` Tvrtko Ursulin
2015-11-05 0:10 ` [PATCH] igt/kms_rotation_crc: Add a new subtest to exhaustively test for fence leaks (v3) Vivek Kasireddy
2015-11-05 9:46 ` Tvrtko Ursulin
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=562604FC.4060407@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vivek.kasireddy@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