All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 7/7] drm/i915: add i915_get_reset_stats_ioctl
Date: Wed, 3 Jul 2013 15:00:39 -0700	[thread overview]
Message-ID: <20130703220039.GF5488@bwidawsk.net> (raw)
In-Reply-To: <CAKMK7uG1GVJ+nf7M=w62okSjrx6qLV8RPovtYi_RuoPvvYGEWg@mail.gmail.com>

On Wed, Jul 03, 2013 at 11:58:31PM +0200, Daniel Vetter wrote:
> On Wed, Jul 3, 2013 at 11:44 PM, Ben Widawsky <ben@bwidawsk.net> wrote:
> > Yes. It won't be a requirement for mesa to know, but since I want to
> > kill aliasing ppgtt as much as possible, I intend to update getparam to
> > both set 0 to aliasing, and a new one for ppgtt.
> 
> We use that one essentially to decide whether the hw uses ppgtt or
> not, aliasing kinda doesn't matter. So to keep api I guess we need to
> keep that one enabled. Although only i-g-t really cares I think, but
> keeping it working would still be nice. Maybe just add a comment to
> the #define explaining what's going on?
> -Daniel

It's a bit off topic for this series, but I don't see any reason to keep
it working. If it doesn't end up being too much trouble, I can - but in
actuality on the kernel would be able to use it. Exposing the param as
true to user space would be a lie.

I was planning to update the IGT tests to support both things FWIW.

> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2013-07-03 22:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 14:22 [PATCH 0/7] Hangcheck and arb robustness Mika Kuoppala
2013-07-03 14:22 ` [PATCH 1/7] drm/i915: Fix retrieval of hangcheck stats Mika Kuoppala
2013-07-03 14:22 ` [PATCH 2/7] drm/i915: Replace open-coding of DEFAULT_CONTEXT_ID Mika Kuoppala
2013-07-03 14:22 ` [PATCH 3/7] drm/i915: introduce i915_queue_hangcheck Mika Kuoppala
2013-07-03 14:22 ` [PATCH 4/7] drm/i915: no hangcheck when reset is in progress Mika Kuoppala
2013-07-16  8:45   ` Daniel Vetter
2013-07-03 14:22 ` [PATCH 5/7] drm/i915: queue hangcheck on reset Mika Kuoppala
2013-07-16  8:49   ` Daniel Vetter
2013-07-16  9:16     ` Chris Wilson
2013-07-03 14:22 ` [PATCH 6/7] drm/i915: add i915_reset_count Mika Kuoppala
2013-07-03 14:22 ` [PATCH 7/7] drm/i915: add i915_get_reset_stats_ioctl Mika Kuoppala
2013-07-03 15:14   ` Chris Wilson
2013-07-03 21:23     ` Ben Widawsky
2013-07-03 21:41       ` Chris Wilson
2013-07-03 21:44         ` Ben Widawsky
2013-07-03 21:58           ` Daniel Vetter
2013-07-03 22:00             ` Ben Widawsky [this message]
2013-07-04  7:54               ` Ville Syrjälä
2013-07-04 16:39                 ` Ben Widawsky
2013-10-26  1:42   ` Ian Romanick
2013-10-27 12:30     ` Daniel Vetter
2013-10-29 22:29       ` Ian Romanick
2013-10-30  8:21         ` Daniel Vetter
2013-11-08  5:48           ` Dave Airlie
2013-11-08  6:32             ` Daniel Vetter
2013-11-08 17:21               ` Ian Romanick
2013-11-08 19:00                 ` Dave Airlie
2013-11-08 21:20                   ` Ian Romanick
2013-11-08 19:22               ` Jesse Barnes

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=20130703220039.GF5488@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=daniel.vetter@ffwll.ch \
    --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.