On Wed, Sep 15, 2021 at 12:29:12PM -0700, John Harrison wrote:
On 9/15/2021 12:24, Belgaumkar, Vinay wrote:
On 9/14/2021 12:51 PM, Lucas De Marchi wrote:
The clflush calls here aren't doing anything since we are not writting
something and flushing the cache lines to be visible to GuC. Here the
On Tue, Sep 07, 2021 at 02:56:21PM -0700, Lucas De Marchi wrote:
On Tue, Jul 06, 2021 at 04:44:30PM -0700, Lucas De Marchi wrote:
On Thu, Nov 05, 2020 at 10:02:27AM +0200, Joonas Lahtinen wrote:
Quoting Lucas De Marchi (2020-11-05 03:04:22)
On Wed, Nov 04, 2020 at 11:55:15AM +0200, Joonas Laht
== Series Details ==
Series: drm/i915/display: Fix the dsc check while selecting min_cdclk (rev3)
URL : https://patchwork.freedesktop.org/series/94683/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10615_full -> Patchwork_21104_full
On Tue, Sep 21, 2021 at 02:13:42AM +, Patchwork wrote:
> == Series Details ==
>
> Series: Check SFC fusing on Xe_HP (rev4)
> URL : https://patchwork.freedesktop.org/series/94808/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10613_full -> Patchwork_21099_full
> =
== Series Details ==
Series: drm/i915/display: Fix the dsc check while selecting min_cdclk (rev3)
URL : https://patchwork.freedesktop.org/series/94683/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10615 -> Patchwork_21104
== Series Details ==
Series: drm/i915/tc: Fix TypeC connect/disconnect sequences
URL : https://patchwork.freedesktop.org/series/94878/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10615_full -> Patchwork_21102_full
Summary
== Series Details ==
Series: Check SFC fusing on Xe_HP (rev4)
URL : https://patchwork.freedesktop.org/series/94808/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10613_full -> Patchwork_21099_full
Summary
---
**FAILU
== Series Details ==
Series: series starting with [v3,1/3] drm/i915/display: Disable frontbuffer
rendering when PSR2 selective fetch is enabled
URL : https://patchwork.freedesktop.org/series/94879/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10615 -> Patchwork_21103
===
== Series Details ==
Series: series starting with [v3,1/3] drm/i915/display: Disable frontbuffer
rendering when PSR2 selective fetch is enabled
URL : https://patchwork.freedesktop.org/series/94879/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mo
== Series Details ==
Series: series starting with [v3,1/3] drm/i915/display: Disable frontbuffer
rendering when PSR2 selective fetch is enabled
URL : https://patchwork.freedesktop.org/series/94879/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
32149725ef4a drm/i915/display: Di
== Series Details ==
Series: drm/i915/tc: Fix TypeC connect/disconnect sequences
URL : https://patchwork.freedesktop.org/series/94878/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10615 -> Patchwork_21102
Summary
---
Created a new issue for the regression failures and re-reported.
https://gitlab.freedesktop.org/drm/intel/-/issues/4179
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Monday, September 20, 2021 1:25 PM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana
Subject: Re
== Series Details ==
Series: Check SFC fusing on Xe_HP (rev4)
URL : https://patchwork.freedesktop.org/series/94808/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10613 -> Patchwork_21099
Summary
---
**SUCCESS**
No
== Series Details ==
Series: Check SFC fusing on Xe_HP (rev4)
URL : https://patchwork.freedesktop.org/series/94808/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10613 -> Patchwork_21099
Summary
---
**FAILURE**
Se
PSR always had a requirement to only be enabled if there is active
planes but not following that never caused any issues.
But that changes in Alderlake-P, leaving PSR enabled without
active planes causes transcoder/port underruns.
Similar behavior was fixed during the pipe disable sequence by
comm
From: Gwan-gyeong Mun
We are still missing the PSR2 selective fetch handling of biplanar
formats but until proper handle is added we can workaround it by
doing full frames fetch when state has biplanar formats.
We need the second check because an update in a regular format could
intersect with a
By now all the userspace applications should have migrated to atomic
or at least be calling DRM_IOCTL_MODE_DIRTYFB.
But we still can't kill frontbuffer rendering support for good as
we have some performance issues to be solved in desktop environments
that do not use compositors.
But PSR2 selective
== Series Details ==
Series: drm/i915/tc: Fix TypeC connect/disconnect sequences
URL : https://patchwork.freedesktop.org/series/94878/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+drivers/gpu
== Series Details ==
Series: drm/i915/tc: Fix TypeC connect/disconnect sequences
URL : https://patchwork.freedesktop.org/series/94878/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9d2a21b4286f drm/i915/tc: Fix TypeC port init/resume time sanitization
8cf6d77baac7 drm/i915/adlp
After the previous patch the driver holds a power domain blocking
TC-cold whenever the port is locked, so we can remove the extra blocking
around the lock/unlock sequence.
Cc: José Roberto de Souza
Signed-off-by: Imre Deak
---
drivers/gpu/drm/i915/display/intel_tc.c | 4
1 file changed, 4
So far TC-cold was blocked only for the duration of TypeC mode resets.
The DP-alt and legacy modes require TC-cold to be blocked also whenever
the port is in use (AUX transfers, enable modeset), and this was ensured
by the held PHY ownership flag. On ADL-P this doesn't work, since the
PHY ownership
A follow-up patch will disconnect/reconnect PHYs around AUX transfers
and modeset enable/disables. To prepare for that and make things
consistent for all TypeC modes stop connecting the PHY in legacy mode
without a sink being connected. This was done before since in legacy
mode the PHY is dedicated
The PHY ownership release->AUX PW disable steps during a modeset
disable->PHY disconnect sequence can hang the system if the PHY
disconnect happens after disabling the PHY's PLL. The spec doesn't
require a specific order for these two steps, so this issue is still
being root caused by HW/FW teams.
For the ADL-P TBT mode the spec doesn't require blocking TC-cold by
using the legacy AUX power domain. To avoid the timeouts that this would
cause during PHY disconnect/reconnect sequences (which will be more
frequent after a follow-up change) use the TC_COLD_OFF power domain in
TBT mode on all pla
While a TypeC port mode is locked a DISPLAY_CORE power domain reference
is held, which implies a runtime PM ref. By removing the ICL !legacy
port special casing, a TC_COLD_OFF power domain reference will be taken
for such ports, which also translates to a runtime PM ref on that
platform. A follow-u
Waiting for the PHY complete flag to clear when releasing the PHY
ownership was add in
commit ddec362724f9 ("drm/i915: Wait for TypeC PHY complete flag to clear in
safe mode")
This isn't required by the spec, the vague idea was to make the
handshake with the firmware more robust, without actual
A follow-up change will start to disconnect/re-connect PHYs around AUX
transfers and modeset enable/disables. To prepare for that add a new
TypeC PHY disconnected mode, to help tracking the TC-cold blocking power
domain status (no power domain in disconnected state, mode dependent
power domain in c
A follow-up change will select the TC-cold blocking power domain based
on the TypeC mode, prepare for that here.
Also bring intel_tc_cold_requires_aux_pw() earlier to its logical place
for readability.
No functional change.
Cc: José Roberto de Souza
Signed-off-by: Imre Deak
---
.../drm/i915/d
Instead of directly accessing the TypeC port internal struct members,
add/use helpers to retrieve the corresponding properties.
No functional change.
Cc: José Roberto de Souza
Signed-off-by: Imre Deak
---
drivers/gpu/drm/i915/display/intel_ddi.c | 31 +++
drivers/gpu/drm/i
On ADL-P the PHY ready/complete flag is always set even in TBT-alt mode.
To avoid taking the PHY ownership and the following spurious "PHY sudden
disconnect" messages on this platform when connecting the PHY in TBT
mode, check if there is any DP-alt or legacy sink connected before
taking the owners
Atm during driver loading and system resume TypeC ports are accessed
before their HW/SW state is synced. Move the TypeC port sanitization to
the encoder's sync_state hook to fix this.
Fixes: f9e76a6e68d3 ("drm/i915: Add an encoder hook to sanitize its state
during init/resume")
Cc: José Roberto d
On ADL-P the PHY ready (aka status complete on other platforms) flag is
always set, besides when a DP-alt, legacy sink is connected also when a
TBT sink is connected or nothing is connected. So assume the PHY to be
connected when both the TBT live status and PHY ready flags are set.
Cc: José Rober
This patchset fixes two issues on ADL-P related to the TypeC PHY
connect/disconnect sequences in patch 11 and 13 and a few other minor
TypeC issues I noticed on the way. The fix in patch 11 requires some
refactoring and it affects all TypeC platforms; this was the way that
made sense to me to keep
On 8/20/2021 15:44, Matthew Brost wrote:
Update parallel submit doc to point to i915_drm.h
Signed-off-by: Matthew Brost
Reviewed-by: John Harrison
---
Documentation/gpu/rfc/i915_parallel_execbuf.h | 122 --
Documentation/gpu/rfc/i915_scheduler.rst | 4 +-
2 files
On 8/20/2021 15:44, Matthew Brost wrote:
Introduce 'set parallel submit' extension to connect UAPI to GuC
multi-lrc interface. Kernel doc in new uAPI should explain it all.
IGT: https://patchwork.freedesktop.org/patch/447008/?series=93071&rev=1
media UMD: link to come
Is this link still not ava
Replace drm_mm with drm buddy manager for
VRAM memory management
Signed-off-by: Arunpravin
---
.../gpu/drm/amd/amdgpu/amdgpu_res_cursor.h| 78 +--
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h | 3 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 216 ++
3 files chan
Port Intel buddy system manager to drm root folder
Add CPU mappable/non-mappable region support to the drm buddy manager
Signed-off-by: Arunpravin
---
drivers/gpu/drm/Makefile| 2 +-
drivers/gpu/drm/drm_buddy.c | 465
include/drm/drm_buddy.h | 154 +
On 8/20/2021 15:44, Matthew Brost wrote:
Set number of engines before attempting to create contexts so the
function free_engines can clean up properly.
Fixes: d4433c7600f7 ("drm/i915/gem: Use the proto-context to handle create
parameters (v5)")
Signed-off-by: Matthew Brost
Cc:
---
drivers/g
On 8/20/2021 15:44, Matthew Brost wrote:
Display the workqueue status in debugfs for GuC contexts that are in
parent-child relationship.
Signed-off-by: Matthew Brost
---
.../gpu/drm/i915/gt/uc/intel_guc_submission.c | 51 ++-
1 file changed, 37 insertions(+), 14 deletions(
On 8/20/2021 15:44, Matthew Brost wrote:
Update context and full GPU reset to work with multi-lrc. The idea is
parent context tracks all the active requests inflight for itself and
its' children. The parent context owns the reset replaying / canceling
its' -> its
requests as needed.
Signed-of
On Thu, Sep 16, 2021 at 2:31 AM Maxime Ripard wrote:
>
> Hi Dave, Daniel,
>
> Here's the first drm-misc-next PR for 5.16
>
> Thanks!
> Maxime
>
> drm-misc-next-2021-09-16:
> drm-misc-next for $kernel-version:
>
> UAPI Changes:
>
> Cross-subsystem Changes:
> - dma-buf: Avoid a warning with some a
On 8/20/2021 15:44, Matthew Brost wrote:
The GuC must receive requests in the order submitted for contexts in a
parent-child relationship to function correctly. To ensure this, insert
a submit fence between the current request and last request submitted
for requests / contexts in a parent child r
== Series Details ==
Series: drm/i915/bdb: Fix version check
URL : https://patchwork.freedesktop.org/series/94871/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10614 -> Patchwork_21101
Summary
---
**FAILURE**
Ser
Hi josh, Ben, Kyle
Kindly add the below i915 changes to linux-firmware:
linux-firmware: add frimware for mediatek bluetooth chip (MT7922) (2021-09-13
11:35:49 -0400)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-firmware adlp_dmc_2_12
for you to fetch changes u
On 8/20/2021 15:44, Matthew Brost wrote:
Implement multi-lrc submission via a single workqueue entry and single
H2G. The workqueue entry contains an updated tail value for each
request, of all the contexts in the multi-lrc submission, and updates
these values simultaneously. As such, the tasklet
On 21/09/20 09:54AM, kernel test robot wrote:
>
> [auto build test ERROR on drm-exynos/exynos-drm-next]
> [also build test ERROR on tegra-drm/drm/tegra/for-next linus/master v5.15-rc2
> next-20210917]
I forgot to #include for those platforms and didn't notice
because I only tried to build for X
On Thu, 2021-09-16 at 12:32 +0200, Hans de Goede wrote:
>
> I'm fine with refactoring this a bit and adding
> an intel_modeset_probe_defer() helper for this, I assume I should also
> move the vga_switcheroo_client_probe_defer(pdev) check there?
>
> As you suggested yourself in your reply to the c
On Mon, 2021-09-20 at 16:11 +0200, Lukasz Majczak wrote:
> With patch "drm/i915/vbt: Fix backlight parsing for VBT 234+"
> the size of bdb_lfp_backlight_data structure has been increased,
> causing if-statement in the parse_lfp_backlight function
> that comapres this structure size to the one retri
On Mon, Sep 20, 2021 at 08:42:42AM +0100, Tvrtko Ursulin wrote:
>
> On 20/09/2021 08:38, Jani Nikula wrote:
> > On Mon, 20 Sep 2021, Tvrtko Ursulin wrote:
> > > On 18/09/2021 00:38, Matthew Brost wrote:
> > > > From: Hugh Dickins
> > > >
> > > > 5.15-rc1 crashes with blank screen when booting u
On Mon, Sep 20, 2021 at 08:28:13AM +0100, Tvrtko Ursulin wrote:
>
> On 18/09/2021 00:38, Matthew Brost wrote:
> > From: Hugh Dickins
> >
> > 5.15-rc1 crashes with blank screen when booting up on two ThinkPads
> > using i915. Bisections converge convincingly, but arrive at different
> > and surp
On Mon, Sep 20, 2021 at 06:55:52PM +, Patchwork wrote:
> == Series Details ==
>
> Series: Check SFC fusing on Xe_HP (rev4)
> URL : https://patchwork.freedesktop.org/series/94808/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10613 -> Patchwork_21099
> ===
With patch "drm/i915/vbt: Fix backlight parsing for VBT 234+"
the size of bdb_lfp_backlight_data structure has been increased,
causing if-statement in the parse_lfp_backlight function
that comapres this structure size to the one retrieved from BDB,
always to fail for older revisions.
This patch fix
On Mon, Sep 20, 2021 at 3:21 PM Arunpravin
wrote:
>
> Replace drm_mm with drm buddy manager for
> VRAM memory management
Would be good to document why we are doing this and what advantages it
brings over the old drm_mm code.
Alex
>
> Signed-off-by: Arunpravin
> ---
> .../gpu/drm/amd/amdgpu/a
== Series Details ==
Series: drm/i915: Suspend / resume backup- and restore of LMEM. (rev6)
URL : https://patchwork.freedesktop.org/series/94278/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10613 -> Patchwork_21100
Summar
On Mon, Sep 20, 2021 at 3:21 PM Arunpravin
wrote:
Please prefix the patch subject with drm. E.g.,
drm: Enable buddy memory manager support
Same for the second patch, but make it drm/amdgpu instead.
Alex
>
> Port Intel buddy system manager to drm root folder
> Add CPU mappable/non-mappable reg
On Fri, 2021-09-17 at 10:08 -0700, Matt Roper wrote:
> From: Venkata Sandeep Dhanalakota
>
> Support for multiple GT's within a single i915 device will be
> arriving
> soon. Since each GT may have its own fusing and require different
> workarounds, we need to make the GT workaround functions and
On Sat, Sep 18, 2021 at 12:06:01AM +0300, Imre Deak wrote:
> On Fri, Sep 17, 2021 at 01:52:39PM -0700, José Roberto de Souza wrote:
> > Specification asks for DC_STATE_DEBUG_MASK_CORES to be set for all
> > platforms that supports DMC, not only for geminilake and broxton.
>
> According to the spec
== Series Details ==
Series: drm/i915: Suspend / resume backup- and restore of LMEM. (rev6)
URL : https://patchwork.freedesktop.org/series/94278/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5fe8cae9d0ac drm/i915/ttm: Implement a function to copy the contents of two
TTM-based
== Series Details ==
Series: Check SFC fusing on Xe_HP (rev4)
URL : https://patchwork.freedesktop.org/series/94808/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10613 -> Patchwork_21099
Summary
---
**FAILURE**
Se
== Series Details ==
Series: Check SFC fusing on Xe_HP (rev4)
URL : https://patchwork.freedesktop.org/series/94808/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+drivers/gpu/drm/i915/gt/intel_
Looks good to me.
Tested-by: Gwan-gyeong Mun
Reviewed-by: Gwan-gyeong Mun
On 9/17/21 11:52 PM, José Roberto de Souza wrote:
We were not completely following the selective fetch programming
sequence, here some things we were doing wrong:
- not programming plane selective fetch a PSR2_MAN_TRK_CT
On Thu, Sep 09 2021, Jason Gunthorpe wrote:
> Many of the mdev drivers use a simple counter for keeping track of the
> available instances. Move this code to the core code and store the counter
> in the mdev_type. Implement it using correct locking, fixing mdpy.
>
> Drivers provide a get_availabl
On Mon, Sep 20, 2021 at 04:18:10PM +, Teres Alexis, Alan Previn wrote:
>
> On Mon, 2021-09-20 at 12:04 -0400, Rodrigo Vivi wrote:
> > On Fri, Sep 17, 2021 at 09:20:00PM -0700, Alan Previn wrote:
> > > From: "Huang, Sean Z"
> > >
> > > The HW will generate a teardown interrupt when session te
On Mon, 20 Sep 2021, Lukasz Majczak wrote:
> With patch "drm/i915/vbt: Fix backlight parsing for VBT 234+"
> the size of bdb_lfp_backlight_data structure has been increased,
> causing if-statement in the parse_lfp_backlight function
> that comapres this structure size to the one retrieved from BDB
On Mon, Sep 20, 2021 at 02:19:18PM +0200, Cornelia Huck wrote:
> On Thu, Sep 09 2021, Jason Gunthorpe wrote:
>
> > The subchannel should be left in a quiescent state unless the VFIO device
> > FD is opened. When the FD is opened bring the chanel to active and allow
> > the VFIO device to operate.
On Mon, 2021-09-20 at 12:04 -0400, Rodrigo Vivi wrote:
> On Fri, Sep 17, 2021 at 09:20:00PM -0700, Alan Previn wrote:
> > From: "Huang, Sean Z"
> >
> > The HW will generate a teardown interrupt when session termination is
> > required, which requires i915 to submit a terminating batch. Once the
On Mon, 2021-09-20 at 12:09 -0400, Rodrigo Vivi wrote:
> On Fri, Sep 17, 2021 at 09:20:01PM -0700, Alan Previn wrote:
> > From: Daniele Ceraolo Spurio
> >
> > This api allow user mode to create protected buffers and to mark
> > contexts as making use of such objects. Only when using contexts
> >
On Fri, Sep 17, 2021 at 09:20:01PM -0700, Alan Previn wrote:
> From: Daniele Ceraolo Spurio
>
> This api allow user mode to create protected buffers and to mark
> contexts as making use of such objects. Only when using contexts
> marked in such a way is the execution guaranteed to work as expecte
On Fri, Sep 17, 2021 at 09:20:00PM -0700, Alan Previn wrote:
> From: "Huang, Sean Z"
>
> The HW will generate a teardown interrupt when session termination is
> required, which requires i915 to submit a terminating batch. Once the HW
> is done with the termination it will generate another interru
Re-reported.
-Original Message-
From: Roper, Matthew D
Sent: Monday, September 20, 2021 8:26 AM
To: intel-gfx@lists.freedesktop.org
Cc: Siddiqui, Ayaz A ; Vudum, Lakshminarayana
; Kijanczuk, Damian
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Add "intel_" as
prefix
Reported.
-Original Message-
From: Roper, Matthew D
Sent: Monday, September 20, 2021 7:53 AM
To: intel-gfx@lists.freedesktop.org
Cc: Vudum, Lakshminarayana ; Kijanczuk, Damian
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Make wa list per-gt (rev2)
On Sat, Sep 18, 2021 at 01:46:39AM
We really only need memcpy restore for objects that affect the
operability of the migrate context. That is, primarily the page-table
objects of the migrate VM.
Add an object flag, I915_BO_ALLOC_PM_EARLY for objects that need early
restores using memcpy and a way to assign LMEM page-table object fl
Pinned context images are now reset during resume. Don't back them up,
and assuming that rings can be assumed empty at suspend, don't back them
up either.
Introduce a new object flag, I915_BO_ALLOC_PM_VOLATILE meaning that an
object is allowed to lose its content on suspend.
v3:
- Slight document
Pinned contexts, like the migrate contexts need reset after resume
since their context image may have been lost. Also the GuC needs to
register pinned contexts.
Add a list to struct intel_engine_cs where we add all pinned contexts on
creation, and traverse that list at resume time to reset the pin
Just evict unpinned objects to system. For pinned LMEM objects,
make a backup system object and blit the contents to that.
Backup is performed in three steps,
1: Opportunistically evict evictable objects using the gpu blitter.
2: After gt idle, evict evictable objects using the gpu blitter. This w
An upcoming common pattern is to traverse the region object list and
perform certain actions on all objects in a region. It's a little tricky
to get the list locking right, in particular since a gem object may
change region unless it's pinned or the object lock is held.
Define a function that does
When backing up or restoring contents of pinned objects at suspend /
resume time we need to allocate a new object as the backup. Add a function
to facilitate copies between the two. Some data needs to be copied before
the migration context is ready for operation, so make sure we can
disable acceler
Implement backup and restore of LMEM during suspend / resume.
What complicates things a bit is handling of pinned LMEM memory during
suspend and the fact that we might be dealing with unmappable LMEM in
the future, which makes us want to restrict the number of pinned objects that
need memcpy resume
On Fri, Sep 17, 2021 at 10:08:45AM -0700, Matt Roper wrote:
> From: Venkata Sandeep Dhanalakota
>
> Support for multiple GT's within a single i915 device will be arriving
> soon. Since each GT may have its own fusing and require different
> workarounds, we need to make the GT workaround function
== Series Details ==
Series: drm/i915/gt: Add "intel_" as prefix in set_mocs_index() (rev3)
URL : https://patchwork.freedesktop.org/series/94721/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10605_full -> Patchwork_21088_full
==
== Series Details ==
Series: drm/i915: Make wa list per-gt (rev2)
URL : https://patchwork.freedesktop.org/series/94811/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10605_full -> Patchwork_21091_full
Summary
---
**S
On Fri, Sep 17, 2021 at 11:42:09PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/gt: Add "intel_" as prefix in set_mocs_index() (rev3)
> URL : https://patchwork.freedesktop.org/series/94721/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10605_fu
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
On Sat, Sep 18, 2021 at 01:46:39AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Make wa list per-gt (rev2)
> URL : https://patchwork.freedesktop.org/series/94811/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_10605_full -> Patchwork_21091_full
== Series Details ==
Series: drm/i915/guc, docs: Fix pdfdocs build error by removing nested grid
URL : https://patchwork.freedesktop.org/series/94858/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10611 -> Patchwork_21098
S
Nested grids in grid-table cells are not specified as proper ReST
constructs.
Commit 572f2a5cd974 ("drm/i915/guc: Update firmware to v62.0.0")
added a couple of kerneldoc tables of the form:
+---+---+--+
| 1 | 31:0 | +--
Am 17.09.21 um 16:55 schrieb Daniel Vetter:
On Fri, Sep 17, 2021 at 02:35:08PM +0200, Christian König wrote:
Makes the handling a bit more complex, but avoids the use of
dma_resv_get_excl_unlocked().
v2: add missing rcu_read_lock()/unlock()
Signed-off-by: Christian König
---
drivers/gpu/drm
Am 20.09.21 um 10:43 schrieb Tvrtko Ursulin:
On 17/09/2021 14:23, Daniel Vetter wrote:
On Fri, Sep 17, 2021 at 02:34:48PM +0200, Christian König wrote:
Abstract the complexity of iterating over all the fences
in a dma_resv object.
The new loop handles the whole RCU and retry dance and
returns
Am 20.09.21 um 10:47 schrieb Tvrtko Ursulin:
On 20/09/2021 09:45, Tvrtko Ursulin wrote:
On 17/09/2021 13:35, Christian König wrote:
Simplifying the code a bit.
v2: use dma_resv_for_each_fence instead, according to Tvrtko the
lock is
held here anyway.
v3: back to using dma_resv_for_eac
Am 17.09.21 um 16:35 schrieb Daniel Vetter:
On Fri, Sep 17, 2021 at 02:34:50PM +0200, Christian König wrote:
This makes the function much simpler since the complex
retry logic is now handled else where.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-resv.c | 86 --
Am 17.09.21 um 16:53 schrieb Daniel Vetter:
On Fri, Sep 17, 2021 at 02:35:07PM +0200, Christian König wrote:
Simplifying the code a bit.
v2: add missing rcu_read_lock()/unlock()
Signed-off-by: Christian König
This will be gone as soon as I can land the last conversion patches. Plus
it's alwa
Hi,
First of all, thanks organizers for such a great conference. It was
smooth and, although there were some issues as it is usual in any
conference, they were fixed promptly :-)
I would like also to thank all of you for attending and participating
either via submitting talks, watching them or jo
Am 17.09.21 um 16:43 schrieb Daniel Vetter:
On Fri, Sep 17, 2021 at 02:34:52PM +0200, Christian König wrote:
This makes the function much simpler since the complex
retry logic is now handled elsewhere.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-resv.c | 68 ++-
Am 20.09.21 um 10:45 schrieb Tvrtko Ursulin:
On 17/09/2021 13:35, Christian König wrote:
This makes the function much simpler since the complex
retry logic is now handled else where.
Signed-off-by: Christian König
---
drivers/gpu/drm/i915/gem/i915_gem_busy.c | 32
On Thu, Sep 09 2021, Jason Gunthorpe wrote:
> The subchannel should be left in a quiescent state unless the VFIO device
> FD is opened. When the FD is opened bring the chanel to active and allow
> the VFIO device to operate. When the device FD is closed then quiesce the
> channel.
>
> To make thi
== Series Details ==
Series: drm/i915/debugfs: Do not report currently active engine when describing
objects (rev2)
URL : https://patchwork.freedesktop.org/series/94691/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_10609 -> Patchwork_21097
===
On Thu, Sep 09 2021, Jason Gunthorpe wrote:
> mdev_device should only be used in functions assigned to ops callbacks,
> interior functions should use the struct vfio_ccw_private instead of
> repeatedly trying to get it from the mdev.
>
> Signed-off-by: Jason Gunthorpe
> ---
> drivers/s390/cio/v
On Mon, 2021-09-20 at 12:05 +0100, Matthew Auld wrote:
> On 14/09/2021 20:31, Thomas Hellström wrote:
> > We really only need memcpy restore for objects that affect the
> > operability of the migrate context. That is, primarily the page-
> > table
> > objects of the migrate VM.
> >
> > Add an obje
On 14/09/2021 20:31, Thomas Hellström wrote:
We really only need memcpy restore for objects that affect the
operability of the migrate context. That is, primarily the page-table
objects of the migrate VM.
Add an object flag, I915_BO_ALLOC_PM_EARLY for objects that need early
restores using memcp
On Mon, 2021-09-20 at 11:49 +0100, Matthew Auld wrote:
> On 14/09/2021 20:31, Thomas Hellström wrote:
> > Just evict unpinned objects to system. For pinned LMEM objects,
> > make a backup system object and blit the contents to that.
> >
> > Backup is performed in three steps,
> > 1: Opportunistica
1 - 100 of 119 matches
Mail list logo
