Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ruhl, Michael J" <michael.j.ruhl@intel.com>
To: "Latvala, Petri" <petri.latvala@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	Mohammed Khajapasha <mohammed.khajapasha@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 08/11] tests/kms_addfb_basic: Add invalid buffer object test for discrete
Date: Thu, 10 Jun 2021 12:50:32 +0000	[thread overview]
Message-ID: <ecc9e9ed02054e1d8ab2f82557e34a5f@intel.com> (raw)
In-Reply-To: <YMIJqcUpIenSJE+r@platvala-desk.ger.corp.intel.com>

>-----Original Message-----
>From: Latvala, Petri <petri.latvala@intel.com>
>Sent: Thursday, June 10, 2021 8:47 AM
>To: Ruhl, Michael J <michael.j.ruhl@intel.com>
>Cc: Patnana, Venkata Sai <venkata.sai.patnana@intel.com>; igt-
>dev@lists.freedesktop.org; Mohammed Khajapasha
><mohammed.khajapasha@intel.com>
>Subject: Re: [PATCH i-g-t 08/11] tests/kms_addfb_basic: Add invalid buffer
>object test for discrete
>
>On Thu, Jun 10, 2021 at 03:30:46PM +0300, Ruhl, Michael J wrote:
>> >-----Original Message-----
>> >From: Patnana, Venkata Sai <venkata.sai.patnana@intel.com>
>> >Sent: Wednesday, June 9, 2021 8:18 AM
>> >To: igt-dev@lists.freedesktop.org
>> >Cc: Patnana, Venkata Sai <venkata.sai.patnana@intel.com>; Mohammed
>> >Khajapasha <mohammed.khajapasha@intel.com>; Latvala; Latvala, Petri
>> ><petri.latvala@intel.com>; Ruhl, Michael J <michael.j.ruhl@intel.com>
>> >Subject: [PATCH i-g-t 08/11] tests/kms_addfb_basic: Add invalid buffer
>object
>> >test for discrete
>> >
>> >From: Mohammed Khajapasha <mohammed.khajapasha@intel.com>
>> >
>> >Add invalid buffer object test case for discrete, to validate
>> >IOCTL_MODE_ADDFB2 ioctl for LMEM, the framebuffer backing
>> >gem objects should be from local memory for discrete.
>> >
>> >Cc: Latvala, Petri <petri.latvala@intel.com>
>> >Cc: Michael J. Ruhl <michael.j.ruhl@intel.com>
>> >Signed-off-by: Mohammed Khajapasha
>> ><mohammed.khajapasha@intel.com>
>> >---
>> > tests/kms_addfb_basic.c | 16 ++++++++++++++++
>> > 1 file changed, 16 insertions(+)
>> >
>> >diff --git a/tests/kms_addfb_basic.c b/tests/kms_addfb_basic.c
>> >index 1fb18d668f..aac74a7568 100644
>> >--- a/tests/kms_addfb_basic.c
>> >+++ b/tests/kms_addfb_basic.c
>> >@@ -40,6 +40,7 @@
>> >
>> > #include "igt_rand.h"
>> > #include "igt_device.h"
>> >+#include "i915/intel_memory_region.h"
>> >
>> > uint32_t gem_bo;
>> > uint32_t gem_bo_small;
>> >@@ -146,6 +147,21 @@ static void invalid_tests(int fd)
>> > 		igt_assert(f.modifier[0] == 0);
>> > 	}
>> >
>> >+	igt_subtest("invalid-smem-bo-on-discrete") {
>> >+		int devid;
>> >+		uint32_t handle, stride;
>> >+		uint64_t size;
>> >+
>> >+		igt_require_intel(fd);
>> >+		devid = intel_get_drm_devid(fd);
>>
>> This will only work on if the discrete card is the only card on the system.
>>
>> Is there a better way to:
>>
>> 1) identify discrete cards and/or
>> 2) specifically select a discrete card for testing?
>
>The test does not select the device to use. The admin _running_ the
>test does that, with IGT_DEVICE.

Ok, that makes sense.

I believe you (Petri) had a comment that should be addressed,
but from my perspective

Acked-by: Michael J. Ruhl <michael.j.ruhl@intel.com>

>With that done, mapping of results will be
>
>non-intel: skip
>intel integrated: skip
>intel discrete: actually tested
>
>which looks correct. We're trying to test what happens specifically
>if the used device is intel discrete, skip otherwise.

>
>--
>Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2021-06-10 12:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 12:17 [igt-dev] [PATCH i-g-t 01/11] tests/kms_dither: New IGT to validate crtc Dithering venkata.sai.patnana
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 02/11] tests/kms_dither: Validate dither after CC blocks venkata.sai.patnana
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 03/11] tests/kms_dither: Dont assert if debugfs is not present venkata.sai.patnana
2021-06-10  7:41   ` Petri Latvala
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 04/11] tests/device_reset: Unload snd driver before i915 unbind venkata.sai.patnana
2021-06-10  7:32   ` Janusz Krzysztofik
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 05/11] tests/core_hotunplug: " venkata.sai.patnana
2021-06-10  7:37   ` Janusz Krzysztofik
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 06/11] tests/kms_force_connector_basic: Skip prune stale mode venkata.sai.patnana
2021-06-10  7:42   ` Petri Latvala
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 07/11] tests/kms: Create buffer object from LMEM for discrete venkata.sai.patnana
2021-06-10  7:54   ` Petri Latvala
2021-06-10 12:31   ` Ruhl, Michael J
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 08/11] tests/kms_addfb_basic: Add invalid buffer object test " venkata.sai.patnana
2021-06-10  8:08   ` Petri Latvala
2021-06-10  8:20     ` Petri Latvala
2021-06-10 12:30   ` Ruhl, Michael J
2021-06-10 12:46     ` Petri Latvala
2021-06-10 12:50       ` Ruhl, Michael J [this message]
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 09/11] tests/kms_dp_dsc: Read the debugfs only once venkata.sai.patnana
2021-06-10  6:07   ` Karthik B S
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 10/11] tests/kms_big_fb: Add max HW stride length tests venkata.sai.patnana
2021-06-09 12:17 ` [igt-dev] [PATCH i-g-t 11/11] tests/kms_big_fb: Add max hw stride lenght async flip test venkata.sai.patnana
2021-06-10  6:14   ` Karthik B S
2021-06-09 13:54 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,01/11] tests/kms_dither: New IGT to validate crtc Dithering Patchwork
2021-06-09 15:23 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

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=ecc9e9ed02054e1d8ab2f82557e34a5f@intel.com \
    --to=michael.j.ruhl@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mohammed.khajapasha@intel.com \
    --cc=petri.latvala@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