From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: reduce default drm vblank off delay to 50ms
Date: Tue, 30 Oct 2012 12:28:48 -0700 [thread overview]
Message-ID: <20121030122848.1cb10f06@jbarnes-desktop> (raw)
In-Reply-To: <CAKMK7uF_R0zYS0YmgGCT6zC8UN4YhCmP1S8uuWwS94spq77tHA@mail.gmail.com>
On Tue, 30 Oct 2012 20:20:44 +0100
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
>
> Nacked-by: Daniel Vetter <daniel@ffwll.ch>
>
> Also discussed with Jesse on irc, we've had fun ;-)
That's ridiculous. Just because we have a race we can't fix wrt
reading hw regs, doesn't mean we can't reduce the timeout.
I nack your nack.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-10-30 19:28 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 [this message]
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
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=20121030122848.1cb10f06@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).