public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 04/11] drm/i915: Add ioctl to set per-context parameters
Date: Wed, 07 Jan 2015 16:13:25 +0200	[thread overview]
Message-ID: <871tn665mi.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20150107131856.GJ10955@nuc-i3427.alporthouse.com>

Chris Wilson <chris@chris-wilson.co.uk> writes:

> On Wed, Jan 07, 2015 at 02:08:46PM +0100, Daniel Vetter wrote:
>> On Wed, Jan 07, 2015 at 01:57:04PM +0200, Mika Kuoppala wrote:
>> > Rodrigo Vivi <rodrigo.vivi@intel.com> writes:
>> > 
>> > > From: Chris Wilson <chris@chris-wilson.co.uk>
>> > >
>> > > Sometimes we wish to tweak how an individual context behaves. Since we
>> > > always create a context for every filp, this means that individual
>> > > processes can fine tune their behaviour even if they do not explicitly
>> > > create a context.
>> > >
>> > > The first example parameter here is to enable multi-process GPU testing,
>> > > but the interface should be able to cope with passing arbitrarily complex
>> > > parameters.
>> > >
>> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> > > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> > 
>> > Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
>> 
>> Do we have the igt for this already somewhere? I've merged the prep patch
>> meanwhile.
>
> I have a bunch of igt that use this for hangcheck races. Patches were
> posted around the same time and you were happy enough with them.

On top of those I have additional stuff for tests/gem_reset_stats.

-Mika
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-01-07 14:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-24 16:13 [PATCH 00/11] drm-intel-collector - update Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 01/11] drm/i915: Specify bsd rings through exec flag Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 02/11] drm/i915: add I915_PARAM_HAS_BSD2 to i915_getparam Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 03/11] drm/i915: Move the ban period onto the context Rodrigo Vivi
2015-01-07 11:07   ` Mika Kuoppala
2014-12-24 16:13 ` [PATCH 04/11] drm/i915: Add ioctl to set per-context parameters Rodrigo Vivi
2015-01-07 11:57   ` Mika Kuoppala
2015-01-07 13:08     ` Daniel Vetter
2015-01-07 13:18       ` Chris Wilson
2015-01-07 14:13         ` Mika Kuoppala [this message]
2015-01-07 14:21           ` [PATCH] tests/gem_reset_stats: add tests for ban period ioctl Mika Kuoppala
2015-01-07 14:21             ` Chris Wilson
2015-01-07 16:49               ` Daniel Vetter
2014-12-24 16:13 ` [PATCH 05/11] drm/i915: Put logical pipe_control emission into a helper Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 06/11] drm/i915: Add WaCsStallBeforeStateCacheInvalidate:bdw, chv to logical ring Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 07/11] drm/i915: Remove pinned check from madvise_ioctl Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 08/11] drm/i915: Extend GET_APERTURE ioctl to report available map space Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 09/11] drm/i915: Display current hangcheck status in debugfs Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 10/11] drm/i915/vlv: check port in infoframe_enabled v2 Rodrigo Vivi
2014-12-24 16:13 ` [PATCH 11/11] drm/i915: vlv: fix save/restore of GFX_MAX_REQ_COUNT reg Rodrigo Vivi

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=871tn665mi.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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