Hi Dave & Daniel,
Here comes the final feature PR for 5.16.
As the biggest thing it adds multi-LRC (parallel) submission
implementation for GuC and a simplified parallel submission uAPI
to go with that (only works with GuC for now). It is has a similar
mission to the bonded submission uAPI, take
sion teardown
drm/i915/pxp: Implement PXP irq handler
drm/i915/pxp: Enable PXP power management
Jani Nikula (1):
drm/i915/pci: rename functions to have i915_pci prefix
Janusz Krzysztofik (2):
drm/i915: Mark GPU wedging on driver unregister unrecoverable
drm/i915: Fl
Quoting Peter Zijlstra (2021-09-17 16:13:19)
> On Thu, Sep 16, 2021 at 03:28:11PM +0200, Peter Zijlstra wrote:
> > On Thu, Sep 16, 2021 at 03:00:39PM +0200, Maarten Lankhorst wrote:
> >
> > > > For merge logistics, can we pls have a stable branch? I expect that the
> > > > i915 patches will be rea
Quoting Nathan Chancellor (2021-08-23 22:08:37)
> Ping? This is a pretty clear bug and it is not fixed in -next or
> drm-intel at this point.
Pushed to drm-intel-gt-next with my R-b.
Regards, Joonas
> On Fri, Aug 13, 2021 at 10:11:58AM -0700, Nathan Chancellor wrote:
> > Clang warns:
> >
> > In
Quoting Zhenyu Wang (2021-08-19 11:29:29)
> On 2021.08.17 13:22:03 +0800, Zhenyu Wang wrote:
> > > On 2021.08.16 19:34:58 +0200, Christoph Hellwig wrote:
> > > > Any updates on this? I'd really hate to miss this merge window.
> > >
> > > I'm still waiting for our validation team's report on this.
Quoting Dave Airlie (2021-08-11 06:48:39)
> dim: db47fe727e1f ("drm/i915/step:
> s/_revid_tbl/_revids"): committer Signed-off-by
> missing.
>
> I'm not sure how much pain it is to fix that up, but
> commit db47fe727e1fc516cf60fc9ab8299605ef3c2d54
> Author: Anusha Srivatsa
> Commit: Matt Roper
>
+ Dave as FYI
Quoting Daniel Vetter (2021-08-10 09:27:25)
> On Mon, Aug 09, 2021 at 09:19:39AM -0700, Matt Roper wrote:
> > On Mon, Aug 09, 2021 at 04:05:59PM +0200, Daniel Vetter wrote:
> > > On Fri, Aug 06, 2021 at 09:36:56AM +0300, Joonas Lahtinen wrot
Quoting Christoph Hellwig (2021-07-21 18:53:38)
> Instead of having an option to build the gvt code into the main i915
> module, just move it into the kvmgt.ko module. This only requires
> a new struct with three entries that the main i915 module needs to
> request before enabling VGPU passthrough
Quoting Joonas Lahtinen (2021-08-06 13:06:17)
> Hi Dave & Daniel,
>
> Sorry for the big PR in advance. Had the summer vacations and did not
> notice until tool late how many patches were in already before leaving.
>
> As requested, there is a lot of refactoring to i
drm/i915/guc: Connect reset modparam updates to GuC policy flags
drm/i915/guc: Include scheduling policies in the debugfs state dump
drm/i915/guc: Add golden context to GuC ADS
drm/i915/selftest: Better error reporting from hangcheck selftest
drm/i915/selftest: Fix hang
Hi Matt,
Always use the dim tooling when applying patches, it will do the right
thing with regards to adding the S-o-b.
Regards, Joonas
Quoting Stephen Rothwell (2021-07-15 07:18:54)
> Hi all,
>
> Commit
>
> db47fe727e1f ("drm/i915/step: s/_revid_tbl/_revids")
>
> is missing a Signed-off-by
t;
> and the specific change that was blocked around tracepoints:
>
> https://lwn.net/Articles/442113/
>
> Anyway to make it a notch clearer why we have this Kconfig option
> consistly add the "Recommended for driver developers only." to it and
> all the other debug o
Hi Joel,
That seems like a genuine bug. Could you file it at the i915 bug tracker
with all the requested information to make sure we can take a look at
it:
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
Are you able to try different kernel versions to bisect which kernel
Quoting Joonas Lahtinen (2021-06-11 14:13:02)
> Quoting Joonas Lahtinen (2021-06-11 13:40:56)
> > Quoting Maarten Lankhorst (2021-06-11 12:27:15)
> > > Pull request for drm-misc-next and drm-intel-gt-next.
> > >
> > > topic/i915-ttm-2021-06-11:
> > >
Quoting Thomas Zimmermann (2021-06-13 21:54:03)
> Hi Joonas
>
> Am 11.06.21 um 13:13 schrieb Joonas Lahtinen:
> > Quoting Joonas Lahtinen (2021-06-11 13:40:56)
> >> Quoting Maarten Lankhorst (2021-06-11 12:27:15)
> >>> Pull request for drm-misc-next and drm-i
Quoting Joonas Lahtinen (2021-06-11 13:40:56)
> Quoting Maarten Lankhorst (2021-06-11 12:27:15)
> > Pull request for drm-misc-next and drm-intel-gt-next.
> >
> > topic/i915-ttm-2021-06-11:
> > drm-misc and drm-intel pull request for topic/i915-ttm:
> > -
Quoting Maarten Lankhorst (2021-06-11 12:27:15)
> Pull request for drm-misc-next and drm-intel-gt-next.
>
> topic/i915-ttm-2021-06-11:
> drm-misc and drm-intel pull request for topic/i915-ttm:
> - Convert i915 lmem handling to ttm.
> - Add a patch to temporarily add a driver_private member to vma_
(Address for Hans was corrupt in previous message, which confused my mail
client. Sorry for duplicate message, the other is without From: field).
+ Jesse
Quoting Colin Ian King (2021-06-09 14:50:07)
> Hi,
>
> I was reviewing some old unassigned variable warnings from static
> analysis by Coverit
+ Jesse
Quoting Colin Ian King (2021-06-09 14:50:07)
> Hi,
>
> I was reviewing some old unassigned variable warnings from static
> analysis by Coverity and found an issue introduced with the following
> commit:
>
> commit aa7ffc01d254c91a36bf854d57a14049c6134c72
> Author: Jesse Barnes
> Date:
only the user interrupt when using GuC submission
drm/i915/guc: Use guc_class instead of engine_class in fw interface
John Harrison (1):
drm/i915/uc: Use platform specific defaults for GuC/HuC enabling
Joonas Lahtinen (1):
Merge drm/drm-next into drm-intel-gt-next
Lucas De
+ Tvrtko to take a look
Quoting Konrad Rzeszutek Wilk (2021-05-20 18:12:58)
> On Mon, May 10, 2021 at 05:25:25PM +0200, Christoph Hellwig wrote:
> > Hi all,
> >
> > swiotlb_max_segment is a rather strange "API" export by swiotlb.c,
> > and i915 is the only (remaining) user.
> >
> > swiotlb_max_s
Quoting Joonas Lahtinen (2021-05-28 10:25:57)
> Hi Dave & Daniel,
>
> Here's drm-intel-gt-next pull request.
>
> Most notably it has the reworked DG1 uAPI (behind CONFIG_BROKEN)
> as requested. Important fix for Gitlab issues #3293 and #3450 and
> one anot
ename pm_ prefixed functions names
Janusz Krzysztofik (1):
drm/i915/gt: Do release kernel context if breadcrumb measure fails
Joonas Lahtinen (1):
Merge tag 'topic/intel-gen-to-ver-2021-04-19' of
git://anongit.freedesktop.org/drm/drm-intel into drm-intel-gt-next
José
Quoting Jani Nikula (2021-04-19 12:53:11)
>
> Hi Joonas and Rodrigo -
>
> Here's the gen to ver conversion topic branch to be merged to both
> drm-intel-next and drm-intel-gt-next.
Pulled.
Regards, Joonas
> Lots of Cc's for heads up.
>
>
> BR,
> Jani.
>
>
> topic/intel-gen-to-ver-2021-04-1
Hi Dave & Daniel,
Bit late PR due to Easter break.
Prep work for local memory support as requested. Hard hang
fix for Sandybridge. Sanitize dma-buf size on import and
avoid GPU reset if heartbeat callback runs before timeout.
The rest is mostly small fixes and code/checkpatch cleanups.
Regards
Quoting Brian Welty (2021-01-26 23:46:24)
> Single control below is added to DRM cgroup controller in order to track
> user execution time for GPU devices. It is up to device drivers to
> charge execution time to the cgroup via drm_cgroup_try_charge().
>
> sched.runtime
> Read-only value,
g
drm/i915/gt: Do not suspend bonded requests if one hangs
drm/i915/gt: Skip over completed active execlists, again
drm/i915/gvt: Add missing forward decl of intel_vgpu for HDRTEST
John Harrison (1):
drm/i915/uc: Add function to define defaults for GuC/HuC enable
Hi Dave & Daniel,
Here is the first PR for v5.12. There are quite a few patches
accumulated after the holidays as usual:
Most importantly there are fixes to the clear residual security
mitigations to avoid GPU hangs caused by them. Further there is
option to allow the user to decide to disable su
+ Tvrtko and Chris for comments
Code seems to be added in:
commit 0cd4684d6ea9a4ffec33fc19de4dd667bb90d0a5
Author: Tvrtko Ursulin
Date: Tue Nov 21 18:18:50 2017 +
drm/i915/pmu: Add interrupt count metric
I think later in the thread there was a suggestion to replace this with
simple c
Quoting Thomas Zimmermann (2020-11-24 13:38:16)
> Using struct drm_device.pdev is deprecated. Convert i915 to struct
> drm_device.dev. No functional changes.
>
> Signed-off-by: Thomas Zimmermann
> Cc: Jani Nikula
> Cc: Joonas Lahtinen
> Cc: Rodrigo Vivi
Any chance of
Hi Dave & Daniel,
Here goes the drm-intel-gt-next PR for 5.11.
Most importantly there is a healthy chunk of Tigerlake
related fixes and a fix for user reported issue #2381 where
graphics output would stop at "switching to inteldrmfb from
simple".
Fixes to DMA mapped sg usage in i915 to unblock i
+ Lionel
Can you please take a look at best resolving the below problem.
Maybe we should eliminate the duplicate declarations? Updating such
a list manually seems error prone to me.
Regards, Joonas
Quoting Mauro Carvalho Chehab (2020-10-13 14:53:59)
> As reported by Sphinx:
>
> ./Docum
Quoting Daniel Vetter (2020-10-01 18:13:26)
> On Thu, Oct 1, 2020 at 5:08 PM Jani Nikula
> wrote:
> >
> > On Thu, 01 Oct 2020, Daniel Vetter wrote:
> > > On Thu, Oct 1, 2020 at 3:53 PM Christoph Hellwig wrote:
> > >>
> > >> On Thu, Oct 01, 2020 at 08:39:17PM +1000, Stephen Rothwell wrote:
> > >
Quoting paul...@kernel.org (2020-09-29 02:30:58)
> From: Thomas Gleixner
>
> CONFIG_PREEMPT_COUNT is now unconditionally enabled and will be
> removed. Cleanup the leftovers before doing so.
Change looks fine:
Reviewed-by: Joonas Lahtinen
Are you looking for us to merge or m
Quoting Christoph Hellwig (2020-09-28 15:37:41)
> On Mon, Sep 28, 2020 at 01:13:38PM +0300, Joonas Lahtinen wrote:
> > I think we have a gap that after splitting the drm-intel-next pull requests
> > into
> > two the drm-intel/for-linux-next branch is now missing material f
+ Dave and Daniel
+ Stephen
Quoting Christoph Hellwig (2020-09-26 09:29:59)
> On Fri, Sep 25, 2020 at 07:43:49PM -0700, Andrew Morton wrote:
> > On Thu, 24 Sep 2020 15:58:42 +0200 Christoph Hellwig wrote:
> >
> > > this series removes alloc_vm_area, which was left over from the big
> > > vmalloc
Hi Dave & Daniel,
Exactly same content as previous PR:
https://lists.freedesktop.org/archives/intel-gfx/2020-September/247626.html
Just rebased adding the missing S-o-b:s and updated "Fixes:" tags accordingly
as requested.
Regards, Joonas
***
drm-intel-gt-next-2020-09-07:
(Same content as dr
Hi Dave & Daniel,
Here goes the GT pull request for v5.10. It's the same patches as
previously at "topic/drm-intel-gem-next", one dropped and a few
re-ordered while creating the "drm-intel-gt-next" branch. So the
patches have been part of drm-tip already for weeks.
More about the PR itself at the
Hi Dave & Daniel,
(Covering for Jani here for drm-intel-next-fixes)
5 new commits over drm-intel-next here.
Fix for KASAN detected race condition and linux-next scheduler
WARNs. Patch to avoid IRQ spinlock and Cc: stable PMU refcount
update.
CI machinery needed some kicking, so results didn't a
Hi Dave & Daniel,
-rc1 required the usual juggling to get baseline from CI.
Needed to temporarily apply this fixup to drm-intel-fixes:
"ext4: mballoc: Use this_cpu_read instead of this_cpu_ptr"
For display side, fix for TypeC interrupt storm detection. Fixes to
TypeC, DDI and MST hardware registe
Quoting Stephen Rothwell (2020-06-16 02:39:12)
> Hi all,
>
> After merging the drm-intel-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from drivers/gpu/drm/i915/gt/intel_lrc.c:5972:
> drivers/gpu/drm/i915/gt/selftest_lrc.c: In function
> 'liv
Quoting Joonas Lahtinen (2020-06-10 12:37:00)
> Hi Dave & Daniel,
>
> Sending this one early for it to hopefully make it in before -rc1.
>
> Two important fixes: OOPS fix that was missing "Fixes:" tag and
> not picked up earlier. Also fix for a use-after-free in
Hi Dave & Daniel,
Sending this one early for it to hopefully make it in before -rc1.
Two important fixes: OOPS fix that was missing "Fixes:" tag and
not picked up earlier. Also fix for a use-after-free in cmdparser.
Additional fixup to module param types.
Regards, Joonas
***
drm-intel-next-fi
drm/i915/params: fix i915.fake_lmem_start module param sysfs permissions
Joonas Lahtinen (1):
Merge tag 'gvt-next-fixes-2020-05-28' of
https://github.com/intel/gvt-linux into drm-intel-next-fixes
Nathan Chancellor (1):
drm/i915: Mark check_shadow_context_ppgtt as maybe
Hi Dave & Daniel,
Two bigger fixes to corner case kernel access faults
and three workload scheduling fixups this week.
CI_DINF_191 at:
https://intel-gfx-ci.01.org/tree/drm-intel-next-fixes/combined-alt.html?
I got gvt-next-fixes pull today, I'll pull it next week so it
has time to run through CI
ompute routine on PSR
Imre Deak (2):
drm/i915/tgl+: Fix interrupt handling for DP AUX transactions
drm/i915: Fix AUX power domain toggling across TypeC mode resets
Joonas Lahtinen (3):
Merge tag 'gvt-next-2020-05-12' of https://github.com/intel/gvt-linux
into drm-intel
drm/i915: Stop sending DP SDPs on ddi disable
drm/i915/dp: Add compute routine for DP PSR VSC SDP
drm/i915/psr: Use new DP VSC SDP compute routine on PSR
Imre Deak (1):
drm/i915/tgl+: Fix interrupt handling for DP AUX transactions
Joonas Lahtinen (3):
Merge tag 'gvt-
Quoting Dave Airlie (2020-05-14 04:28:17)
> On Thu, 14 May 2020 at 03:10, Joonas Lahtinen
> wrote:
> >
> > Ping for merging this? If there are no issues, I'd prefer to pull in
> > next gvt-next and tag the final pull sooner than later.
>
> Can you check
Ping for merging this? If there are no issues, I'd prefer to pull in
next gvt-next and tag the final pull sooner than later.
Regards, Joonas
Quoting Joonas Lahtinen (2020-04-30 15:49:04)
> Hi Dave & Daniel,
>
> Fix for performance regression GitLab #1698: Iris Plus 655 and
&g
Quoting Dave Airlie (2020-05-07 21:27:27)
> On Fri, 8 May 2020 at 01:44, Chris Wilson wrote:
> >
> > Quoting Jason Ekstrand (2020-05-07 16:36:00)
> > > The Vulkan driver in Mesa for Intel hardware never uses relocations if
> > > it's running on a version of i915 that supports at least softpin whic
drm/i915/audio: error log non-zero audio power refcount after unbind
drm/i915/hdmi: remove unused intel_hdmi_hdcp2_protocol()
drm/i915: drop a bunch of superfluous inlines
drm/i915/audio: fix compressed_bpp check
Joonas Lahtinen (2):
Merge tag 'gvt-next-2020-04-22'
Quoting Sultan Alsawaf (2020-04-20 18:42:16)
> On Mon, Apr 20, 2020 at 12:02:39PM +0300, Joonas Lahtinen wrote:
> > I think the the patch should be dropped for now before the issue is
> > properly addressed. Either by backporting the mainline fixes or if
> > those are too big
Quoting Sultan Alsawaf (2020-04-20 19:15:14)
> On Mon, Apr 20, 2020 at 11:21:42AM +0300, Joonas Lahtinen wrote:
> > So it seems that the patch got pulled into v5.6 and has been backported
> > to v5.5 but not v5.4.
>
> You're right, that's my mistake.
Did applying
Quoting Greg KH (2020-04-14 11:23:44)
> On Tue, Apr 14, 2020 at 09:15:07AM +0100, Chris Wilson wrote:
> > Quoting Greg KH (2020-04-11 12:39:57)
> > > On Fri, Apr 10, 2020 at 07:17:38AM -0700, Sultan Alsawaf wrote:
> > > > On Fri, Apr 10, 2020 at 11:08:38AM +0200, Greg KH wrote:
> > > > > On Tue, Ap
Quoting Sultan Alsawaf (2020-04-20 08:24:19)
> Chris,
>
> Could you please look at this in earnest? This is a real bug that crashes my
> laptop without any kind of provocation. It is undeniably a bug in i915, and
> I've
> clearly described it in my patch. If you dont like the patch, I'm open to a
r struct drm_device based logging
drm/i915/stolen: prefer struct drm_device based logging
drm/i915/gt: prefer struct drm_device based logging
drm/i915/uc: prefer struct drm_device based logging
Joonas Lahtinen (3):
Merge drm/drm-next into drm-intel-next-queued
Merge tag &
Quoting Jani Nikula (2020-04-15 10:48:15)
> On Wed, 15 Apr 2020, Daniel Vetter wrote:
> > On Wed, Apr 15, 2020 at 8:40 AM Jani Nikula
> > wrote:
> >>
> >> On Wed, 08 Apr 2020, Maarten Lankhorst
> >> wrote:
> >> > Hey,
> >> >
> >> > Here's a pull request to pull in the DP PHY Compliance series.
Quoting Akeem G Abodunrin (2020-01-30 18:57:21)
> From: Prathap Kumar Valsan
>
> On gen7 and gen7.5 devices, there could be leftover data residuals in
> EU/L3 from the retiring context. This patch introduces workaround to clear
> that residual contexts, by submitting a batch buffer with dedicated
Hi Dave & Daniel,
Last pull request for 5.5. Then it's Jani's turn
to handle 5.6.
A fix for huge userptr objects and a fix that is
also cc stable, to correctly handle negative values
in engine->uabi_class/instance.
Regards, Joonas
***
drm-intel-fixes-2020-01-23:
- Avoid overflow with huge use
Quoting Stephen Rothwell (2020-01-20 23:34:24)
> Hi all,
>
> After merging the drm-intel-fixes tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
>
> Caused by commit
>
> d8fcca47e195 ("drm/i915/userptr: fix size calculation")
>
> I have reverted that commit for today
Hi Dave & Daniel,
Two new fixes still, the VMA activity fixes are overflow from
last week as I couldn't get CI results then.
One important uAPI fix for PMU names to comply with tools/perf,
thanks for our media team for noticing. A compile fix and two
VMA activity tracking fixes for error capture
moment. I think it would be a
> worthwhile endeavour, but one requiring more time and conversation to
> ensure the drm traces fit somewhere sensible.
>
> Cc: Daniel Vetter
> Cc: David Airlie
> Cc: Jani Nikula
> Cc: Joonas Lahtinen
> Cc: Pekka Paalanen
> Cc: Rob Clark
Quoting Joonas Lahtinen (2020-01-09 15:34:58)
> Hi Dave & Daniel,
>
> Happy New Year, now back from the holiday break.
>
> A bunch of important fixes. Further fixes for the power/perf
> regressions caused by the past security fixes. Then fix for
> user reported GPU h
Hi Dave & Daniel,
Happy New Year, now back from the holiday break.
A bunch of important fixes. Further fixes for the power/perf
regressions caused by the past security fixes. Then fix for
user reported GPU hang regression. Revert to avoid screen flicker
caused by HDA audio. Then missing two W/A a
Quoting Wambui Karuga (2020-01-07 17:13:29)
> Convert the use of the DRM_DEBUG_KMS() logging macro to the new struct
> drm_device based drm_dbg_kms() logging macro in i915/intel_pch.c.
>
> Signed-off-by: Wambui Karuga
> ---
> drivers/gpu/drm/i915/intel_pch.c | 46 +---
Quoting Jani Nikula (2019-12-19 14:37:02)
> On Thu, 19 Dec 2019, Stephen Rothwell wrote:
> > Hi all,
> >
> > Commits
> >
> > 987e379d7500 ("Revert "devtmpfs: use do_mount() instead of ksys_mount()"")
> > 9bd5ba4fe25a ("Revert "initrd: use do_mount() instead of ksys_mount()"")
> > fa31001c96a
et fence_work.ops before dma_fence_init
drm/i915/gem: Keep request alive while attaching fences
Gao Fred (1):
drm/i915/gvt: Fix guest boot warning
Joonas Lahtinen (1):
Merge tag 'gvt-fixes-2019-12-18' of https://github.com/intel/gvt-linux
into drm-intel-fixes
Matt
Hi Dave & Daniel,
Two important user visible fixes; GPU hang on BDW/SKL when idling
and top of screen corruption on GLK+ when FBC enabled.
Fix to Tigerlake perf/OA, HDCP commit computation touching global
state.
Then two CI spotted corner cases, race condition about context
retirement and lockde
/gem: Take timeline->mutex to walk list-of-requests
Gao, Fred (2):
drm/i915/gvt: Refine non privilege register address calucation
drm/i915/gvt: Update force-to-nonpriv register whitelist
Joonas Lahtinen (1):
Merge tag 'gvt-next-fixes-2019-12-02' of
https://github.co
Hi Dave & Daniel,
Most importantly we have the fix to power regression that was
introduced by the security fixes. Then fix for query uAPI and
increase in request pre-emption timeout to accommodate super
heavy benchmarks.
Couple of display voltage programming fixes too.
Thanks to Chris for fixing
Quoting Niranjan Vishwanathapura (2019-11-27 21:23:56)
> >We should try to have the uAPI as final as early as possible. The
> >change process is harder the later it is done, even for RFC :)
> >
> >On the same note, I'm inclined to have I915_SVM_MIGRATE called
> >I915_GEM_VM_PREFAULT from the start,
Quoting Niranjana Vishwanathapura (2019-11-22 22:57:21)
> Shared Virtual Memory (SVM) allows the programmer to use a single virtual
> address space which will be shared between threads executing on CPUs and GPUs.
> It abstracts away from the user the location of the backing memory, and hence
> simp
Quoting Niranjan Vishwanathapura (2019-11-25 18:40:57)
> On Mon, Nov 25, 2019 at 09:59:37AM +, Chris Wilson wrote:
> >Quoting Niranjana Vishwanathapura (2019-11-22 20:57:24)
> >> Shared Virtual Memory (SVM) runtime allocator support allows
> >> binding a shared virtual address to a buffer objec
ges.
>
> Cc: Joonas Lahtinen
> Cc: Jon Bloomfield
> Cc: Daniel Vetter
> Cc: Sudeep Dutt
> Signed-off-by: Niranjana Vishwanathapura
> Signed-off-by: Venkata Sandeep Dhanalakota
Having this as a separate commit ahead of the functionality breaks
bisecting.
The uAPI should be e
Hi Dave & Daniel,
A quick fixup amendment to the previous PR. gem_exec_reloc/basic-range
got broken in CI, so we've issued a patch revert the offending commit
for now.
Once the results for CI_DINF_163 appear here, and the timeouts seen
in last three CI_DINF_ are green, feel free to pull this:
ht
Quoting Joonas Lahtinen (2019-11-20 22:40:35)
> Hi Dave & Daniel,
>
> NOTE: CI shard results are delayed, bu I'm sending this
> already because I'll travel tomorrow. I'll let you know
> if the results look OK or not. Or you can look up
> CI_DINF_162 results c
drm/i915: Fix detection for a CMP-V PCH
drm/i915: Restore GT coarse power gating workaround
Jani Nikula (1):
drm/i915: fix accidental static variable use
Joonas Lahtinen (1):
Merge tag 'gvt-next-fixes-2019-11-12' of
https://github.com/intel/gvt-linux into drm-intel-next
Quoting Dave Airlie (2019-11-14 03:33:24)
> The landing of the i915 CVE fixes into Linus tree has created a bit of
> a mess in linux-next and downstream in drm-next trees.
>
> I talked to Daniel and he had talked to Joonas a bit, and I decided to
> go with what Daniel describes as the YOLO merge,
Hi Dave & Daniel,
Here comes the set of fixes for drm-intel-next. Quite a few fixes
after a silent last week.
I'll do the backmerge of the BCX fixes from Linus's tree next and
send it as an extra PR.
Regards, Joonas
***
drm-intel-next-fixes-2019-11-14:
- PMU "Frequency" is reported as accumul
Hi Dave & Daniel,
A quiet start. Hopefully stays that way :)
RCU tracking fix and suspend GEM_BUG_ON fix with dependencies.
Regards, Joonas
***
drm-intel-next-fixes-2019-11-07:
One RCU fix and fix for suspend GEM_BUG_ON (with dependencies).
The following changes since commit 8a86b00a437ec06b
Quoting Chris Wilson (2019-11-05 23:13:36)
> Quoting Daniel Vetter (2019-11-05 20:58:25)
> > On Tue, Nov 5, 2019 at 9:38 PM Chris Wilson
> > wrote:
> > >
> > > Quoting Daniel Vetter (2019-11-05 19:38:29)
> > > > It's broken.
> > > >
> > > > Reported-by: Stephen Rothwell
> > > > References:
> >
block definition
Janusz Krzysztofik (2):
drm/i915: Fix i915_inject_load_error() name to read *_probe_*
drm/i915: Rename "inject_load_failure" module parameter
Joonas Lahtinen (2):
drm/i915: Update DRIVER_DATE to 20191101
drm/i915: Update DRIVER_DATE to 20191101
drm_debug_category {
> + /**
> +* @DRM_UT_CORE: Used in the generic drm code: drm_ioctl.c, drm_mm.c,
> +* drm_memory.c, ...
> +*/
> + DRM_UT_CORE = 0x01,
While here, why not BIT()
Reviewed-by: Joonas Lahtinen
Regards, Joonas
_
https://lore.kernel.org/lkml/CAHk-=wiAsJLw1egFEE=z7-ggtm6wcvtyytxza1+bhqta4gg...@mail.gmail.com/
> Reported-by: Linus Torvalds
> [ paulmck: From rcu_replace() to rcu_replace_pointer() per Ingo Molnar. ]
> Signed-off-by: Paul E. McKenney
> Cc: Jani Nikula
> Cc: Joonas Lahtinen
> Cc: Rodrigo
GMP register size for GEN11
drm/i915/dp: Program an Infoframe SDP Header and DB for HDR Static
Metadata
drm/i915/dp: Attach HDR metadata property to DP connector
James Ausmus (2):
drm/i915: Move SAGV block time to dev_priv
drm/i915/tgl: Read SAGV block time from PCODE
Ja
Quoting Sean Paul (2019-10-10 23:48:08)
> From: Sean Paul
>
> *Record scratch* You read that subject correctly, I bet you're wondering
> how we got here. At least hear me out before you flame :-)
>
> For a long while now, we (ChromeOS) have been struggling getting any
> value out of user feedbac
ntel_vga.[ch]
drm/i915: use DRM_ERROR() instead of drm_err()
drm/i915: use DRM_DEBUG_KMS() instead of drm_dbg(DRM_UT_KMS, ...)
drm/i915/dp: remove static variable for aux last status
drm/i915/vga: rename intel_vga_msr_write() to intel_vga_reset_io_mem()
drm/i915: split
+ Chris and Tvrtko
Quoting Andrew Morton (2019-10-03 00:57:21)
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 01 Oct 2019 17:06:35 + bugzilla-dae...@bugzilla.kernel.org wrote:
>
> > https://bugzilla.kernel.org/show_bug.cg
Quoting Dave Airlie (2019-08-13 22:20:52)
> On Sat, 10 Aug 2019 at 08:26, Matthew Auld wrote:
> >
> > In preparation for upcoming devices with device local memory, introduce the
> > concept of different memory regions, and a simple buddy allocator to manage
> > them in i915.
> >
> > One of the con
Quoting john.hubb...@gmail.com (2019-08-02 05:19:37)
> From: John Hubbard
>
> For pages that were retained via get_user_pages*(), release those pages
> via the new put_user_page*() routines, instead of via put_page() or
> release_pages().
>
> This is part a tree-wide conversion, as described in
Hi Dave & Daniel,
Some rather important fixes that appeared after -rc6 and
missed v5.2. As a PR by request of Daniel.
These avoid one WARN and potential dirty pointer deref,
fix a regression on saturated media loads and add missing
Icelake W/As.
I've manually added Cc: stable to all of them. The
drm/i915/gvt: Fix cmd length of VEB_DI_IECP
Joonas Lahtinen (2):
Merge tag 'gvt-fixes-2019-05-30' of https://github.com/intel/gvt-linux
into drm-intel-fixes
Merge tag 'gvt-fixes-2019-06-05' of https://github.com/intel/gvt-linux
into drm-intel-fixes
Tina Zh
n Xu (3):
drm/i915/gvt: Update force-to-nonpriv register whitelist
drm/i915/gvt: Fix GFX_MODE handling
drm/i915/gvt: Fix vGPU CSFE_CHICKEN1_REG mmio handler
Gao, Fred (1):
drm/i915/gvt: Fix cmd length of VEB_DI_IECP
Joonas Lahtinen (1):
Merge tag 'gvt-fixes-2019
Quoting Mauro Carvalho Chehab (2019-05-30 02:23:43)
> WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function
> Hardware workarounds ./drivers/gpu/drm/i915/intel_workarounds.c' failed with
> return code 1
> WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -function
>
by_guest_entry()
Joonas Lahtinen (1):
Merge tag 'gvt-fixes-2019-05-21' of https://github.com/intel/gvt-linux
into drm-intel-fixes
Weinan (1):
drm/i915/gvt: emit init breadcrumb for gvt request
Yan Zhao (4):
drm/i915/gvt: use cmd to restore in-context mmios to hw for gen9 pla
We also have an incoming patch where the Fixes: line has a comment in
it. Does your tooling account for this when checking the Fixes: line?
Regards, Joonas
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/l
Quoting Stephen Rothwell (2019-05-20 15:15:38)
> Hi all,
>
> In commit
>
> 0d90ccb70211 ("drm/i915: Delay semaphore submission until the start of the
> signaler")
>
> Fixes tag
>
> Fixes: e88619646971 ("drm/i915: Use HW semaphores for inter-engine synchroni
>
> has these problem(s):
>
>
Hi Dave & Daniel,
A fix to close a race opportunity between IRQ handler and RCU.
Two fixes that are also stable, disabling FBC on GLK and HSW EDP fastset
correction.
These patches definitely caused conflicts when merged, resolutions should
be all good.
Regards, Joonas
***
drm-intel-next-fixe
sion until the start of the signaler
drm/i915: Disable semaphore busywaits on saturated systems
Colin Xu (1):
drm/i915/gvt: Add in context mmio 0x20D8 to gen9 mmio list
Joonas Lahtinen (1):
Merge tag 'gvt-next-fixes-2019-05-07' of
https://github.com/intel/gvt-linux into drm
g:
> 'i915_request_await_start' defined but not used [-Wunused-function]
> i915_request_await_start(struct i915_request *rq, struct i915_request
> *signal)
> ^~~~
>
> vim +/already_busywaiting +842 drivers/gpu/drm/i915/i915_request.c
>
> 47f4a142
101 - 200 of 424 matches
Mail list logo
