All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Antonio Argenziano <antonio.argenziano@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [RFC i-g-t 0/1] Introducing HW focused tests
Date: Fri, 02 Jun 2017 14:49:05 +0300	[thread overview]
Message-ID: <1496404145.3795.12.camel@linux.intel.com> (raw)
In-Reply-To: <20170531170037.35344-1-antonio.argenziano@intel.com>

Actually CC'ing Petri. When adding Cc's, it's usually better to Cc the
whole series (and make sure Cc's were effective).

On ke, 2017-05-31 at 10:00 -0700, Antonio Argenziano wrote:
> The IGT test suite aims at testing the functionalities of the i915
> graphics driver. Because of an increasing effort to move development and
> validation to the early stages in the development of new platforms, it
> is necessary to provide some form of coverage for scenarios where the
> driver assumes the HW will have a determined behaviour.
> 
> This patch introduces a more HW focused test that will send 'bad commands'
> to the GPU and expect they are dealt with accordingly. Since the test will
> not exercise i915 as such but rather rely on the HW to manage the issue, it
> is not suitable to be merged in the current IGT tests. A new folder,
> 'tests_hw' has been created to host such tests.
> 
> This is not intended to introduce an exhaustive test of the Intel GEN hardware,
> but, rather, as an attempt to instigate a discussion on what should be the
> proper procedure for managing and maintaining HW focused tests.
> 
> Cc: Latvala Petri <petri.latvala@intel.com>
> 
> Antonio Argenziano (1):
>   tests/gem_bad_address: Fix and update gem_bad_address
> 
>  Makefile.am                           |  4 ++
>  configure.ac                          | 11 ++++++
>  tests_hw/Makefile.am                  | 36 ++++++++++++++++++
>  tests_hw/Makefile.sources             |  8 ++++
>  {tests => tests_hw}/gem_bad_address.c | 69 ++++++++++++++++++++---------------
>  5 files changed, 98 insertions(+), 30 deletions(-)
>  create mode 100644 tests_hw/Makefile.am
>  create mode 100644 tests_hw/Makefile.sources
>  rename {tests => tests_hw}/gem_bad_address.c (50%)
> 
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-06-02 11:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 17:00 [RFC i-g-t 0/1] Introducing HW focused tests Antonio Argenziano
2017-05-31 17:00 ` [RFC i-g-t 1/1] tests/gem_bad_address: Fix and update gem_bad_address Antonio Argenziano
2017-06-05  9:06   ` Petri Latvala
2017-06-02 11:49 ` Joonas Lahtinen [this message]

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=1496404145.3795.12.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=antonio.argenziano@intel.com \
    --cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.