From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Stop CRC gathering when the ctl file is closed
Date: Mon, 21 Oct 2013 19:32:36 +0300 [thread overview]
Message-ID: <20131021163236.GB13047@intel.com> (raw)
In-Reply-To: <CAKMK7uGd9pSSr4Pfis9_tqE1PtHfuTw+46pvVX4FjZOZS8+wbg@mail.gmail.com>
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älä <ville.syrjala@linux.intel.com>
> >
> > If no one is looking at the CRCs, stop gathering them.
> >
> > Signed-off-by: Ville Syrjälä <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älä
Intel OTC
prev parent reply other threads:[~2013-10-21 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 16:01 [PATCH] drm/i915: Stop CRC gathering when the ctl file is closed ville.syrjala
2013-10-21 16:17 ` Daniel Vetter
2013-10-21 16:32 ` Ville Syrjälä [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=20131021163236.GB13047@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox