Re: [Intel-gfx] [PATCH 47/47] drm/i915/guc: Unblock GuC submission on Gen11+

On 02/07/2021 18:07, Michal Wajdeczko wrote: On 02.07.2021 10:09, Martin Peres wrote: On 02/07/2021 10:29, Pekka Paalanen wrote: On Thu, 1 Jul 2021 21:28:06 +0200 Daniel Vetter wrote: On Thu, Jul 1, 2021 at 8:27 PM Martin Peres wrote: On 01/07/2021 11:14, Pekka Paalanen wrote: On Wed

Re: [Intel-gfx] [PATCH 47/47] drm/i915/guc: Unblock GuC submission on Gen11+

On 02/07/2021 16:06, Michal Wajdeczko wrote: On 02.07.2021 10:13, Martin Peres wrote: On 01/07/2021 21:24, Martin Peres wrote: [...] +    i915->params.enable_guc = ENABLE_GUC_LOAD_HUC; +    return; +    } + +    /* Default: enable HuC authentication and GuC submiss

Re: [Intel-gfx] [PATCH 47/47] drm/i915/guc: Unblock GuC submission on Gen11+

On 01/07/2021 21:24, Martin Peres wrote: [...] +    i915->params.enable_guc = ENABLE_GUC_LOAD_HUC; +    return; +    } + +    /* Default: enable HuC authentication and GuC submission */ +    i915->params.enable_guc = ENABLE_GUC_LOAD_HUC | ENABLE_GUC_SUBMISSION; This

Re: [Intel-gfx] [PATCH 47/47] drm/i915/guc: Unblock GuC submission on Gen11+

On 02/07/2021 10:29, Pekka Paalanen wrote: On Thu, 1 Jul 2021 21:28:06 +0200 Daniel Vetter wrote: On Thu, Jul 1, 2021 at 8:27 PM Martin Peres wrote: On 01/07/2021 11:14, Pekka Paalanen wrote: On Wed, 30 Jun 2021 11:58:25 -0700 John Harrison wrote: On 6/30/2021 01:22, Martin Peres

Re: [Intel-gfx] [PATCH 47/47] drm/i915/guc: Unblock GuC submission on Gen11+

On 01/07/2021 11:14, Pekka Paalanen wrote: On Wed, 30 Jun 2021 11:58:25 -0700 John Harrison wrote: On 6/30/2021 01:22, Martin Peres wrote: On 24/06/2021 10:05, Matthew Brost wrote: From: Daniele Ceraolo Spurio Unblock GuC submission on Gen11+ platforms. Signed-off-by: Michal Wajdeczko

Re: [Intel-gfx] [PATCH 47/47] drm/i915/guc: Unblock GuC submission on Gen11+

On 30/06/2021 21:00, Matthew Brost wrote: On Wed, Jun 30, 2021 at 11:22:38AM +0300, Martin Peres wrote: On 24/06/2021 10:05, Matthew Brost wrote: From: Daniele Ceraolo Spurio Unblock GuC submission on Gen11+ platforms. Signed-off-by: Michal Wajdeczko Signed-off-by: Daniele Ceraolo Spurio

Re: [Intel-gfx] [PATCH 2/2] drm/doc/rfc: i915 new parallel submission uAPI plan

On 29/06/2021 22:35, Matthew Brost wrote: Add entry for i915 new parallel submission uAPI plan. v2: (Daniel Vetter): - Expand logical order explaination - Add dummy header - Only allow N BBs in execbuf IOCTL - Configure parallel submission per slot not per gem context v3:

Re: [Intel-gfx] [PATCH 47/47] drm/i915/guc: Unblock GuC submission on Gen11+

On 24/06/2021 10:05, Matthew Brost wrote: From: Daniele Ceraolo Spurio Unblock GuC submission on Gen11+ platforms. Signed-off-by: Michal Wajdeczko Signed-off-by: Daniele Ceraolo Spurio Signed-off-by: Matthew Brost --- drivers/gpu/drm/i915/gt/uc/intel_guc.h| 1 +

Re: [Intel-gfx] [PATCH 1/2] drm/doc/rfc: i915 GuC submission / DRM scheduler

On 29/06/2021 22:35, Matthew Brost wrote: Add entry for i915 GuC submission / DRM scheduler integration plan. Follow up patch with details of new parallel submission uAPI to come. v2: (Daniel Vetter) - Expand explaination of why bonding isn't supported for GuC submission - CC some

Re: [Intel-gfx] [RFC PATCH 00/97] Basic GuC submission support in the i915

On 11/05/2021 19:39, Matthew Brost wrote: On Tue, May 11, 2021 at 08:26:59AM -0700, Bloomfield, Jon wrote: -Original Message- From: Martin Peres Sent: Tuesday, May 11, 2021 1:06 AM To: Daniel Vetter Cc: Jason Ekstrand ; Brost, Matthew ; intel-gfx ; dri-devel ; Ursulin, Tvrtko

Re: [Intel-gfx] [RFC PATCH 00/97] Basic GuC submission support in the i915

On 10/05/2021 19:33, Daniel Vetter wrote: On Mon, May 10, 2021 at 3:55 PM Martin Peres wrote: On 10/05/2021 02:11, Jason Ekstrand wrote: On May 9, 2021 12:12:36 Martin Peres wrote: Hi, On 06/05/2021 22:13, Matthew Brost wrote: Basic GuC submission support. This is the first bullet point

Re: [Intel-gfx] [RFC PATCH 00/97] Basic GuC submission support in the i915

On 10/05/2021 19:25, Jason Ekstrand wrote: On May 10, 2021 08:55:55 Martin Peres wrote: On 10/05/2021 02:11, Jason Ekstrand wrote: On May 9, 2021 12:12:36 Martin Peres wrote: Hi, On 06/05/2021 22:13, Matthew Brost wrote: Basic GuC submission support. This is the first bullet point

Re: [Intel-gfx] [RFC PATCH 00/97] Basic GuC submission support in the i915

On 11/05/2021 05:58, Dixit, Ashutosh wrote: On Sun, 09 May 2021 16:11:43 -0700, Jason Ekstrand wrote: Yes, landing GuC support may be the first step in removing execlist support. The inevitable reality is that GPU scheduling is coming and likely to be there only path in the not-too-distant

Re: [Intel-gfx] [RFC PATCH 00/97] Basic GuC submission support in the i915

On 10/05/2021 02:11, Jason Ekstrand wrote: On May 9, 2021 12:12:36 Martin Peres wrote: Hi, On 06/05/2021 22:13, Matthew Brost wrote: Basic GuC submission support. This is the first bullet point in the upstreaming plan covered in the following RFC [1]. At a very high level the GuC

Re: [Intel-gfx] [RFC PATCH 00/97] Basic GuC submission support in the i915

Hi, On 06/05/2021 22:13, Matthew Brost wrote: Basic GuC submission support. This is the first bullet point in the upstreaming plan covered in the following RFC [1]. At a very high level the GuC is a piece of firmware which sits between the i915 and the GPU. It offloads some of the scheduling

Re: [Intel-gfx] [PATCH i-g-t] i915: Drop gem_exec_reuse

> case. > > Closes: https://gitlab.freedesktop.org/drm/intel/issues/1289 > Signed-off-by: Chris Wilson > Cc: Martin Peres I can't review easily that what Chris' statement that gem_exec_parallel/gem_exec_whisper are testing a superset of gem_exec_reuse, but I can agree with the logic

Re: [Intel-gfx] [PATCH i-g-t] i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry

hich apparently is one of the better > behaving systems). > > v2: Assert that we are currently suspended prior to opening the file, > i.e. that nothing else is waking up the device behind our backs. > > Signed-off-by: Chris Wilson > Cc: Martin Peres This changes th

Re: [Intel-gfx] [PATCH i-g-t] i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry

On 2020-02-21 10:21, Chris Wilson wrote: > Quoting Martin Peres (2020-02-21 07:33:59) >> On 2020-02-20 19:41, Chris Wilson wrote: >>> Since we check before and then after each debugfs entry, we do not need >>> to check before each time as well. We will error out as soon

Re: [Intel-gfx] [PATCH i-g-t] i915/i915_pm_rpm: Only check for suspend failures after each debugfs entry

hich apparently is one of the better > behaving systems). > > Signed-off-by: Chris Wilson > Cc: Martin Peres I don't like this patch because the first read might not have the gpu suspended, and there shouldn't be much overhead in checking twice rather than once. What's your ration

Re: [Intel-gfx] [PATCH i-g-t] sw_sync: Use fixed runtime for sync_expired_merge

On 2020-02-20 18:57, Chris Wilson wrote: > Convert from using a fixed number of iterations (1 million), to using a > fixed runtime so that we have predictable (and shorter!) run times across > a wide variety of machines. > > Signed-off-by: Chris Wilson > Cc: Martin Peres

Re: [Intel-gfx] [PATCH i-g-t] i915/gem_eio: Trim kms workload

Chris Wilson > Cc: Martin Peres The only difference between the previous behaviour and the new one introduced by the patch is that reset_stress() is called for only the default exec engine as opposed to all of them previously. So, the patch is: Reviewed-by: Martin Peres > --- >

[Intel-gfx] [PATCH 1/2] drm/i915: update the bug-filing instructions link

Freedesktop's Bugzilla instance is no more, and bugs have been migrated to gitlab.freedesktop.org/drm/intel. The instructions also moved from 01.org to fd.o's gitlab to make it easier to keep up to date. This patch updates the link presented to the user after a GPU hang. Signed-off-by: Martin

[Intel-gfx] [PATCH 2/2] MAINTAINERS: update the i915 bug filing instruction

This reflects the fact that freedesktop.org's bugzilla instance is no more, and bugs got migrated to gitlab.freedesktop.org/drm/intel. Signed-off-by: Martin Peres --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index c6278faccdc8

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/4] drm/i915/display: Handle fused off display correctly

On 10/10/2019 23:18, Patchwork wrote: > == Series Details == > > Series: series starting with [1/4] drm/i915/display: Handle fused off display > correctly > URL : https://patchwork.freedesktop.org/series/67872/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_7058 ->

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/huc: improve documentation

nd descrive how HuC accesses > memory (Martin) > > Signed-off-by: Daniele Ceraolo Spurio > Cc: Michal Wajdeczko > Cc: Martin Peres > Acked-by: Anna Karas > --- > Documentation/gpu/i915.rst| 16 +-- > drivers/gpu/drm/i915/gt/uc/intel_huc.c

Re: [Intel-gfx] [PATCH v2 2/3] drm/i915/guc: improve documentation

s not mandatory (Martin) > > Signed-off-by: Daniele Ceraolo Spurio > Cc: Michal Wajdeczko > Cc: Matthew Brost > Cc: Martin Peres > Acked-by: Anna Karas > --- > Documentation/gpu/i915.rst| 22 +- > drivers/gpu/drm/i915/gt/uc/intel_guc.c

Re: [Intel-gfx] [PATCH 3/3] drm/i915/huc: improve documentation

On 28/09/2019 00:42, Daniele Ceraolo Spurio wrote: > Better explain the usage of the microcontroller and what i915 is > responsible of. While at it, fix the documentation for the auth > function, which doesn't do any pinning anymore. > > Signed-off-by: Daniele Ceraolo Spurio > Cc: Michal

Re: [Intel-gfx] [PATCH 2/3] drm/i915/guc: improve documentation

On 28/09/2019 00:42, Daniele Ceraolo Spurio wrote: > Add a short description of what we expect from GuC and some minor > improvements to existing documentation. Also remove a comment about a > difference between GuC and HuC that is not true anymore. > > Signed-off-by: Daniele Ceraolo Spurio >

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Add microcontrollers documentation section

On 28/09/2019 00:42, Daniele Ceraolo Spurio wrote: > To better organize the information, add a microcontrollers section and > move/link the GuC, HuC and DMC documentation under it. Also add a small > intro. > > Signed-off-by: Daniele Ceraolo Spurio Reviewed-by: Martin Peres

Re: [Intel-gfx] [PATCH i-g-t] tests/kms_crtc_background_color: overhaul to match upstream ABI (v5.1)

On 30/09/2019 19:13, Matt Roper wrote: > CRTC background color kernel patches were written about 2.5 years ago > and floated on the upstream mailing list, but since no opensource > userspace materialized, we never actually merged them. However the > corresponding IGT test did get merged and has

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Allow set context SSEU on platforms after gen 11

On 18/09/2019 23:28, Summers, Stuart wrote: > On Wed, 2019-09-18 at 19:31 +, Patchwork wrote: >> == Series Details == >> >> Series: drm/i915: Allow set context SSEU on platforms after gen 11 >> URL : https://patchwork.freedesktop.org/series/66870/ >> State : success >> >> == Summary == >> >>

Re: [Intel-gfx] [PATCH] drm/i915: Enable stolen for iommu on snb/ivb

f I am not, then let's hold the merging of this patch :) Martin > > Signed-off-by: Chris Wilson > Cc: Ville Syrjälä > Cc: Martin Peres > --- > drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 7 --- > 1 file changed, 7 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gem/i

Re: [Intel-gfx] [PATCH i-g-t] i915/gem_mmap_gtt: Run forked mmap tests on tgl

> Signed-off-by: Chris Wilson > Cc: Mika Kuoppala > Cc: Martin Peres > --- > tests/i915/gem_mmap_gtt.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c > index ac439cdf8..e2c6ad9a0 100644 &g

Re: [Intel-gfx] [PATCH] drm/i915: Squeeze iommu status into debugfs/i915_capabilities

ch pertinent information, > so add the iommu status. > > Suggested-by: Martin Peres > Signed-off-by: Chris Wilson > Cc: Martin Peres > Cc: Tomi Sarvela > Cc: Mika Kuoppala > --- > drivers/gpu/drm/i915/i915_debugfs.c | 7 +++ > 1 file changed, 7 insertions

Re: [Intel-gfx] [PATCH 1/1] drm/i915/uc: Turn on GuC/HuC auto mode again

On 19/08/2019 21:22, Lucas De Marchi wrote: > On Mon, Aug 19, l we need is to add2019 at 4:15 AM Michal Wajdeczko > wrote: >> >> On Mon, 19 Aug 2019 10:09:15 +0200, Martin Peres >> wrote: >> >>> On 18/08/2019 18:51, Michal Wajdeczko wrote: >>>>

Re: [Intel-gfx] [PATCH 1/1] drm/i915/uc: Turn on GuC/HuC auto mode again

On 18/08/2019 18:51, Michal Wajdeczko wrote: > We hope that now all issues related to missing uC firmwares > are fixed and that driver can continue to load without GuC > or HuC firmware available and running: > > - missing or corrupted HuC firmware has no impact to driver >load (clients

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for HDCP2.2 Phase II (rev14)

Hi, Sorry for the delay, I was on vacation. The machine fi-skl-6770hq was not marked as having an LSPCON. This is now done, and this means that this issue should be covered by ab existing bug. I queued another run, and we'll see if it gives us a green (new tests don't need to pass on all

Re: [Intel-gfx] [igt-dev] [PATCH i-g-t] i915/gem_pread/pwrite: Rename "basic"

On 27/06/2019 16:26, Arkadiusz Hiler wrote: > On Thu, Jun 27, 2019 at 08:18:36AM +, Ser, Simon wrote: >> On Thu, 2019-06-27 at 08:36 +0100, Chris Wilson wrote: >>> The "basic" subtests perform no verification that the read/write work, >>> only function as mere API exercisers and loose

Re: [Intel-gfx] [PATCH i-g-t] i915/gem_mmap_gtt: Disregard forked subtests on ICL for reasons

gt; Cc: Mika Kuoppala > Cc: Martin Peres > --- > tests/i915/gem_mmap_gtt.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/tests/i915/gem_mmap_gtt.c b/tests/i915/gem_mmap_gtt.c > index 034658e64..c3cb5db2d 100644 > --- a/tests/i915/gem_mmap_gtt.c > ++

Re: [Intel-gfx] [PATCH v5 00/17] GuC 32.0.3

On 28/05/2019 12:45, Chris Wilson wrote: > Quoting Petri Latvala (2019-05-28 10:40:31) >> On Tue, May 28, 2019 at 10:23:24AM +0100, Chris Wilson wrote: >>> Quoting Michal Wajdeczko (2019-05-27 19:35:56) New GuC firmwares (for SKL, BXT, KBL, GLK, ICL) with updated ABI interface. >>> >>> All

Re: [Intel-gfx] [PATCH] drm/i915: Tune down link train error messages due to IO failure

On 23/05/2019 16:08, Imre Deak wrote: > An IO failure happens if the sink is unplugged. This scenario shouldn't > be logged with error level, since it is not a user visible problem. > Converting the corresponding error messages to be debug messages also > ensures that we don't fail some CI test

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Add HDR Metadata Parsing and handling in DRM layer (rev10)

On 16/05/2019 16:18, Shankar, Uma wrote: > > >>> -Original Message- From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com] Sent: Thursday, May 16, 2019 1:02 AM To: Shankar, Uma Cc: intel-gfx@lists.freedesktop.org Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT:

Re: [Intel-gfx] [PATCH v3 00/11] drm/fb-helper: Move modesetting code to drm_client

On 20/04/2019 20:24, Noralf Trønnes wrote: > > > Den 20.04.2019 12.45, skrev Noralf Trønnes: >> This moves the modesetting code from drm_fb_helper to drm_client so it >> can be shared by all internal clients. >> >> Changes this time: >> - Use full drm_client_init/release for the modesets (Daniel

Re: [Intel-gfx] [PATCH v3 02/19] drm/i915/guc: Don't allow GuC submission

urio > Cc: John Spotswood > Cc: Vinay Belgaumkar > Cc: Tony Ye > Cc: Anusha Srivatsa > Cc: Jeff Mcgee > Cc: Antonio Argenziano > Cc: Sujaritha Sundaresan > Cc: Martin Peres Thanks for the update! This will also allow you to drop the HAX patch (patch 22/22) :) Acked

Re: [Intel-gfx] [PATCH v2 02/22] drm/i915/guc: Don't allow GuC submission

On 11/04/2019 11:44, Michal Wajdeczko wrote: > Due to the upcoming changes to the GuC ABI interface, we must > disable GuC submission mode until final ABI will be available > on all GuC firmwares. If I understand correctly, you are disabling command submission by returning -EIO, which leads to

Re: [Intel-gfx] [PATCH v2 22/22] HAX: prevent CI failures on configs with forced GuC submission

On 11/04/2019 11:44, Michal Wajdeczko wrote: > Some CI systems might be configured to run with no longer supported > configuration "enable_guc=3" or "enable_guc=1". Hack that ;) This is not a hack, this is what we need to do: Users put parameters in their command line and forget about them,

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/psr: Get pipe id following atomic guidelines (rev2)

On 29/11/2018 19:36, Rodrigo Vivi wrote: > On Wed, Nov 28, 2018 at 11:52:49PM -0800, Saarinen, Jani wrote: >> Hi, >> >>> -Original Message- >>> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf >>> Of >>> Rodrigo Vivi >>> Sent: torstai 29. marraskuuta 2018 8.18

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/icl: Fix suspend/resume for TypeC HDMI

On 05/11/2018 15:42, Imre Deak wrote: > On Sat, Nov 03, 2018 at 12:45:01AM +, Patchwork wrote: >> == Series Details == >> >> Series: drm/i915/icl: Fix suspend/resume for TypeC HDMI >> URL : https://patchwork.freedesktop.org/series/51976/ >> State : failure > > The failures are unrelated

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Implement HDCP2.2: PART-I (rev2)

On 29/10/2018 13:55, Patchwork wrote: > == Series Details == > > Series: Implement HDCP2.2: PART-I (rev2) > URL : https://patchwork.freedesktop.org/series/51495/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_5044_full -> Patchwork_10620_full = > > == Summary -

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Enabling the IGT for HDCP1.4 (rev4)

On 23/10/2018 08:42, C, Ramalingam wrote: > > On 10/22/2018 10:47 PM, Patchwork wrote: >> == Series Details == >> >> Series: Enabling the IGT for HDCP1.4 (rev4) >> URL : https://patchwork.freedesktop.org/series/51113/ >> State : failure >> >> == Summary == >> >> = CI Bug Log - changes from

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/4] drm/i915: Replace some open-coded i915_map_coherent_type() (rev2)

On 03/10/2018 05:47, Patchwork wrote: > == Series Details == > > Series: series starting with [1/4] drm/i915: Replace some open-coded > i915_map_coherent_type() (rev2) > URL : https://patchwork.freedesktop.org/series/50408/ > State : failure > > == Summary == > > = CI Bug Log - changes from

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Hold task_struct ref for smoking kthread

On 03/10/2018 09:24, Patchwork wrote: > == Series Details == > > Series: drm/i915/selftests: Hold task_struct ref for smoking kthread > URL : https://patchwork.freedesktop.org/series/50441/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4915_full ->

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Rename full ppgtt configuration to be more generic (rev5)

On 03/10/2018 11:29, Patchwork wrote: > == Series Details == > > Series: drm/i915: Rename full ppgtt configuration to be more generic (rev5) > URL : https://patchwork.freedesktop.org/series/49021/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4915_full ->

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm: Fix kernel doc for DRM_MODE_PROP_IMMUTABLE

On 03/10/2018 11:38, Patchwork wrote: > == Series Details == > > Series: drm: Fix kernel doc for DRM_MODE_PROP_IMMUTABLE > URL : https://patchwork.freedesktop.org/series/50462/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4915_full -> Patchwork_10330_full = >

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix the HDMI hot plug disconnection failure

On 03/10/2018 12:34, Patchwork wrote: > == Series Details == > > Series: drm/i915: Fix the HDMI hot plug disconnection failure > URL : https://patchwork.freedesktop.org/series/50477/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4916_full -> Patchwork_10333_full =

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Add XYUV format support (rev6)

On 07/09/2018 14:37, Patchwork wrote: > == Series Details == > > Series: Add XYUV format support (rev6) > URL : https://patchwork.freedesktop.org/series/48007/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4786_full -> Patchwork_10123_full = > > == Summary -

Re: [Intel-gfx] [PATCH] kernel/panic: Show the stacktrace after additional notifier messages

t! Acked-by: Martin Peres > > Signed-off-by: Chris Wilson > --- > kernel/panic.c | 15 --- > 1 file changed, 8 insertions(+), 7 deletions(-) > > diff --git a/kernel/panic.c b/kernel/panic.c > index 8b2e002d52eb..c0334516cb15 100644 > --- a/kernel/panic.c > +

Re: [Intel-gfx] [PATCH i-g-t] igt: Remove gvt_basic

>> >> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106989 >> Signed-off-by: Chris Wilson >> Cc: Zhi Wang > > Martin, would you care to ack? ACK, since we have no tests for GVT-d anyway, we can consider it is broken by default: Acked-by: Martin Peres Zhi, pleas

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] drm/i915: Use ktime on wait_for

On 20/04/18 19:55, Patchwork wrote: > == Series Details == > > Series: series starting with [1/2] drm/i915: Use ktime on wait_for > URL : https://patchwork.freedesktop.org/series/42035/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4072_full -> Patchwork_8764_full

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gvt: Deliver guest cursor hotspot info (rev2)

On 16/04/18 14:45, Patchwork wrote: > == Series Details == > > Series: drm/i915/gvt: Deliver guest cursor hotspot info (rev2) > URL : https://patchwork.freedesktop.org/series/41727/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4054_full -> Patchwork_8694_full = >

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/audio: Fix audio detection issue on GLK (rev2)

On 17/04/18 11:00, Patchwork wrote: > == Series Details == > > Series: drm/i915/audio: Fix audio detection issue on GLK (rev2) > URL : https://patchwork.freedesktop.org/series/41334/ > State : failure > > == Summary == > > = CI Bug Log - changes from CI_DRM_4058 -> Patchwork_8701 = > > ==

[Intel-gfx] Google Summer of Code 2018

Hi everyone, Just a quick word to remind you that the X.Org Foundation got accepted to the Google Summer of Code 2018! As a potential mentor, if you have a project falling under the foundation's (large) umbrella that you would like to kick start or get help finishing, please add it to the list

Re: [Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

On 08/11/17 17:59, Jani Nikula wrote: > On Wed, 08 Nov 2017, Tomi Sarvela wrote: >> On 08/11/17 17:27, Jani Nikula wrote: >>> On Wed, 08 Nov 2017, Chris Wilson wrote: Quoting Jani Nikula (2017-11-08 13:06:39) > > Please use trybot

Re: [Intel-gfx] [PATCH i-g-t] tests/gem_eio: Skip in-flight-suspend on snb

On 20/10/17 12:26, Joonas Lahtinen wrote: > + Petri > > On Thu, 2017-10-19 at 16:29 +0300, Martin Peres wrote: >> On 19/10/17 12:51, Daniel Vetter wrote: >>> CI gets upset about it resulting in an incomplete, let's skip it until >>> that's fixed to avoi

Re: [Intel-gfx] [PATCH i-g-t] tests/gem_eio: Skip in-flight-suspend on snb

Lahtinen <joonas.lahti...@linux.intel.com> Cc: Chris Wilson <ch...@chris-wilson.co.uk> Cc: "Lofstedt, Marta" <marta.lofst...@intel.com> Cc: Martin Peres <martin.pe...@linux.intel.com> References: https://intel-gfx-ci.01.org/tree/drm-tip/igt@gem_...@in-fli

Re: [Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [1/2] drm/i915: avoid unnecessary call to intel_hpd_pin_to_port

On 07/10/17 00:19, Paulo Zanoni wrote: Em Sex, 2017-10-06 às 10:45 +, Patchwork escreveu: == Series Details == Series: series starting with [1/2] drm/i915: avoid unnecessary call to intel_hpd_pin_to_port URL   : https://patchwork.freedesktop.org/series/31459/ State : warning == Summary ==

Re: [Intel-gfx] [PATCH igt 1/5] igt/gem_eio: inflight wedged requires long plugging

On 11/09/17 13:57, Petri Latvala wrote: gem_eio@in-flight is currently filtered in cibuglog. Martin, are you prepared for this subtest rename? Yes, thanks for the heads up! - Intel Finland Oy Registered Address: PL 281, 00181

Re: [Intel-gfx] [PATCH i-g-t] tests: delete extended.testlist

On 04/08/17 10:38, Tomi Sarvela wrote: On 03/08/17 18:34, Daniel Vetter wrote: This approach died, we just run everything there is (and use that to apply some serious darwinian pressure onto testcase to prove themselves). Cc: Martin Peres <martin.pe...@linux.intel.com> Cc: Arkadiusz

Re: [Intel-gfx] [RFC i-g-t v2] igt: Test tagging support

On 21/07/17 15:17, Tvrtko Ursulin wrote: On 21/07/2017 13:02, Martin Peres wrote: On 21/07/17 14:27, Chris Wilson wrote: Quoting Tvrtko Ursulin (2017-07-21 12:08:00) On 21/07/2017 11:36, Chris Wilson wrote: Quoting Tvrtko Ursulin (2017-07-21 11:20:05) From: Tvrtko Ursulin <tvrtko.u

Re: [Intel-gfx] [RFC i-g-t v2] igt: Test tagging support

On 21/07/17 14:27, Chris Wilson wrote: Quoting Tvrtko Ursulin (2017-07-21 12:08:00) On 21/07/2017 11:36, Chris Wilson wrote: Quoting Tvrtko Ursulin (2017-07-21 11:20:05) From: Tvrtko Ursulin [snip] --- a/tests/gem_concurrent_all.c +++

[Intel-gfx] Making IGT runnable by CI and developers

Hi everyone, As some of you may already know, we have made great strides in making our CI system usable, especially in the last 6 months when everything started clicking together. The CI team is no longer overwhelmed with fires and bug reports, so we started working on increasing the

Re: [Intel-gfx] [PATCH i-g-t v5 0/7] CRC testing with Chamelium improvements

On 20/07/17 12:39, Jani Nikula wrote: For future reference, please post new versions of the entire series as new threads. When posting new versions of just some individual patches, in-reply-to each patch being replaced is fine. I think this is more clear, and also gives patchwork a better

Re: [Intel-gfx] [PATCH] drm/i915: More stolen quirking

://bugs.freedesktop.org/show_bug.cgi?id=98683 Cc: Martin Peres <martin.pe...@linux.intel.com> Signed-off-by: Daniel Vetter <daniel.vet...@intel.com> Looks good, and it will reduce the noise in CI. Thanks! Reviewed-by: Martin Peres <martin.pe...@linux.intel.com> --- drivers/gpu/drm/i915/i91

Re: [Intel-gfx] [PATCH i-g-t] lib/igt_debugfs: Update documentation and clenup

ory that is allocated (and they are for all the current cases), so let's put that in the doc too. While I was at it I got rid of strdup() in favor of an early allocation. Cc: Martin Peres <martin.pe...@intel.com> Cc: Liviu Dudau <liviu.du...@arm.com> Reviewed-by: Liviu Dudau <l

Re: [Intel-gfx] [PATCH i-g-t v3 4/4] chamelium: Dump obtained and reference frames to png on crc error

On 10/07/17 17:11, Paul Kocialkowski wrote: On Mon, 2017-07-10 at 16:56 +0300, Martin Peres wrote: On 10/07/17 15:06, Paul Kocialkowski wrote: On Mon, 2017-07-10 at 13:33 +0300, Martin Peres wrote: On 10/07/17 13:31, Paul Kocialkowski wrote: On Thu, 2017-07-06 at 17:57 -0400, Lyude Paul

Re: [Intel-gfx] [PATCH i-g-t v3 4/4] chamelium: Dump obtained and reference frames to png on crc error

On 10/07/17 15:06, Paul Kocialkowski wrote: On Mon, 2017-07-10 at 13:33 +0300, Martin Peres wrote: On 10/07/17 13:31, Paul Kocialkowski wrote: On Thu, 2017-07-06 at 17:57 -0400, Lyude Paul wrote: As well, one advantage we do have here from the chamelium end is that you can only really

Re: [Intel-gfx] [PATCH i-g-t v3 4/4] chamelium: Dump obtained and reference frames to png on crc error

On 10/07/17 13:31, Paul Kocialkowski wrote: On Thu, 2017-07-06 at 17:57 -0400, Lyude Paul wrote: As well, one advantage we do have here from the chamelium end is that you can only really be screen grabbing from one port at a time. So you could actually just track stuff internally in the

Re: [Intel-gfx] [PATCH i-g-t v3 4/4] chamelium: Dump obtained and reference frames to png on crc error

On 06/07/17 00:44, Lyude Paul wrote: On Wed, 2017-07-05 at 11:04 +0300, Paul Kocialkowski wrote: When a CRC comparison error occurs, it is quite useful to get a dump of both the frame obtained from the chamelium and the reference in order to compare them. This implements the frame dump, with a

Re: [Intel-gfx] [PATCH i-g-t v3 2/4] tests/ chamelium: Remove the frame dump tests

On 05/07/17 23:53, Lyude Paul wrote: NAK. You're right that these don't actually give us any advantage over just using CRCs and are just slower, however I left these tests in here moreso just so we had something to actually test the frame dumping functions so that we could avoid regressing them

Re: [Intel-gfx] [PATCH i-g-t 4/7] lib/igt_chamelium: Add support for configurable DUT suspend/resume delay

On 26/06/17 17:33, Paul Kocialkowski wrote: On Mon, 2017-06-26 at 17:25 +0300, Martin Peres wrote: On 26/06/17 16:59, Paul Kocialkowski wrote: This adds support for reading a SuspendResumeDelay property (under [DUT]) in the IGT configuration (igtrc) and exposing it through

Re: [Intel-gfx] [PATCH i-g-t 4/7] lib/igt_chamelium: Add support for configurable DUT suspend/resume delay

On 26/06/17 16:59, Paul Kocialkowski wrote: This adds support for reading a SuspendResumeDelay property (under [DUT]) in the IGT configuration (igtrc) and exposing it through a chamelium_get_suspend_resume_delay function. Signed-off-by: Paul Kocialkowski ---

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Setting pch_id for HSW/BDW in virtual environment

On 14/06/17 16:18, Joonas Lahtinen wrote: On ke, 2017-06-14 at 11:27 +, Patchwork wrote: == Series Details == Series: drm/i915: Setting pch_id for HSW/BDW in virtual environment URL : https://patchwork.freedesktop.org/series/25772/ State : success Janie & Daniel, This patch could be

[Intel-gfx] [PATCH v3] NOTFORUPSTREAM sound/hda: add debug information in call_hp_automute

I would like to send this patch to the core-for-CI branch, in order to verify the theory I exposed in fdo#101246. This patch also hides a potentially serious bug in the sound/hda driver, which may improve our chances of not being affected by bugs there. It may actually also fix some of the

[Intel-gfx] [PATCH v2] NOTFORUPSTREAM sound/hda: add debug information in call_hp_automute

I would like to send this patch to the core-for-CI branch, in order to verify the theory I exposed in fdo#101246. This patch also hides a potentially serious bug in the sound/hda driver, which may improve our chances of not being affected by bugs there. It may actually also fix some of the

[Intel-gfx] [PATCH] NOTFORUPSTREAM sound/hda: add debug information in call_hp_automute

I would like to send this patch to the core-for-CI branch, in order to verify the theory I exposed in fdo#101246. This patch also hides a potentially serious bug in the sound/hda driver, which may improve our chances of not being affected by bugs there. It may actually also fix some of the

Re: [Intel-gfx] [PATCH igt] lib/kms: Force a full reprobe if we find a bad link

On 07/06/17 14:33, Chris Wilson wrote: Quoting Martin Peres (2017-06-07 12:13:24) How about this: When the modeset call fails, check if the link-status is BAD. If not, return a FAIL. If so, force a full re-probe, pick the highest available mode and try again. Do this until a mode applies

Re: [Intel-gfx] [PATCH igt] lib/kms: Force a full reprobe if we find a bad link

On 31/05/17 17:45, Martin Peres wrote: On 31/05/17 16:55, Chris Wilson wrote: On Wed, May 31, 2017 at 04:44:41PM +0300, Martin Peres wrote: On 31/05/17 15:42, Chris Wilson wrote: On Wed, May 31, 2017 at 01:40:00PM +0300, Martin Peres wrote: On 26/05/17 14:48, Chris Wilson wrote: If we do

Re: [Intel-gfx] [PATCH igt] Revert "kms_cursor_legacy: Add a burner thread to make basic-busy-* pass."

On 07/06/17 13:34, Chris Wilson wrote: This reverts commit 7c8703fb02b248c2bcf9756bba8812bcfe7ed5d3. If we expect it to fail until we find a solution, let the hw fail and continue to track the known failure in CI/bugs. Cc: Martin Peres <martin.pe...@linux.intel.com> I agree, the ker

Re: [Intel-gfx] Implementing Miracast

On 01/06/17 09:02, Daniel Kasak wrote: Any news? Seems every TV I bump into these days has Miracast support ... Sorry, it must be frustrating. Some code needs to be re-implemented because it was GPL-based and we need it as MIT. Until I have some time to do this, this will probably not move

Re: [Intel-gfx] [PATCH igt] lib/kms: Force a full reprobe if we find a bad link

On 31/05/17 16:55, Chris Wilson wrote: On Wed, May 31, 2017 at 04:44:41PM +0300, Martin Peres wrote: On 31/05/17 15:42, Chris Wilson wrote: On Wed, May 31, 2017 at 01:40:00PM +0300, Martin Peres wrote: On 26/05/17 14:48, Chris Wilson wrote: If we do a shallow probe of the connector

Re: [Intel-gfx] [PATCH igt] lib/kms: Force a full reprobe if we find a bad link

On 31/05/17 15:42, Chris Wilson wrote: On Wed, May 31, 2017 at 01:40:00PM +0300, Martin Peres wrote: On 26/05/17 14:48, Chris Wilson wrote: If we do a shallow probe of the connector and it reports the link failed previous (link-status != GOOD), force a full probe of the connector to give

Re: [Intel-gfx] [PATCH igt] lib/kms: Force a full reprobe if we find a bad link

On 26/05/17 14:48, Chris Wilson wrote: If we do a shallow probe of the connector and it reports the link failed previous (link-status != GOOD), force a full probe of the connector to give the kernel a chance to validate the mode list. Sounds good, but will this make the tests SKIP if no modes

Re: [Intel-gfx] [PATCH i-g-t] tests/initial_state: Add a test to capture the state of the GPU

ble, improving debuggability" With the commit title and the typo fixed, the patch is: Acked-by: Martin Peres <martin.pe...@linux.intel.com> Signed-off-by: Marta Lofstedt <marta.lofst...@intel.com> --- tests/Makefile.sources| 1 + tests/initial_state.c | 5

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: uninitialized value on error path (rev3)

On 18/04/17 12:14, Dan Carpenter wrote: On Tue, Apr 18, 2017 at 10:58:44AM +0300, Jani Nikula wrote: On Mon, 17 Apr 2017, Dan Carpenter wrote: On Fri, Apr 14, 2017 at 08:13:43PM -, Patchwork wrote: == Series Details == Series: drm/i915: uninitialized value on

Re: [Intel-gfx] freedesktop bug id: 100548, bisected to sched/clock commit

On 13/04/17 14:48, Peter Zijlstra wrote: On Wed, Apr 12, 2017 at 05:49:53PM +0300, Martin Peres wrote: Good to know. Is there a way to disable this behaviour, as a workaround for our CI system until a proper fix lands? We already pushed locally the revert for this patch, but that may affect

Re: [Intel-gfx] freedesktop bug id: 100548, bisected to sched/clock commit

On 12/04/17 17:32, Peter Zijlstra wrote: On Wed, Apr 12, 2017 at 04:40:11PM +0300, Martin Peres wrote: So, why is this only affecting the Core 2 Duo? Core2 doesn't have a usable TSC and would revert to the slow path. I'll have another look at that patch. So, by default, it is using

Re: [Intel-gfx] [PATCH] drm/i915: Setting pch_id for Gen7.5+ in virtual environment

On 31/03/17 12:37, Martin Peres wrote: On 30/03/17 08:39, Zhang, Xiong Y wrote: On Wed, Mar 29, 2017 at 05:02:47PM +0800, Xiong Zhang wrote: In a virtual passthrough environment, the ISA bridge isn't able to be passed through. So pch_id couldn't be gotten from ISA bridge, but pch_id is used

Re: [Intel-gfx] freedesktop bug id: 100548, bisected to sched/clock commit

On 12/04/17 15:31, Peter Zijlstra wrote: On Wed, Apr 12, 2017 at 12:04:00PM +, Lofstedt, Marta wrote: Hi, We have this "old" Lenovo Cantiga laptop(Intel Core 2 Duo L9400), hocked up to our i915 pre-merge CI system, that has started to give unstable results after commit: commit

Re: [Intel-gfx] [PATCH] drm: Document code of conduct

-by: Archit Taneja <arch...@codeaurora.org> Thanks for doing this, this was long overdue! Reviewed-by: Martin Peres <martin.pe...@free.fr> ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: [Intel-gfx] [PATCH] drm/i915: Setting pch_id for Gen7.5+ in virtual environment

On 30/03/17 08:39, Zhang, Xiong Y wrote: On Wed, Mar 29, 2017 at 05:02:47PM +0800, Xiong Zhang wrote: In a virtual passthrough environment, the ISA bridge isn't able to be passed through. So pch_id couldn't be gotten from ISA bridge, but pch_id is used to identify LPT_H and LPT_LP, this patch

  1   2   >