From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/9] drm: More vblank on/off work
Date: Thu, 26 Jun 2014 09:32:48 -0700 [thread overview]
Message-ID: <20140626093248.68d2bf5a@jbarnes-desktop> (raw)
In-Reply-To: <1401104792-26560-1-git-send-email-ville.syrjala@linux.intel.com>
On Mon, 26 May 2014 14:46:23 +0300
ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Another vblank series with the following features:
> - Plug a race between drm_vblank_off() and marking the crtc inactive
> - Don't send zeroed vblank evens to userspace at drm_vblank_off()
> - Have the user visible vblank counter account the entire time
> when the crtc was active, regardless of how long vblank interrupts
> were enabled
> - Avoid random jumps in the user visible vblank counter if the hardware
> counter gets reset
> - Allow disabling vblank interrupts immediately at drm_vblank_put()
> - Some polish via coccinelle
>
> While setting drm_vblank_offdelay to 0 is now possible, I'm not sure
> if we should set it 0 automatically in the i915 driver. If there are
> multiple GPUs in the system that setting will affect them all, which
> might have bad consequences if the other GPU doesn't have a hardware
> frame counter, or if it's just buggy. So perhaps we should move that
> option to be per-driver?
>
> Ville Syrjälä (9):
> drm: Always reject drm_vblank_get() after drm_vblank_off()
> drm/i915: Warn if drm_vblank_get() still works after drm_vblank_off()
> drm: Don't clear vblank timestamps when vblank interrupt is disabled
> drm: Move drm_update_vblank_count()
> drm: Have the vblank counter account for the time between vblank irq
> disable and drm_vblank_off()
> drm: Avoid random vblank counter jumps if the hardware counter has
> been reset
> drm: Disable vblank interrupt immediately when drm_vblank_offdelay==0
> drm: Reduce the amount of dev->vblank[crtc] in the code
> drm/i915: Leave interrupts enabled while disabling crtcs during
> suspend
Here's one that may be fixed by this series, needs testing though:
https://bugs.freedesktop.org/show_bug.cgi?id=79054
--
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-06-26 16:32 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 11:46 [PATCH 0/9] drm: More vblank on/off work ville.syrjala
2014-05-26 11:46 ` [PATCH 1/9] drm: Always reject drm_vblank_get() after drm_vblank_off() ville.syrjala
2014-05-26 13:21 ` Daniel Vetter
2014-05-26 13:32 ` Ville Syrjälä
2014-05-26 13:47 ` Daniel Vetter
2014-05-26 11:46 ` [PATCH 2/9] drm/i915: Warn if drm_vblank_get() still works " ville.syrjala
2014-05-26 13:22 ` Daniel Vetter
2014-05-26 13:36 ` Ville Syrjälä
2014-05-26 13:48 ` Daniel Vetter
2014-05-26 13:49 ` [PATCH v2 " ville.syrjala
2014-05-26 13:54 ` Daniel Vetter
2014-05-26 11:46 ` [PATCH 3/9] drm: Don't clear vblank timestamps when vblank interrupt is disabled ville.syrjala
2014-05-26 13:24 ` Daniel Vetter
2014-05-26 11:46 ` [PATCH 4/9] drm: Move drm_update_vblank_count() ville.syrjala
2014-05-26 11:46 ` [PATCH 5/9] drm: Have the vblank counter account for the time between vblank irq disable and drm_vblank_off() ville.syrjala
2014-05-26 13:27 ` Daniel Vetter
2014-05-26 11:46 ` [PATCH 6/9] drm: Avoid random vblank counter jumps if the hardware counter has been reset ville.syrjala
2014-05-26 13:28 ` Daniel Vetter
2014-05-26 11:46 ` [PATCH 7/9] drm: Disable vblank interrupt immediately when drm_vblank_offdelay==0 ville.syrjala
2014-05-26 13:02 ` [Intel-gfx] " Daniel Vetter
2014-05-26 14:26 ` [PATCH 10/9] drm: Add dev->vblank_disable_immediate flag ville.syrjala
2014-05-26 14:26 ` [PATCH 11/9] drm/i915: Opt out of vblank disable timer on >gen2 ville.syrjala
2014-05-26 15:31 ` Daniel Vetter
2014-05-26 19:27 ` Daniel Vetter
2015-11-19 19:44 ` [Intel-gfx] " Paulo Zanoni
2015-11-19 20:06 ` Ville Syrjälä
2015-11-19 20:35 ` Paulo Zanoni
2015-11-19 20:53 ` Ville Syrjälä
2015-11-19 21:15 ` Ville Syrjälä
2015-11-19 21:27 ` [Intel-gfx] " Chris Wilson
2014-06-20 0:41 ` [PATCH 10/9] drm: Add dev->vblank_disable_immediate flag Matt Roper
2014-07-29 17:31 ` [Intel-gfx] " Ville Syrjälä
2014-07-29 17:57 ` Daniel Vetter
2014-05-26 16:06 ` [PATCH v2 1/9] drm: Always reject drm_vblank_get() after drm_vblank_off() ville.syrjala
2014-05-26 11:46 ` [PATCH 8/9] drm: Reduce the amount of dev->vblank[crtc] in the code ville.syrjala
2014-05-26 13:31 ` Daniel Vetter
2014-05-26 11:46 ` [PATCH v2 9/9] drm/i915: Leave interrupts enabled while disabling crtcs during suspend ville.syrjala
2014-05-26 15:49 ` Daniel Vetter
2014-06-20 18:10 ` Matt Roper
2014-06-02 8:15 ` [PATCH 12/9] drm: Fix deadlock between event_lock and vbl_lock/vblank_time_lock ville.syrjala
2014-06-02 8:15 ` [PATCH 13/9] drm: Fix race between drm_vblank_off() and drm_queue_vblank_event() ville.syrjala
2014-06-02 8:15 ` [PATCH 14/9] drm: Kick start vblank interrupts at drm_vblank_on() ville.syrjala
2014-06-20 18:29 ` Matt Roper
2014-06-26 16:32 ` Jesse Barnes [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=20140626093248.68d2bf5a@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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