On Fri, Jul 15, 2022 at 12:19:37PM +0100, Matthew Auld wrote:
> The object here could be very large (8G+), so make sure we allow using
> the entire address space, to avoid sometimes hitting -ENOSPC.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/6446
> Signed-off-by: Matthew Auld
>
Reviewed-by: Nirmoy Das
On 7/15/2022 1:19 PM, Matthew Auld wrote:
The object here could be very large (8G+), so make sure we allow using
the entire address space, to avoid sometimes hitting -ENOSPC.
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/6446
Signed-off-by: Matthew Auld
Cc:
Hi,
On 15/07/2022 23:54, Daniele Ceraolo Spurio wrote:
This patch re-introduces support for GuC v69 in parallel to v70. As this
is a quick fix, v69 has been re-introduced as the single "fallback" guc
version in case v70 is not available on disk. All v69 specific code has
been labeled as such f
On 01/07/2022 23:50, Niranjana Vishwanathapura wrote:
Bind and unbind the mappings upon VM_BIND and VM_UNBIND calls.
Signed-off-by: Niranjana Vishwanathapura
Signed-off-by: Prathap Kumar Valsan
---
drivers/gpu/drm/i915/Makefile | 1 +
drivers/gpu/drm/i915/gem/i915_gem_cr
> -Original Message-
> From: Ville Syrjälä
> Sent: Monday, July 4, 2022 7:41 PM
> To: Murthy, Arun R
> Cc: intel-gfx@lists.freedesktop.org; Zanoni, Paulo R
> ; tprev...@gmail.com; Shankar, Uma
> ; Nikula, Jani
> Subject: Re: [PATCH] drm/i915/dp: wait on timeout before retry
>
> On Mon,
On 09/07/2022 00:48, Daniele Ceraolo Spurio wrote:
The current HuC status getparam return values are a bit confusing in
regards to what happens in some scenarios. In particular, most of the
error cases cause the ioctl to return an error, but a couple of them,
INIT_FAIL and LOAD_FAIL, are not ex
Hi,
On 12/07/2022 06:00, Christoph Hellwig wrote:
On Mon, Jul 11, 2022 at 04:31:49PM -0400, Rodrigo Vivi wrote:
On Mon, Jul 11, 2022 at 10:26:14AM +0200, Christoph Hellwig wrote:
Hi i915 and nouveau maintainers,
any chance I could get some help to remove the remaining direct
driver calls in
On Fri, 15 Jul 2022 15:16:05 -0700
Joe Perches wrote:
> On Fri, 2022-07-15 at 17:35 -0400, Rodrigo Vivi wrote:
> > On Wed, Jul 13, 2022 at 09:12:12AM +0100, Mauro Carvalho Chehab wrote:
> > > This file is licensed with MIT license. Change its license text
> > > to use SPDX.
> > >
> > > Signe
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: Matthew Brost
Remove bogus GEM_BUG_ON which compared kernel context timeline seqno to
seqno in memory on engine PM unpark. If a GT reset occurred these values
might not match as a kernel context could be skipped. This bug was
hidden
On Sat, Jun 18, 2022 at 12:50:26AM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/tgl+: Fix HDMI transcoder clock vs. DDI BUF disabling order
> URL : https://patchwork.freedesktop.org/series/105290/
> State : failure
Thanks for the review, patch pushed to drm-intel-next. Th
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: Matthew Brost
The engine registers really shouldn't be touched during GuC submission
as the GuC owns the registers. Don't call ring_is_idle and tie
Touch being just read and it is somehow harmful?
intel_engine_is_idle strictly to
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: Matthew Brost
The GuC needs a copy of a golden context for implementing watchdog
resets (aka media resets). This context is larger on newer platforms.
So adjust the size being allocated/copied accordingly.
What were the consequence
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: John Harrison
When the KMD sends a CLIENT_RESET request to GuC (as part of the
suspend sequence), GuC will mark the CTB buffer as 'UNUSED'. If the
KMD then checked the CTB queue, it would see a non-zero status value
and report the bu
On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
From: Chris Wilson
Check if the device is powered down prior to any engine activity,
as, on such cases, all the TLBs were already invalidated, so an
explicit TLB invalidation is not needed, thus reducing the
performance regression impact due t
On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
Add a kernel-doc markup to document this new macro.
Signed-off-by: Mauro Carvalho Chehab
---
To avoid mailbombing on a large number of people, only mailing lists were C/C
on the cover.
See [PATCH v2 00/21] at:
https://lore.kernel.org/all/co
On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
From: Chris Wilson
Ensure that the TLB of the OA unit is also invalidated
on gen12 HW, as just invalidating the TLB of an engine is not
enough.
Cc: sta...@vger.kernel.org
Fixes: 7938d61591d3 ("drm/i915: Flush TLBs before releasing backing sto
On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
From: Chris Wilson
Don't flush TLBs when the buffer is only used in the GGTT under full
control of the kernel, as there's no risk of concurrent access
and stale access from prefetch.
We only need to invalidate the TLB if they are accessible b
On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
From: Chris Wilson
Skip all further TLB invalidations once the device is wedged and
had been reset, as, on such cases, it can no longer process instructions
on the GPU and the user no longer has access to the TLB's in each engine.
That helps
>
> On Wed, Jul 06, 2022 at 02:43:33PM +0300, Alexander Usyskin wrote:
> > Add slow_fw flag to the mei auxiliary device info to inform the mei
> > driver about slow underlying firmware.
> > Such firmware will require to use larger operation timeouts.
> >
> > Signed-off-by: Alexander Usyskin
> >
On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
From: Chris Wilson
Invalidate TLB in patch, in order to reduce performance regressions.
"in batches"?
Currently, every caller performs a full barrier around a TLB
invalidation, ignoring all other invalidations that may have already
removed
On Mon, 18 Jul 2022 14:16:10 +0100
Tvrtko Ursulin wrote:
> On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
> > From: Chris Wilson
> >
> > Check if the device is powered down prior to any engine activity,
> > as, on such cases, all the TLBs were already invalidated, so an
> > explicit TLB inva
On 18/07/2022 15:53, Mauro Carvalho Chehab wrote:
On Mon, 18 Jul 2022 14:16:10 +0100
Tvrtko Ursulin wrote:
On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
From: Chris Wilson
Check if the device is powered down prior to any engine activity,
as, on such cases, all the TLBs were already in
From: Mauro Carvalho Chehab
> Sent: 18 July 2022 15:54
>
> On Mon, 18 Jul 2022 14:16:10 +0100
> Tvrtko Ursulin wrote:
>
> > On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
> > > From: Chris Wilson
> > >
> > > Check if the device is powered down prior to any engine activity,
> > > as, on such
On Mon, 18 Jul 2022 14:39:17 +0100
Tvrtko Ursulin wrote:
> On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
> > From: Chris Wilson
> >
> > Don't flush TLBs when the buffer is only used in the GGTT under full
> > control of the kernel, as there's no risk of concurrent access
> > and stale acces
On Mon, 18 Jul 2022 14:45:22 +0100
Tvrtko Ursulin wrote:
> On 14/07/2022 13:06, Mauro Carvalho Chehab wrote:
> > From: Chris Wilson
> >
> > Skip all further TLB invalidations once the device is wedged and
> > had been reset, as, on such cases, it can no longer process instructions
> > on the GP
On 7/18/2022 3:02 AM, Tvrtko Ursulin wrote:
Hi,
On 15/07/2022 23:54, Daniele Ceraolo Spurio wrote:
This patch re-introduces support for GuC v69 in parallel to v70. As this
is a quick fix, v69 has been re-introduced as the single "fallback" guc
version in case v70 is not available on disk. A
On 7/18/2022 4:26 AM, Tvrtko Ursulin wrote:
On 09/07/2022 00:48, Daniele Ceraolo Spurio wrote:
The current HuC status getparam return values are a bit confusing in
regards to what happens in some scenarios. In particular, most of the
error cases cause the ioctl to return an error, but a coup
On Mon, Jul 18, 2022 at 11:02:03AM +0100, Tvrtko Ursulin wrote:
>
> Hi,
>
> On 15/07/2022 23:54, Daniele Ceraolo Spurio wrote:
> > This patch re-introduces support for GuC v69 in parallel to v70. As this
> > is a quick fix, v69 has been re-introduced as the single "fallback" guc
> > version in ca
On Fri, Jul 15, 2022 at 01:19:53PM +0800, Jason Wang wrote:
> The double `wait' is duplicated in line 974, remove one.
The line number changes... if you remove the "in line #"
the msg gets better.
With that changed:
Reviewed-by: Rodrigo Vivi
>
> Signed-off-by: Jason Wang
> ---
> drivers/gp
On Sun, Jul 17, 2022 at 02:44:39AM +0800, Jason Wang wrote:
> The semicolon after the `}' in line 648 is unneeded.
same here
The line number changes... if you remove the "in line #"
the msg gets better.
With that changed:
Reviewed-by: Rodrigo Vivi
>
> Signed-off-by: Jason Wang
> ---
> driver
gen11_gu_misc_irq_handler() does not do anything tile specific.
Cc: Matt Roper
Signed-off-by: Anusha Srivatsa
---
drivers/gpu/drm/i915/i915_irq.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index 7
On Mon, Jul 18, 2022 at 11:34:24AM -0700, Anusha Srivatsa wrote:
> gen11_gu_misc_irq_handler() does not do anything tile specific.
>
> Cc: Matt Roper
> Signed-off-by: Anusha Srivatsa
Reviewed-by: Matt Roper
> ---
> drivers/gpu/drm/i915/i915_irq.c | 8
> 1 file changed, 4 insertions(
No functional change. Cleanup the intel_phy_is_combo
to accomodate for cases where combo phy is not available.
Cc: Matt Roper
Signed-off-by: Anusha Srivatsa
---
drivers/gpu/drm/i915/display/intel_display.c | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/gpu/d
== Series Details ==
Series: drm/i915: Pass drm_i915_private struct instead of gt for
gen11_gu_misc_irq_handler()
URL : https://patchwork.freedesktop.org/series/106449/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11915 -> Patchwork_106449v1
=
== Series Details ==
Series: drm/i915/display: Cleanup intel_phy_is_combo()
URL : https://patchwork.freedesktop.org/series/106450/
State : warning
== Summary ==
Error: dim checkpatch failed
69c232c23b9b drm/i915/display: Cleanup intel_phy_is_combo()
-:7: WARNING:TYPO_SPELLING: 'accomodate' may
== Series Details ==
Series: drm/i915/display: Cleanup intel_phy_is_combo()
URL : https://patchwork.freedesktop.org/series/106450/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11915 -> Patchwork_106450v1
Summary
---
On 7/15/2022 15:54, Daniele Ceraolo Spurio wrote:
This patch re-introduces support for GuC v69 in parallel to v70. As this
is a quick fix, v69 has been re-introduced as the single "fallback" guc
version in case v70 is not available on disk. All v69 specific code has
been labeled as such for easy
On 7/18/2022 2:19 PM, John Harrison wrote:
On 7/15/2022 15:54, Daniele Ceraolo Spurio wrote:
This patch re-introduces support for GuC v69 in parallel to v70. As this
is a quick fix, v69 has been re-introduced as the single "fallback" guc
version in case v70 is not available on disk. All v69 s
This patch re-introduces support for GuC v69 in parallel to v70. As this
is a quick fix, v69 has been re-introduced as the single "fallback" guc
version in case v70 is not available on disk and only for platforms that
are out of force_probe and require the GuC by default. All v69 specific
code has
== Series Details ==
Series: drm/i915/guc: support v69 in parallel to v70
URL : https://patchwork.freedesktop.org/series/106457/
State : warning
== Summary ==
Error: dim checkpatch failed
5b8282554b81 drm/i915/guc: support v69 in parallel to v70
-:742: ERROR:COMPLEX_MACRO: Macros with complex
== Series Details ==
Series: drm/i915/guc: support v69 in parallel to v70
URL : https://patchwork.freedesktop.org/series/106457/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915: Pass drm_i915_private struct instead of gt for
gen11_gu_misc_irq_handler()
URL : https://patchwork.freedesktop.org/series/106449/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11915_full -> Patchwork_106449v1_full
===
== Series Details ==
Series: drm/i915/guc: support v69 in parallel to v70
URL : https://patchwork.freedesktop.org/series/106457/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11915 -> Patchwork_106457v1
Summary
---
*
On 7/18/2022 05:15, Tvrtko Ursulin wrote:
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: Matthew Brost
Remove bogus GEM_BUG_ON which compared kernel context timeline seqno to
seqno in memory on engine PM unpark. If a GT reset occurred these values
might not match as a kernel cont
On 7/18/2022 05:26, Tvrtko Ursulin wrote:
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: Matthew Brost
The engine registers really shouldn't be touched during GuC submission
as the GuC owns the registers. Don't call ring_is_idle and tie
Touch being just read and it is somehow h
On 7/18/2022 05:35, Tvrtko Ursulin wrote:
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: Matthew Brost
The GuC needs a copy of a golden context for implementing watchdog
resets (aka media resets). This context is larger on newer platforms.
So adjust the size being allocated/copie
On 7/18/2022 05:36, Tvrtko Ursulin wrote:
On 13/07/2022 00:31, john.c.harri...@intel.com wrote:
From: John Harrison
When the KMD sends a CLIENT_RESET request to GuC (as part of the
suspend sequence), GuC will mark the CTB buffer as 'UNUSED'. If the
KMD then checked the CTB queue, it would see
Create a gt/gtN/.defaults/ directory (similar to
engine//.defaults/) to expose default parameter values for each
gt in sysfs. This allows userspace to restore default parameter values
after they may have changed.
Patch 1: Creates the gt/gtN/.defaults/ directory
Patch 2: Adds per-gt RPS defaults (r
Add the following sysfs files to gt/gtN/.defaults/:
* rps_min_freq_mhz
* rps_max_freq_mhz
v2: Correct gt/gtN/.defaults/* file names in commit message
v3: Remove rps_boost_freq_mhz since it is not consumed by userspace
Cc: Tvrtko Ursulin
Cc: Andi Shyti
Signed-off-by: Ashutosh Dixit
Reviewed-by:
Create a gt/gtN/.defaults/ directory (similar to
engine//.defaults/) to expose default parameter values for
each gt in sysfs. This allows userspace to restore default parameter values
after they have changed. The empty 'struct gt_defaults' will be populated
by subsequent patches.
v2: Changed 'stru
On Thu, 02 Jun 2022 16:55:50 -0700, Matt Roper wrote:
>
> On Thu, Jun 02, 2022 at 04:36:02PM -0700, Dixit, Ashutosh wrote:
> > On Fri, 27 May 2022 16:41:28 -0700, Matt Roper wrote:
> > >
> > > On Thu, May 26, 2022 at 12:00:42PM -0700, Ashutosh Dixit wrote:
> > > > Create a gt/gtN/.defaults director
== Series Details ==
Series: drm/i915/gt: Expose per gt defaults in sysfs
URL : https://patchwork.freedesktop.org/series/106460/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/display: Cleanup intel_phy_is_combo()
URL : https://patchwork.freedesktop.org/series/106450/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11915_full -> Patchwork_106450v1_full
Summary
== Series Details ==
Series: drm/i915/gt: Expose per gt defaults in sysfs
URL : https://patchwork.freedesktop.org/series/106460/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11915 -> Patchwork_106460v1
Summary
---
*
> -Original Message-
> From: Nautiyal, Ankit K
> Sent: Friday, July 8, 2022 3:36 PM
> To: Murthy, Arun R ; intel-
> g...@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915/hdmi: Prune modes that require
> HDMI2.1 FRL
>
> Hi Arun,
>
> Thanks for the comments.
>
> Please fi
> -Original Message-
> From: Intel-gfx On Behalf Of
> Anusha Srivatsa
> Sent: Tuesday, July 19, 2022 12:42 AM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH] drm/i915/display: Cleanup intel_phy_is_combo()
>
> No functional change. Cleanup the intel_phy_is_combo to acc
On Mon, 09 May 2022 14:01:46 -0700, Alan Previn wrote:
>
> When GuC-Error-Capture was introduced, we created
> buf_in_use as a way to identify if relay logging
> had started. It is meant to replace the previous
> method where a mmap of the GuC log buffer was
Let's change mmap to something else sin
== Series Details ==
Series: drm/i915/guc: support v69 in parallel to v70
URL : https://patchwork.freedesktop.org/series/106457/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11915_full -> Patchwork_106457v1_full
Summary
--
On 7/19/2022 8:45 AM, Murthy, Arun R wrote:
-Original Message-
From: Nautiyal, Ankit K
Sent: Friday, July 8, 2022 3:36 PM
To: Murthy, Arun R ; intel-
g...@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/hdmi: Prune modes that require
HDMI2.1 FRL
Hi Arun,
Thanks for th
== Series Details ==
Series: drm/i915/gt: Expose per gt defaults in sysfs
URL : https://patchwork.freedesktop.org/series/106460/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11915_full -> Patchwork_106460v1_full
Summary
--
60 matches
Mail list logo
