Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio Argenziano <antonio.argenziano@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Petri Latvala <petri.latvala@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 2/4] tests: Move gem_bad_address to hw-tests
Date: Fri, 15 Dec 2017 11:43:40 -0800	[thread overview]
Message-ID: <0da39cba-3838-7802-d8ba-0852f6313b57@intel.com> (raw)
In-Reply-To: <151317160480.11713.11113338002391398846@mail.alporthouse.com>



On 13/12/17 05:26, Chris Wilson wrote:
> Quoting Petri Latvala (2017-12-13 12:58:14)
>> Since the test is considered to be HW focused, meaning that it doesn't
>> really exercise the driver but rather an HW feature, it is placed in
>> tests/hw-tests.
> 
> Do we really want to keep this test at all? It's an interesting debate

This test has been around for a long time now so I think keeping it 
around would not be a problem, plus it actually gets fixed in this series.

-Antonio

> whether we want to show how trivial it is to subvert the kernel and HW
> (in some circumstances). > -Chris
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-12-15 19:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 12:58 [PATCH i-g-t 0/4] Create a new directory for hardware-targeting tests Petri Latvala
2017-12-13 12:58 ` [PATCH i-g-t 1/4] tests: Add a hw-tests subdirectory Petri Latvala
2017-12-13 12:58 ` [PATCH i-g-t 2/4] tests: Move gem_bad_address to hw-tests Petri Latvala
2017-12-13 13:26   ` Chris Wilson
2017-12-15 19:43     ` Antonio Argenziano [this message]
2017-12-13 12:58 ` [PATCH i-g-t 3/4] hw-tests: Fix and update gem_bad_address Petri Latvala
2017-12-15 20:46   ` Chris Wilson
2017-12-13 12:58 ` [PATCH i-g-t 4/4] run-tests.sh: Allow users to override IGT_TEST_ROOT Petri Latvala
2017-12-13 16:04   ` Arkadiusz Hiler
2017-12-13 16:41 ` ✓ Fi.CI.BAT: success for Create a new directory for hardware-targeting tests Patchwork
2017-12-13 18:31 ` ✓ 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=0da39cba-3838-7802-d8ba-0852f6313b57@intel.com \
    --to=antonio.argenziano@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --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