From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH] drm/i915: Stop CRC gathering when the ctl
 file is closed
Date: Mon, 21 Oct 2013 19:32:36 +0300
Message-ID: <20131021163236.GB13047@intel.com>
References: <1382371267-9116-1-git-send-email-ville.syrjala@linux.intel.com>
	<CAKMK7uGd9pSSr4Pfis9_tqE1PtHfuTw+46pvVX4FjZOZS8+wbg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
	by gabe.freedesktop.org (Postfix) with ESMTP id 9F057E7143
	for <intel-gfx@lists.freedesktop.org>;
	Mon, 21 Oct 2013 09:32:39 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <CAKMK7uGd9pSSr4Pfis9_tqE1PtHfuTw+46pvVX4FjZOZS8+wbg@mail.gmail.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On Mon, Oct 21, 2013 at 06:17:30PM +0200, Daniel Vetter wrote:
> On Mon, Oct 21, 2013 at 6:01 PM,  <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrj=E4l=E4 <ville.syrjala@linux.intel.com>
> >
> > If no one is looking at the CRCs, stop gathering them.
> >
> > Signed-off-by: Ville Syrj=E4l=E4 <ville.syrjala@linux.intel.com>
> =

> As discussed on irc this prevents fools like me from wreaking havoc
> directly with the cli, at least if you still want to interactively
> test stuff easily (background processes and all would work around
> this). Imo it's better to disable (and maybe re-enable) the CRC stuff
> when we disable/enable the pipe.

I would still suggest using exec for keeping the file open.

Especially if we go for the auto re-enable, since then we'd
essientially never turn off the crc capture once it's started
unless someone explicitly writes to the ctl file. We'd just pause
it while the pipe is off.

Also I would assume we want to avoid full modesets in the future
if possible, so relying on that doesn't feel very robust to me.

-- =

Ville Syrj=E4l=E4
Intel OTC