From: Ismael Luceno <ismael@iodev.co.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Fix screen flickering on X
Date: Thu, 7 May 2015 18:23:02 -0300 [thread overview]
Message-ID: <20150507182302.4534634d@pirotess> (raw)
In-Reply-To: <20150507141827.GW22099@nuc-i3427.alporthouse.com>
On Thu, 7 May 2015 15:18:27 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Thu, May 07, 2015 at 04:41:48PM +0300, Jani Nikula wrote:
> > On Thu, 07 May 2015, Matt Roper <matthew.d.roper@intel.com> wrote:
> > > On Thu, May 07, 2015 at 12:12:18PM +0300, Jani Nikula wrote:
> > >> On Thu, 23 Apr 2015, Chris Wilson <chris@chris-wilson.co.uk>
> > >> wrote:
> > >> > [cc'ing the authors]
> > >>
> > >> This has been posted earlier [1] and it has review to be
> > >> addressed [2].
> > >>
> > >> BR,
> > >> Jani.
> > >
> > > I agree with Ander's response in [2]...we can't call
> > > intel_update_watermarks() in the commit function because we're
> > > under vblank evasion. We should already be flagging the
> > > transaction as needing a watermark update in
> > > intel_check_cursor_plane(), and that flag will be acted upon
> > > immediately after the commit functions are done running, once
> > > we've re-enabled interrupts.
> > >
> > > Note that our current codebase looks a bit different since we've
> > > dropped intel_crtc->cursor_{width,height}. So the relevant check
> > > in intel_check_cursor_plane() now looks like:
> > >
> > > if (plane->state->crtc_w != state->base.crtc_w)
> > > intel_crtc->atomic.update_wm = true;
> > >
> > > Is there a bugzilla open on this issue with more details?
> >
> > Not that I know of. Ismael?
> >
>
> Probably:
> https://bugs.freedesktop.org/show_bug.cgi?id=88944
> https://bugzilla.redhat.com/show_bug.cgi?id=1199890
> are related.
> -Chris
>
I am experiencing neither of those things.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Ismael Luceno <ismael@iodev.co.uk>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix screen flickering on X
Date: Thu, 7 May 2015 18:23:02 -0300 [thread overview]
Message-ID: <20150507182302.4534634d@pirotess> (raw)
In-Reply-To: <20150507141827.GW22099@nuc-i3427.alporthouse.com>
On Thu, 7 May 2015 15:18:27 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Thu, May 07, 2015 at 04:41:48PM +0300, Jani Nikula wrote:
> > On Thu, 07 May 2015, Matt Roper <matthew.d.roper@intel.com> wrote:
> > > On Thu, May 07, 2015 at 12:12:18PM +0300, Jani Nikula wrote:
> > >> On Thu, 23 Apr 2015, Chris Wilson <chris@chris-wilson.co.uk>
> > >> wrote:
> > >> > [cc'ing the authors]
> > >>
> > >> This has been posted earlier [1] and it has review to be
> > >> addressed [2].
> > >>
> > >> BR,
> > >> Jani.
> > >
> > > I agree with Ander's response in [2]...we can't call
> > > intel_update_watermarks() in the commit function because we're
> > > under vblank evasion. We should already be flagging the
> > > transaction as needing a watermark update in
> > > intel_check_cursor_plane(), and that flag will be acted upon
> > > immediately after the commit functions are done running, once
> > > we've re-enabled interrupts.
> > >
> > > Note that our current codebase looks a bit different since we've
> > > dropped intel_crtc->cursor_{width,height}. So the relevant check
> > > in intel_check_cursor_plane() now looks like:
> > >
> > > if (plane->state->crtc_w != state->base.crtc_w)
> > > intel_crtc->atomic.update_wm = true;
> > >
> > > Is there a bugzilla open on this issue with more details?
> >
> > Not that I know of. Ismael?
> >
>
> Probably:
> https://bugs.freedesktop.org/show_bug.cgi?id=88944
> https://bugzilla.redhat.com/show_bug.cgi?id=1199890
> are related.
> -Chris
>
I am experiencing neither of those things.
next prev parent reply other threads:[~2015-05-07 21:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 22:40 [PATCH] drm/i915: Fix screen flickering on X Ismael Luceno
2015-04-23 9:15 ` Chris Wilson
2015-04-23 9:15 ` Chris Wilson
2015-05-07 9:12 ` Jani Nikula
2015-05-07 9:12 ` [Intel-gfx] " Jani Nikula
2015-05-07 13:27 ` Matt Roper
2015-05-07 13:27 ` [Intel-gfx] " Matt Roper
2015-05-07 13:41 ` Jani Nikula
2015-05-07 13:41 ` [Intel-gfx] " Jani Nikula
2015-05-07 14:18 ` Chris Wilson
2015-05-07 21:23 ` Ismael Luceno [this message]
2015-05-07 21:23 ` Ismael Luceno
2015-05-08 15:10 ` Ismael Luceno
2015-05-08 15:10 ` [Intel-gfx] " Ismael Luceno
2015-05-08 15:16 ` Ismael Luceno
2015-05-08 15:16 ` [Intel-gfx] " Ismael Luceno
-- strict thread matches above, loose matches on Subject: below --
2015-04-11 22:17 Ismael Luceno
2015-04-13 12:33 ` Ander Conselvan De Oliveira
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=20150507182302.4534634d@pirotess \
--to=ismael@iodev.co.uk \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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.