From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PULL] drm-intel-next-fixes
Date: Tue, 11 Jul 2017 16:07:12 +0300 [thread overview]
Message-ID: <87d197p1fj.fsf@nikula.org> (raw)
Hi Dave, drm/i915 fixes for v4.13-rc1. Almost half of them for stable
kernels, the rest for issues in this merge window. Two batches of GVT
fixes, otherwise fixes all around.
BR,
Jani.
The following changes since commit bdbbf7d619d1fd2f1fa9eb529b7817e4faf73f5e:
drm/i915: Clear execbuf's vma backpointer upon release (2017-06-26 10:38:43 +0200)
are available in the git repository at:
git://anongit.freedesktop.org/git/drm-intel tags/drm-intel-next-fixes-2017-07-11
for you to fetch changes up to eafbc20701243d21989c9c9aff5e5d9488e1890a:
Merge tag 'gvt-fixes-2017-07-11' of https://github.com/01org/gvt-linux into drm-intel-next-fixes (2017-07-11 12:52:14 +0300)
----------------------------------------------------------------
drm/i915 fixes for v4.13-rc1
----------------------------------------------------------------
Changbin Du (1):
drm/i915/gvt: Make function dpy_reg_mmio_readx safe
Chris Wilson (2):
drm/i915: Avoid undefined behaviour of "u32 >> 32"
drm/i915/fbdev: Check for existence of ifbdev->vma before operations
Christophe JAILLET (1):
drm/i915: Fix an error checking test
Chuanxiao Dong (4):
drm/i915/gvt: Fix possible recursive locking issue
drm/i915/gvt: Fix inconsistent locks holding sequence
drm/i915/gvt: Revert "drm/i915/gvt: Fix possible recursive locking issue"
drm/i915/gvt: Use fence error from GVT request for workload status
Gabriel Krisman Bertazi (1):
drm/i915: reintroduce VLV/CHV PFI programming power domain workaround
Jani Nikula (2):
Merge tag 'gvt-fixes-2017-06-29' of https://github.com/01org/gvt-linux into drm-intel-next-fixes
Merge tag 'gvt-fixes-2017-07-11' of https://github.com/01org/gvt-linux into drm-intel-next-fixes
Maarten Lankhorst (1):
drm/i915: Make DP-MST connector info work
Navare, Manasi D (1):
drm/i915/cnl: Fix the CURSOR_COEFF_MASK used in DDI Vswing Programming
Ping Gao (1):
drm/i915/gvt: Audit the command buffer address
Rodrigo Vivi (1):
drm/i915/cfl: Fix Workarounds.
Ville Syrjälä (1):
drm/i915: Disable MSI for all pre-gen5
Weinan Li (1):
drm/i915/gvt: remove scheduler_mutex in per-engine workload_thread
Xiong Zhang (2):
drm/i915/gvt: Set initial PORT_CLK_SEL vreg for BDW
drm/i915/gvt: Don't read ADPA_CRT_HOTPLUG_MONITOR from host
Zhou, Wenjia (1):
drm/i915/gvt: Fix a memory leak in intel_gvt_init_gtt()
sagar.a.kamble@intel.com (1):
drm/i915: Hold RPM wakelock while initializing OA buffer
drivers/gpu/drm/i915/gvt/cmd_parser.c | 10 +++++++
drivers/gpu/drm/i915/gvt/display.c | 22 ++++++++++++++
drivers/gpu/drm/i915/gvt/gtt.c | 2 ++
drivers/gpu/drm/i915/gvt/handlers.c | 37 ++++++++++++-----------
drivers/gpu/drm/i915/gvt/kvmgt.c | 14 +++++----
drivers/gpu/drm/i915/gvt/scheduler.c | 28 ++++++++---------
drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
drivers/gpu/drm/i915/i915_drv.c | 8 +++--
drivers/gpu/drm/i915/i915_gem_execbuffer.c | 38 +++++++++++++++---------
drivers/gpu/drm/i915/i915_perf.c | 12 ++++----
drivers/gpu/drm/i915/i915_reg.h | 2 +-
drivers/gpu/drm/i915/intel_cdclk.c | 20 +++++++++++++
drivers/gpu/drm/i915/intel_engine_cs.c | 14 ++++-----
drivers/gpu/drm/i915/intel_fbdev.c | 11 +++----
drivers/gpu/drm/i915/selftests/i915_gem_dmabuf.c | 6 ++--
15 files changed, 148 insertions(+), 78 deletions(-)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2017-07-11 13:07 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 13:07 Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-19 8:30 [PULL] drm-intel-next-fixes Joonas Lahtinen
2024-01-11 10:51 Joonas Lahtinen
2023-11-08 14:04 Jani Nikula
2023-11-10 15:48 ` Daniel Vetter
2023-08-31 21:28 Rodrigo Vivi
2023-08-24 12:34 Rodrigo Vivi
2023-07-06 8:24 Tvrtko Ursulin
2023-06-29 10:02 Tvrtko Ursulin
2023-06-21 9:54 Tvrtko Ursulin
2023-05-04 13:01 Joonas Lahtinen
2023-04-27 11:23 Joonas Lahtinen
2023-04-20 8:12 Joonas Lahtinen
2023-04-13 12:12 Joonas Lahtinen
2023-04-13 18:47 ` Daniel Vetter
2023-02-27 10:17 Jani Nikula
2023-02-17 12:24 Jani Nikula
2022-12-15 20:36 Rodrigo Vivi
2022-12-01 16:40 Rodrigo Vivi
2022-10-13 12:56 Tvrtko Ursulin
2022-10-06 10:18 Tvrtko Ursulin
2022-09-29 14:26 Tvrtko Ursulin
2022-08-11 21:03 Rodrigo Vivi
2022-08-04 17:33 Rodrigo Vivi
2022-05-24 13:59 Jani Nikula
2022-03-24 8:44 Tvrtko Ursulin
2022-03-17 7:47 Joonas Lahtinen
2022-03-10 7:58 Joonas Lahtinen
2022-01-20 10:13 Tvrtko Ursulin
2022-01-13 9:33 Tvrtko Ursulin
2022-01-14 13:23 ` Daniel Vetter
2021-11-09 23:17 Rodrigo Vivi
2021-08-26 9:03 Jani Nikula
2021-07-07 15:09 Rodrigo Vivi
2021-06-29 18:54 Rodrigo Vivi
2021-06-30 10:05 ` Jani Nikula
2021-06-30 19:04 ` Rodrigo Vivi
2021-07-01 8:57 ` Jani Nikula
2021-02-25 14:43 Rodrigo Vivi
2021-02-18 22:46 Rodrigo Vivi
2020-12-18 15:04 Jani Nikula
2020-12-18 15:42 ` Daniel Vetter
2020-10-22 20:56 Rodrigo Vivi
2020-10-15 18:14 Rodrigo Vivi
2020-10-02 18:26 Rodrigo Vivi
2020-07-30 16:26 Joonas Lahtinen
2020-08-10 7:31 ` Dave Airlie
2020-08-12 12:49 ` Jani Nikula
2020-06-10 9:37 Joonas Lahtinen
2020-06-10 11:19 ` Joonas Lahtinen
2020-06-04 15:04 Joonas Lahtinen
2020-05-28 14:40 Joonas Lahtinen
2020-05-20 12:32 Joonas Lahtinen
2020-04-08 21:59 Rodrigo Vivi
2020-04-02 21:30 Rodrigo Vivi
2020-03-27 8:16 Rodrigo Vivi
2019-12-05 9:24 Joonas Lahtinen
2019-11-28 14:15 Joonas Lahtinen
2019-11-22 15:55 Joonas Lahtinen
2019-11-20 20:40 Joonas Lahtinen
2019-11-22 12:08 ` Joonas Lahtinen
2019-11-14 8:52 Joonas Lahtinen
2019-11-07 14:50 Joonas Lahtinen
2019-09-27 19:49 Rodrigo Vivi
2019-09-19 14:16 Rodrigo Vivi
2019-09-11 23:33 Rodrigo Vivi
2019-05-15 7:48 Joonas Lahtinen
2019-05-09 10:01 Joonas Lahtinen
2019-05-02 13:40 Joonas Lahtinen
2019-04-30 7:08 Joonas Lahtinen
2019-04-25 6:13 Joonas Lahtinen
2019-03-12 20:55 Rodrigo Vivi
2018-12-27 7:40 Jani Nikula
2018-10-25 13:18 Joonas Lahtinen
2018-10-19 10:37 Joonas Lahtinen
2018-10-19 12:34 ` Daniel Vetter
2018-10-18 16:57 Joonas Lahtinen
2018-10-18 19:32 ` Daniel Vetter
2018-10-19 6:59 ` Joonas Lahtinen
2018-10-19 7:05 ` Daniel Vetter
2018-10-19 9:41 ` Joonas Lahtinen
2018-10-04 13:37 Joonas Lahtinen
2018-08-24 21:48 Rodrigo Vivi
2018-08-16 19:03 Rodrigo Vivi
2018-08-06 23:30 Rodrigo Vivi
2018-04-19 9:30 Joonas Lahtinen
2018-03-27 14:58 Joonas Lahtinen
2018-03-22 14:35 Joonas Lahtinen
2018-02-07 20:44 Rodrigo Vivi
2018-02-02 0:45 Rodrigo Vivi
2017-11-23 9:34 Jani Nikula
2017-11-10 13:21 Jani Nikula
2017-06-27 8:28 Daniel Vetter
2017-02-17 9:46 Jani Nikula
2017-02-15 14:06 Jani Nikula
2016-12-22 10:22 Jani Nikula
2016-12-07 19:45 Jani Nikula
2016-10-11 14:09 Jani Nikula
2016-08-05 13:27 Jani Nikula
2016-07-25 6:41 Daniel Vetter
2016-05-25 8:57 Jani Nikula
2016-03-16 11:04 Jani Nikula
2016-01-14 20:06 Jani Nikula
2015-11-06 13:43 Jani Nikula
2015-10-22 8:28 Daniel Vetter
2015-09-02 11:49 Jani Nikula
2015-08-28 12:44 Jani Nikula
2015-08-16 18:13 Daniel Vetter
2015-07-02 11:26 Jani Nikula
2015-06-22 10:33 Jani Nikula
2015-06-18 6:04 Jani Nikula
2015-06-19 3:48 ` Dave Airlie
2015-06-19 15:24 ` Daniel Vetter
2015-06-22 7:59 ` Ander Conselvan De Oliveira
2015-06-22 8:12 ` Jani Nikula
2015-06-22 8:13 ` Dave Airlie
2015-06-11 8:40 Jani Nikula
2015-05-29 17:39 Daniel Vetter
2015-04-24 21:46 Jani Nikula
2015-04-15 12:21 Jani Nikula
2015-02-11 11:09 Jani Nikula
2015-02-11 11:48 ` Daniel Vetter
2014-12-30 12:47 Jani Nikula
2014-12-17 12:16 Jani Nikula
2014-12-11 13:43 Jani Nikula
2014-12-04 9:56 Daniel Vetter
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=87d197p1fj.fsf@nikula.org \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).