dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Stéphane Marchesin" <stephane.marchesin@gmail.com>
Cc: airlied@redhat.com,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm: reduce default drm vblank off delay to 50ms
Date: Wed, 2 Jul 2014 13:42:38 -0700	[thread overview]
Message-ID: <20140702134238.3370ef6b@jbarnes-desktop> (raw)
In-Reply-To: <CACP_E+Kc5dKt+Mrtp+kRMDa6UUHacT09UcR7GUVG4AAPT0QChQ@mail.gmail.com>

On Wed, 2 Jul 2014 13:35:19 -0700
Stéphane Marchesin <stephane.marchesin@gmail.com> wrote:

> On Tue, Oct 30, 2012 at 12:20 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Tue, Oct 30, 2012 at 8:09 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> >> People keep whining about this, but no one seems to send a patch.  This
> >> *ought* to be safe now that we've dealt with the hw races in Mario's
> >> updated code, and fixed the bugs we know about in VT switch, DPMS, and
> >> multi-head configuraions.
> >>
> >> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> >
> > Afaik the fundamental race of enabling the vblank is still there, so
> > this is just duct-tape. And our hw has the required registers (on
> > gen5+ at least) to close this race for real and abolish all "disable
> > vblank irq later to paper over races and smooth things out). Hence I
> > think we should dtrt and so
> 
> [digging an old thread]
> 
> So I'm looking at this machine where we can't get good PSR residency
> because the vblank_offdelay is so long. Therefore, I'm suddenly very
> interested in solving this issue :) Of course I can't seem to find
> logs of the fun IRC discussion you guys had, can you describe what the
> race is, and also what are the registers you're talking about?

Beyond that I don't see why this obvious and simple improvement should
be blocked on some other work.  Maybe it's a bit late now since Ville
may already have patches for what Daniel mentions above, but I still
find the nack to be totally misguided.

Dave, please just pick this up so everyone can benefit while we thrash
through an i915 fix (doubtless introducing some bugs) that lets us
disable immediately.

-- 
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2014-07-02 20:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 19:09 [PATCH] drm: reduce default drm vblank off delay to 50ms Jesse Barnes
2012-10-30 19:20 ` Daniel Vetter
2012-10-30 19:28   ` Jesse Barnes
2012-11-02  5:56     ` Mario Kleiner
2012-11-02 18:37       ` Jesse Barnes
2012-11-12  3:33         ` Mario Kleiner
2014-07-02 20:35   ` Stéphane Marchesin
2014-07-02 20:42     ` Jesse Barnes [this message]
2014-07-08 13:56       ` Daniel Vetter
2014-07-08 16:38         ` Jesse Barnes
2012-10-30 19:21 ` 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=20140702134238.3370ef6b@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=stephane.marchesin@gmail.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