Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Welty <brian.welty@intel.com>
To: Vanshidhar Konda <vanshidhar.r.konda@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH 2/2] i915/i915_fb_tiling: Check if device supports tiling
Date: Tue, 19 Nov 2019 14:44:28 -0800	[thread overview]
Message-ID: <93e8e590-2e0b-145e-a538-3664aade3d54@intel.com> (raw)
In-Reply-To: <20191119223322.77446fvgwvwcch47@vrkonda-desk.ra.intel.com>



On 11/19/2019 2:33 PM, Vanshidhar Konda wrote:
> On Tue, Nov 19, 2019 at 02:23:41PM -0800, Brian Welty wrote:
>>
>>
>> On 11/15/2019 3:16 PM, Vanshidhar Konda wrote:
>>> Skip this test if the platform does not support setting tiling for frame
>>> buffer object.
>>>
>>
>> Looking over some other tests, I came across a libdrm function that uses SET_TILING,
>> drm_intel_bo_alloc_tiled().
>>
>> Any chance you can expand your patch series to fix tests using that function as well?
> 
> The change to igt doesn't apply directly to libdrm. libdrm change will
> have to come seperately.

Yes, libdrm changes would be separate.
I only meant that until that happens, the igts could be fixed to use igt_require
before the offending libdrm function calls.  Just as you have done here....
so just as you have identified not to call igt_create_fb(), there are few libdrm
functions that should not be used by igts either (at least not unless 'legacy tiling'
is supported).

> 
>> It is not quite as easy, I believe you maybe shouldn't disable them all but should
>> maybe conditionally use drm_intel_bo_alloc_tiled() or drm_intel_bo_alloc().
>> Not sure.
> 
> I was asked to put FIXME in the patches where I'm skipping execution of these tests.
> I was thinking that since the GET/SET_TILING feature doesn't exist anymore the only
> solution was to just remove these tests. I'm going to start a discussion on this to
> finalize if the change is just a FIXME or if that is the final change.
> 
> Once we close on that discussion, I think we can fix on whether these methods
> should fail with an error and the tests calling these need to be fixed.
> For now things still seem to be in a limbo.
> 
> Vanshi
> 
>>
>> Thanks,
>> -Brian
>>
>>
>>> Signed-off-by: Vanshidhar Konda <vanshidhar.r.konda@intel.com>
>>> Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>>> ---
>>>  tests/i915/i915_fb_tiling.c | 2 ++
>>>  1 file changed, 2 insertions(+)
>>>
>>> diff --git a/tests/i915/i915_fb_tiling.c b/tests/i915/i915_fb_tiling.c
>>> index 7d5c3f1f..4ec84962 100644
>>> --- a/tests/i915/i915_fb_tiling.c
>>> +++ b/tests/i915/i915_fb_tiling.c
>>> @@ -32,6 +32,8 @@ igt_simple_main
>>>      struct igt_fb fb;
>>>      int ret;
>>>
>>> +    igt_require(gem_has_legacy_hw_tiling(drm_fd));
>>> +
>>>      igt_create_fb(drm_fd, 512, 512, DRM_FORMAT_XRGB8888,
>>>                LOCAL_I915_FORMAT_MOD_X_TILED, &fb);
>>>
>>>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-11-19 22:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 23:16 [igt-dev] [PATCH 0/2] Check if get/set tiling is supported Vanshidhar Konda
2019-11-15 23:16 ` [igt-dev] [PATCH 1/2] lib/ioctl_wrappers: Query if device supports set/get legacy tiling Vanshidhar Konda
2019-11-15 23:16 ` [igt-dev] [PATCH 2/2] i915/i915_fb_tiling: Check if device supports tiling Vanshidhar Konda
2019-11-19 22:23   ` Brian Welty
2019-11-19 22:33     ` Vanshidhar Konda
2019-11-19 22:44       ` Brian Welty [this message]
2019-11-19 22:51         ` Vanshidhar Konda
2019-11-15 23:50 ` [igt-dev] ✓ Fi.CI.BAT: success for Check if get/set tiling is supported Patchwork
2019-11-17 13:09 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-11-15  5:33 [igt-dev] [PATCH 0/2] " Vanshidhar Konda
2019-11-15  5:33 ` [igt-dev] [PATCH 2/2] i915/i915_fb_tiling: Check if device supports tiling Vanshidhar Konda

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=93e8e590-2e0b-145e-a538-3664aade3d54@intel.com \
    --to=brian.welty@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=vanshidhar.r.konda@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