> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 08/12] drm/i915/dp: Rework HDMI DFP TMDS clock
> handling
>
> From: Ville Syrjälä
>
> Rework the HDMI
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 10/12] drm/i915/dp: Duplicate native HDMI TMDS
> clock limit handling for DP HDMI DFPs
>
> From: Ville
> -Original Message-
> From: Ville Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Nautiyal, Ankit K ; Shankar, Uma
>
> Subject: [PATCH v2 12/12] drm/i915/dp: Disable DFP RGB->YCbCr conversion for
> now
>
> From: Ville Syrjälä
>
> We lack
i915 doesn't use pm_suspend_ignore_children(), which warrants that
any runtime active child of i915 will block the runtime suspend
of i915.
i915_runtime_pm_status only exposes i915 runtime pm usage_count,
which is not sufficient to debug in the scenarios when i915 has
zero usage_count but there
On 31/03/2022 00:28, Matt Roper wrote:
Historically we've selected and programmed a single MCR group/instance
ID at driver startup that will steer register accesses for GSLICE/DSS
ranges to a non-terminated instance. Any reads of these register ranges
that don't need a specific unicast access
On 31/03/2022 00:28, Matt Roper wrote:
Rather than treating multicast registers as 'i915_reg_t' let's define
them as a completely new type. This will allow the compiler to help us
make sure we're using multicast-aware functions to operate on multicast
registers.
This plan does break down a
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 02/12] drm/i915/dp: Respect the sink's max TMDS
> clock when dealing with DP->HDMI DFPs
>
> From: Ville
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 03/12] drm/i915/dp: Extract
> intel_dp_has_audio()
>
> From: Ville Syrjälä
>
> Declutter
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 07/12] drm/i915/dp: Make
> intel_dp_output_format()
> usable for "4:2:0 also" modes
>
> From: Ville
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 09/12] drm/i915/dp: Add support for "4:2:0
> also"
> modes for DP
>
> From: Ville Syrjälä
>
> Currently
> -Original Message-
> From: Ville Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Nautiyal, Ankit K ; Shankar, Uma
>
> Subject: [PATCH v2 11/12] drm/i915/dp: Fix DFP rgb->ycbcr conversion matrix
>
> From: Ville Syrjälä
>
> Our YCbCr
On Wed, 30 Mar 2022, Jani Nikula wrote:
> Only intel_dmc.c should be accessing dmc details directly.
>
> Need to add an i915_error_printf() stub for
> CONFIG_DRM_I915_CAPTURE_ERROR=n.
>
> v2: Add the stub (kernel test robot )
>
> Signed-off-by: Jani Nikula
> Reviewed-by: Lucas De Marchi # v1
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 01/12] drm/i915/dp: Extract
> intel_dp_tmds_clock_valid()
>
> From: Ville Syrjälä
>
> We're currently
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 04/12] drm/i915/dp:
> s/intel_dp_hdmi_ycbcr420/intel_dp_is_ycbcr420/
>
> From: Ville Syrjälä
>
>
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 06/12] drm/i915/dp: Pass around intel_connector
> rather than drm_connector
>
> From: Ville Syrjälä
>
>
> -Original Message-
> From: Intel-gfx On Behalf Of Ville
> Syrjala
> Sent: Tuesday, March 22, 2022 5:30 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v2 05/12] drm/i915/dp: Reorder
> intel_dp_compute_config() a bit
>
> From: Ville Syrjälä
>
> Consolidate
On Thu, Mar 31, 2022 at 05:20:21PM +0200, Daniel Vetter wrote:
> The stuff never really worked, and leads to lots of fun because it
> out-of-order frees atomic states. Which upsets KASAN, among other
> things.
>
> For async updates we now have a more solid solution with the
> ->atomic_async_check
On Thu, 31 Mar 2022, Jani Nikula wrote:
> v2 of https://patchwork.freedesktop.org/series/101931/
>
> Rebased, review comments addressed.
Ville, care to double check patches 1 & 7 please?
Thanks,
Jani.
>
> BR,
> Jani.
>
>
>
> Jani Nikula (12):
> drm/edid: use struct edid * in
== Series Details ==
Series: drm/i915/debugfs: Dump i915 children runtime status (rev2)
URL : https://patchwork.freedesktop.org/series/101866/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11437 -> Patchwork_22757
Summary
Extend the live migrate selftest, to verify the ccs surface clearing
during the Flat-CCS capable lmem obj clear.
v2:
Look at right places for ccs data [Thomas]
Signed-off-by: Ramalingam C
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/i915/gt/selftest_migrate.c | 250
Add a parameter called "extra_pages" for ttm_tt_init, to indicate that
driver needs extra pages in ttm_tt.
v2:
Used imperative wording [Thomas and Christian]
Signed-off-by: Ramalingam C
cc: Christian Koenig
cc: Hellstrom Thomas
Reviewed-by: Thomas Hellstrom
Reviewed-by: Christian Konig
On Xe-HP and later devices, dedicated compression control state (CCS)
stored in local memory is used for each surface, to support the
3D and media compression formats.
The memory required for the CCS of the entire local memory is 1/256 of
the local memory size. So before the kernel boot, the
When we are swapping out the local memory obj on flat-ccs capable platform,
we need to capture the ccs data too along with main meory and we need to
restore it when we are swapping in the content.
When lmem object is swapped into a smem obj, smem obj will
have the extra pages required to hold the
Xe-HP and latest devices support Flat CCS which reserved a portion of
the device memory to store compression metadata, during the clearing of
device memory buffer object we also need to clear the associated
CCS buffer.
XY_CTRL_SURF_COPY_BLT is a BLT cmd used for reading and writing the
ccs
Consider the possible round up happened at obj size alignment to
min_page_size during the obj allocation.
Signed-off-by: Ramalingam C
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/i915/gt/selftest_migrate.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
To make it uniform across copy and clear, use the engine offset directly
to calculate the offset in the cmd forming for emit_clear.
Signed-off-by: Ramalingam C
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/i915/gt/intel_migrate.c | 11 ---
1 file changed, 4 insertions(+), 7
Move the static calculations out of the loops for copy and clear.
Signed-off-by: Ramalingam C
Reviewed-by: Thomas Hellstrom
---
drivers/gpu/drm/i915/gt/intel_migrate.c | 40 -
1 file changed, 19 insertions(+), 21 deletions(-)
diff --git
Use faster XY_FAST_COLOR_BLT cmd on graphics version of 12 and more,
for clearing (Zero out) the pages of the newly allocated object.
XY_FAST_COLOR_BLT is faster than the older XY_COLOR_BLT.
v2:
Typo fix at title [Thomas]
v3:
XY_FAST_COLOR_BLT is used only for FLAT_CCS capable gen12+
On Xe-HP and later devices, we use dedicated compression control
state (CCS) stored in local memory for each surface, to support
the 3D and media compression formats.
The memory required for the CCS of the entire local memory is
1/256 of the local memory size. So before the kernel
boot, the
> -Original Message-
> From: Jani Nikula
> Sent: Friday, April 1, 2022 5:31 PM
> To: Dixit, Ashutosh ; Gupta, Anshuman
>
> Cc: intel-gfx@lists.freedesktop.org; Wilson, Chris P
> ;
> Vivi, Rodrigo
> Subject: Re: [Intel-gfx] [PATCH] drm/i915/debugfs: Dump i915 children runtime
>
On Tue, 29 Mar 2022, Bhanuprakash Modem wrote:
> This new debugfs will expose the connector's max supported bpc
> and the bpc currently using. It is very useful for verifying
> whether we enter the correct output color depth from IGT.
>
> Example:
> cat /sys/kernel/debug/dri/0/DP-1/output_bpc
>
On Mon, 28 Mar 2022, Anusha Srivatsa wrote:
> We need add some checks around DMC reloading to
> prevents the rare possibility of some adversary
> writing to a random mmio register
I've recently merged cleanup to localize all DMC register definitions to
a new file display/intel_dmc_regs.h, and
On Fri, 01 Apr 2022, "Gupta, Anshuman" wrote:
>> -Original Message-
>> From: Jani Nikula
>> Sent: Friday, April 1, 2022 5:31 PM
>> To: Dixit, Ashutosh ; Gupta, Anshuman
>>
>> Cc: intel-gfx@lists.freedesktop.org; Wilson, Chris P
>> ;
>> Vivi, Rodrigo
>> Subject: Re: [Intel-gfx] [PATCH]
On Mon, 21 Mar 2022, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Clean up a few random things that caught my eye.
Dunno if this got reviewed and merged already, but anyway, on the
series,
Reviewed-by: Jani Nikula
>
> Ville Syrjälä (3):
> drm/i915: Program i830 DPLL FP register later
>
The code of saving initial HW state snapshot has been moved into i915.
Let the GVT-g core logic use that snapshot.
Cc: Christoph Hellwig
Cc: Jason Gunthorpe
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Vivi Rodrigo
Cc: Zhenyu Wang
Cc: Zhi Wang
Signed-off-by: Zhi Wang
---
From: Zhi Wang
To support the new mdev interfaces and the re-factor patches from
Christoph, which moves the GVT-g code into a dedicated module, the GVT-g
MMIO tracking table needs to be separated from GVT-g.
---
v8:
- Use SPDX header in the intel_gvt_mmio_table.c
- Reference the gvt.h with
To support the new mdev interfaces and the re-factor patches from
Christoph, which moves the GVT-g code into a dedicated module, the GVT-g
initialization path has to be separated into two phases:
a) Early initialization.
The early initialization of GVT requires to be done when loading i915.
Save the initial HW state snapshot in i915 so that the rest code of GVT-g
can be moved into a dedicated module while it can still get a clean
initial HW state saved at the correct time during the initialization of
i915. The futhrer vGPU created by GVT-g will use this HW state as the
initial HW
> -Original Message-
> From: Jani Nikula
> Sent: Friday, April 1, 2022 6:26 PM
> To: Gupta, Anshuman ; Dixit, Ashutosh
>
> Cc: intel-gfx@lists.freedesktop.org; Wilson, Chris P
> ;
> Vivi, Rodrigo
> Subject: RE: [Intel-gfx] [PATCH] drm/i915/debugfs: Dump i915 children runtime
>
Hi Jani:
Thanks so much for the guidance. :) I included it in the v8 patch. :)
Thanks,
Zhi.
On 3/31/22 8:25 AM, Jani Nikula wrote:
> On Thu, 31 Mar 2022, "Wang, Zhi A" wrote:
>> Hi Jani and Joonas:
>>
>> Are you OK with these patches? I noticed I need to change the license
>> of the new file.
On Thu, Mar 31, 2022 at 05:05:31PM +0300, Ville Syrjälä wrote:
> On Thu, Mar 31, 2022 at 04:59:11PM +0300, Jani Nikula wrote:
> > On Thu, 31 Mar 2022, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > Nothing special about static DRRS on LVDS, it's just your
> > > bog standard modeset.
== Series Details ==
Series: drm/i915/ttm: Evict and restore of compressed object (rev7)
URL : https://patchwork.freedesktop.org/series/101106/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11438_full -> Patchwork_22758_full
== Series Details ==
Series: Per client GPU utilisation (rev4)
URL : https://patchwork.freedesktop.org/series/100573/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Hi Chirs:
Thanks for the testing. I will find a kabelake and try it. :)
-Original Message-
From: Christoph Hellwig
Sent: Friday, April 1, 2022 8:22 PM
To: Zhi Wang
Cc: dri-de...@lists.freedesktop.org; linux-ker...@vger.kernel.org;
intel-gfx@lists.freedesktop.org;
== Series Details ==
Series: Per client GPU utilisation (rev5)
URL : https://patchwork.freedesktop.org/series/100573/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/gem/i915_gem_context_types.h:417: warning: Function
parameter or member
Hi "José,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on v5.17 next-20220401]
[cannot apply to drm-intel/for-linux-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submi
== Series Details ==
Series: Per client GPU utilisation (rev5)
URL : https://patchwork.freedesktop.org/series/100573/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11440 -> Patchwork_22761
Summary
---
**SUCCESS**
Daniel Vetter writes:
> On Wed, Mar 30, 2022 at 02:53:11PM -0700, Matt Atwood wrote:
>> Newer platforms have DSS that aren't necessarily available for both
>> geometry and compute, two queries will need to exist. This introduces
>> the first, when passing a valid engine class and engine instance
Hi "José,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[also build test WARNING on v5.17 next-20220401]
[cannot apply to drm-intel/for-linux-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submi
== Series Details ==
Series: Per client GPU utilisation (rev5)
URL : https://patchwork.freedesktop.org/series/100573/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7e9efd72439e drm/i915: Explicitly track DRM clients
-:130: WARNING:FILE_PATH_CHANGES: added, moved or deleted
== Series Details ==
Series: drm/i915/dsb: modified to drm_info in dsb_prepare() (rev3)
URL : https://patchwork.freedesktop.org/series/101723/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11407_full -> Patchwork_22688_full
== Series Details ==
Series: series starting with [1/3] drm/i915/display/psr: Set partial frame
enable when forcing full frame fetch
URL : https://patchwork.freedesktop.org/series/102095/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
== Series Details ==
Series: series starting with [1/3] drm/i915/display/psr: Set partial frame
enable when forcing full frame fetch
URL : https://patchwork.freedesktop.org/series/102095/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11440 -> Patchwork_22762
== Series Details ==
Series: series starting with [1/3] drm/i915/display/psr: Set partial frame
enable when forcing full frame fetch
URL : https://patchwork.freedesktop.org/series/102095/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11440_full -> Patchwork_22762_full
Frontbuffer rendering and page flips can race with each other
and this can potentialy cause issues with PSR2 selective fetch.
And because pipe/crtc updates are time sentive we can't grab the
PSR lock after intel_pipe_update_start() and before
intel_pipe_update_end().
So here adding the lock and
Following up what was done in commit 804f46885317 ("drm/i915/psr: Set
"SF Partial Frame Enable" also on full update") and also setting
partial frame enable when psr_force_hw_tracking_exit() is called.
Also as PSR2_MAN_TRK_CTL is a double buffered registers do a RMW
is not a good idea so here also
Instead of exit PSR when a frontbuffer invalidation happens, we can
enable the PSR2 selective fetch continuous full frame, that will keep
the panel updated like PSR was disabled but without keeping PSR active.
So as soon as the frontbuffer flush happens we can disable the
continuous full frame
== Series Details ==
Series: Per client GPU utilisation (rev5)
URL : https://patchwork.freedesktop.org/series/100573/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/dsb: modified to drm_info in dsb_prepare() (rev3)
URL : https://patchwork.freedesktop.org/series/101723/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11407_full -> Patchwork_22688_full
== Series Details ==
Series: Per client GPU utilisation (rev5)
URL : https://patchwork.freedesktop.org/series/100573/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11440_full -> Patchwork_22761_full
Summary
---
From: Tvrtko Ursulin
Proposal to standardise the fdinfo text format as optionally output by DRM
drivers.
Idea is that a simple but, well defined, spec will enable generic
userspace tools to be written while at the same time avoiding a more heavy
handed approach of adding a mid-layer to DRM.
From: Tvrtko Ursulin
As contexts are abandoned we want to remember how much GPU time they used
(per class) so later we can used it for smarter purposes.
As GEM contexts are closed we want to have the DRM client remember how
much GPU time they used (per class) so later we can used it for smarter
From: Tvrtko Ursulin
We soon want to start answering questions like how much GPU time is the
context belonging to a client which exited still using.
To enable this we start tracking all context belonging to a client on a
separate list.
Signed-off-by: Tvrtko Ursulin
Reviewed-by: Aravind
From: Tvrtko Ursulin
Track context active (on hardware) status together with the start
timestamp.
This will be used to provide better granularity of context
runtime reporting in conjunction with already tracked pphwsp accumulated
runtime.
The latter is only updated on context save so does not
From: Tvrtko Ursulin
This will be useful to have at hand in a following patch.
Signed-off-by: Tvrtko Ursulin
Reviewed-by: Umesh Nerlige Ramappa
---
drivers/gpu/drm/i915/gt/intel_engine_user.c | 11 ++-
drivers/gpu/drm/i915/i915_drv.h | 1 +
2 files changed, 7
From: Tvrtko Ursulin
Similar to AMD commit
874442541133 ("drm/amdgpu: Add show_fdinfo() interface"), using the
infrastructure added in previous patches, we add basic client info
and GPU engine utilisation for i915.
Example of the output:
pos:0
flags: 012
mnt_id: 21
drm-driver:
From: Tvrtko Ursulin
Test-with: 20220401141155.3122817-1-tvrtko.ursu...@linux.intel.com
Tvrtko Ursulin (8):
drm/i915: Explicitly track DRM clients
drm/i915: Make GEM contexts track DRM clients
drm/i915: Track runtime spent in closed and unreachable GEM contexts
drm/i915: Track all user
From: Tvrtko Ursulin
Tracking DRM clients more explicitly will allow later patches to
accumulate past and current GPU usage in a centralised place and also
consolidate access to owning task pid/name.
Unique client id is also assigned for the purpose of distinguishing/
consolidating between
From: Tvrtko Ursulin
Make GEM contexts keep a reference to i915_drm_client for the whole of
of their lifetime which will come handy in following patches.
v2: Don't bother supporting selftests contexts from debugfs. (Chris)
v3 (Lucas): Finish constructing ctx before adding it to the list
v4
== Series Details ==
Series: Per client GPU utilisation (rev4)
URL : https://patchwork.freedesktop.org/series/100573/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
037908479101 drm/i915: Explicitly track DRM clients
-:130: WARNING:FILE_PATH_CHANGES: added, moved or deleted
On Fri, 01 Apr 2022, Ville Syrjälä wrote:
> On Fri, Apr 01, 2022 at 11:55:21AM +0300, Jani Nikula wrote:
>> On Thu, 31 Mar 2022, Jani Nikula wrote:
>> > v2 of https://patchwork.freedesktop.org/series/101931/
>> >
>> > Rebased, review comments addressed.
>>
>> Ville, care to double check patches
== Series Details ==
Series: Per client GPU utilisation (rev4)
URL : https://patchwork.freedesktop.org/series/100573/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11439 -> Patchwork_22760
Summary
---
**FAILURE**
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: e797b8d09704b91463456234efdf04dc8f8c385d
commit: edc1a46d62b7a03d53067f598db831092f9e1b05 [4/8] Merge remote-tracking
branch 'drm-misc/drm-misc-next' into drm-tip
config: arm-randconfig-r033-20220401
(https://download.01.org/0day
On 2022-04-01 at 15:59:01 +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/ttm: Evict and restore of compressed object (rev7)
> URL : https://patchwork.freedesktop.org/series/101106/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_11438_full ->
From: Tvrtko Ursulin
Only first three patches for review purposes (first stage) - adding the test and
intel_gpu_top support.
Tvrtko Ursulin (3):
lib: Helper library for parsing i915 fdinfo output
tests/i915/drm_fdinfo: Basic and functional tests for GPU busyness
exported via fdinfo
From: Tvrtko Ursulin
Tests and intel_gpu_top will share common code for parsing this file.
v2:
* Fix key-value parsing if valid key line ends with ':'.
* Return number of drm keys found.
* Add DRM_CLIENT_FDINFO_MAX_ENGINES. (Umesh)
* Always zero terminate read buffer. (Umesh)
== Series Details ==
Series: Refactor GVT-g MMIO tracking table and handlers
URL : https://patchwork.freedesktop.org/series/102073/
State : failure
== Summary ==
CALLscripts/checksyscalls.sh
CALLscripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
== Series Details ==
Series: drm/i915/dsb: modified to drm_info in dsb_prepare() (rev3)
URL : https://patchwork.freedesktop.org/series/101723/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11407_full -> Patchwork_22688_full
From: Tvrtko Ursulin
Mostly inherited from the perf_pmu, some basic tests, and some tests to
verify exported GPU busyness is as expected.
v2:
* Skip when kernel does not export drm keys in fdinfo.
Signed-off-by: Tvrtko Ursulin
Reviewed-by: Umesh Nerlige Ramappa
---
tests/i915/drm_fdinfo.c
On Fri, Apr 01, 2022 at 10:43:19AM +0300, Jani Nikula wrote:
On Wed, 30 Mar 2022, Jani Nikula wrote:
Only intel_dmc.c should be accessing dmc details directly.
Need to add an i915_error_printf() stub for
CONFIG_DRM_I915_CAPTURE_ERROR=n.
v2: Add the stub (kernel test robot )
Signed-off-by:
From: Tvrtko Ursulin
Use the i915 exported data in /proc//fdinfo to show GPU utilization
per DRM client.
Example of the output:
intel-gpu-top: Intel Tigerlake (Gen12) @ /dev/dri/card0 - 220/ 221 MHz
70% RC6; 0.62/ 7.08 W; 760 irqs/s
ENGINES BUSY
== Series Details ==
Series: drm/i915/ttm: Evict and restore of compressed object (rev7)
URL : https://patchwork.freedesktop.org/series/101106/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11438 -> Patchwork_22758
Summary
On 31/03/2022 23:08, Umesh Nerlige Ramappa wrote:
lgtm, I just have a few nits and questions below:
Regardless, this is
Reviewed-by: Umesh Nerlige Ramappa
Thanks!
I've sent the updated series with only first three patches for first
stage. Only first patch misses the r-b now.
Rest of
> -Original Message-
> From: Jani Nikula
> Sent: Friday, April 1, 2022 7:40 PM
> To: Gupta, Anshuman ; Dixit, Ashutosh
>
> Cc: intel-gfx@lists.freedesktop.org; Wilson, Chris P
> ;
> Vivi, Rodrigo
> Subject: RE: [Intel-gfx] [PATCH] drm/i915/debugfs: Dump i915 children runtime
>
Christian, Joonas and vivi
Once the premerge results are greeen, if this patch can be merged into
drm-intel-gt-next along with other patches could you please ack the
request to merge into drm-intel-gt-next?
Thanks
Ram
On 2022-04-01 at 18:07:49 +0530, Ramalingam C wrote:
> Add a parameter called
lgtm, thanks for clarifications on the other patch.
Reviewed-by: Umesh Nerlige Ramappa
Umesh
On Fri, Apr 01, 2022 at 03:11:53PM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Tests and intel_gpu_top will share common code for parsing this file.
v2:
* Fix key-value parsing if valid key
== Series Details ==
Series: Per client GPU utilisation (rev4)
URL : https://patchwork.freedesktop.org/series/100573/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/gem/i915_gem_context_types.h:417: warning: Function
parameter or member
== Series Details ==
Series: drm/i915/dsb: modified to drm_info in dsb_prepare() (rev3)
URL : https://patchwork.freedesktop.org/series/101723/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11407 -> Patchwork_22688
Summary
This version still seems unhappy (same hardware as the last report):
[ 38.650768] vfio_mdev 6814f392-50ac-4236-ae3d-26d472fd8aae: Adding to iommu
group 0
[ 38.880317] L1TF CPU bug present and SMT on, data leak possible. See
CVE-2018-3646 and
== Series Details ==
Series: Splitting intel-gtt calls for non-x86 platforms (rev7)
URL : https://patchwork.freedesktop.org/series/101552/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11440 -> Patchwork_22763
Summary
== Series Details ==
Series: Splitting intel-gtt calls for non-x86 platforms (rev7)
URL : https://patchwork.freedesktop.org/series/101552/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
270de0551c0b drm/i915/gt: Split intel-gtt functions by arch
-:368:
On 2022-04-01 at 16:31:19 +0200, Christian König wrote:
> I would be nicer to push this through drm-misc-next, but the intel branch
> works for me as well.
Hi Christian
I have pushed this patch into drm-misc-next.
Regards,
Ram.
>
> Regards,
> Christian.
>
> Am 01.04.22 um 16:28 schrieb
== Series Details ==
Series: drm/i915/rps: Centralize computation of freq caps (rev5)
URL : https://patchwork.freedesktop.org/series/101606/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Tue, Mar 22, 2022 at 02:14:37PM +0530, Mullati Siva wrote:
From: Siva Mullati
Convert CT commands and descriptors to use iosys_map rather
than plain pointer and save it in the intel_guc_ct_buffer struct.
This will help with ct_write and ct_read for cmd send and receive
after the
== Series Details ==
Series: drm/i915/rps: Centralize computation of freq caps (rev5)
URL : https://patchwork.freedesktop.org/series/101606/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11441 -> Patchwork_22764
Summary
== Series Details ==
Series: Splitting intel-gtt calls for non-x86 platforms (rev7)
URL : https://patchwork.freedesktop.org/series/101552/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On 2022-03-16 at 11:25:33 +0200, Jani Nikula wrote:
> On Sun, 20 Feb 2022, Anshuman Gupta wrote:
> > Abstract opregion operations like get opregion base, get rvda and
> > opregion cleanup in form of i915_opregion_ops.
> > This will be required to converge igfx and dgfx opregion.
> >
> > v2:
> > -
== Series Details ==
Series: drm/i915/ttm: Evict and restore of compressed object (rev7)
URL : https://patchwork.freedesktop.org/series/101106/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c7781263ce21 drm/i915/gt: use engine instance directly for offset
4b35aa78c844
== Series Details ==
Series: drm/i915/ttm: Evict and restore of compressed object (rev7)
URL : https://patchwork.freedesktop.org/series/101106/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Fri, 01 Apr 2022, "Gupta, Anshuman" wrote:
>> -Original Message-
>> From: Jani Nikula
>> Sent: Friday, April 1, 2022 6:26 PM
>> To: Gupta, Anshuman ; Dixit, Ashutosh
>>
>> Cc: intel-gfx@lists.freedesktop.org; Wilson, Chris P
>> ;
>> Vivi, Rodrigo
>> Subject: RE: [Intel-gfx] [PATCH]
1 - 100 of 106 matches
Mail list logo
