Re: [Intel-gfx] [PATCH 11/11] drm/i915/guc: Restore GuC interrupts across suspend/reset if enabled

2017-10-21 Thread Sagar Arun Kamble
On 10/19/2017 4:33 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:47, Sagar Arun Kamble wrote: In order to override the disable/enable control of GuC interrupts during suspend/reset cycle we are creating two new functions suspend/restore guc_interrupts which check if interrupts were enabled and

Re: [Intel-gfx] [PATCH 10/11] drm/i915/guc: Skip interrupt enabling if logging is already enabled

2017-10-21 Thread Sagar Arun Kamble
On 10/19/2017 4:01 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:47, Sagar Arun Kamble wrote: To balance the GuC interrupt references we don't allow enabling interrupts If logging was enabled earlier with different verbosity. I've noticed in a couple of your previous commits words in the

Re: [Intel-gfx] [PATCH 09/11] drm/i915/guc: Fix GuC interrupts disabling with Logging

2017-10-21 Thread Sagar Arun Kamble
On 10/19/2017 3:54 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:47, Sagar Arun Kamble wrote: With guc_log_unregister disabling runtime logging and interrupts there is no need to disable interrupts during uc_fini_hw hence it is removed. With GuC CT buffer mechanism, interrupt disabling can be

Re: [Intel-gfx] [PATCH 08/11] drm/i915/guc: Add client support to enable/disable GuC interrupts

2017-10-21 Thread Sagar Arun Kamble
On 10/19/2017 3:49 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:46, Sagar Arun Kamble wrote: This patch adds support to enable/disable GuC interrupts for different features without impacting others needs. Currently GuC log capture and CT buffer receive mechanisms use the GuC interrupts. GuC

[Intel-gfx] How To install?

2017-10-21 Thread Rhyanz
How to install graphic card on kali linux with "00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)". i dont know what the steps to install. please help me. Thanks :) ___

[Intel-gfx] ✗ Fi.CI.IGT: failure for HAX: ignore fbcon entirely. ;D

2017-10-21 Thread Patchwork
== Series Details == Series: HAX: ignore fbcon entirely. ;D URL : https://patchwork.freedesktop.org/series/32367/ State : failure == Summary == Test kms_plane_multiple: Subgroup atomic-pipe-C-tiling-none: pass -> INCOMPLETE (shard-hsw) Test pm_rpm:

[Intel-gfx] ✗ Fi.CI.IGT: failure for HAX: Do not restore mode through fbcon (rev2)

2017-10-21 Thread Patchwork
== Series Details == Series: HAX: Do not restore mode through fbcon (rev2) URL : https://patchwork.freedesktop.org/series/31893/ State : failure == Summary == Test gem_mmap_wc: Subgroup set-cache-level: pass -> SKIP (shard-hsw) Test kms_sysfs_edid_timing:

Re: [Intel-gfx] [PATCH 07/11] drm/i915/guc: Grab RPM wakelock while disabling GuC interrupts

2017-10-21 Thread Sagar Arun Kamble
On 10/19/2017 3:39 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:46, Sagar Arun Kamble wrote: Disabling GuC interrupts involves access to GuC IRQ control registers hence ensure device is RPM awake. v2: Add comment about need to synchronize flush work and log runtime destroy

[Intel-gfx] ✗ Fi.CI.BAT: failure for HAX: ignore fbcon entirely. ;D

2017-10-21 Thread Patchwork
== Series Details == Series: HAX: ignore fbcon entirely. ;D URL : https://patchwork.freedesktop.org/series/32367/ State : failure == Summary == Series 32367v1 HAX: ignore fbcon entirely. ;D https://patchwork.freedesktop.org/api/1.0/series/32367/revisions/1/mbox/ Test chamelium:

[Intel-gfx] ✗ Fi.CI.BAT: failure for HAX: Do not restore mode through fbcon (rev2)

2017-10-21 Thread Patchwork
== Series Details == Series: HAX: Do not restore mode through fbcon (rev2) URL : https://patchwork.freedesktop.org/series/31893/ State : failure == Summary == Series 31893v2 HAX: Do not restore mode through fbcon https://patchwork.freedesktop.org/api/1.0/series/31893/revisions/2/mbox/ Test

Re: [Intel-gfx] [PATCH 04/11] drm/i915/guc: Sanitize module parameter guc_log_level

2017-10-21 Thread Sagar Arun Kamble
On 10/19/2017 12:52 PM, Tvrtko Ursulin wrote: On 18/10/2017 16:50, Sagar Arun Kamble wrote: On 10/18/2017 6:29 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:46, Sagar Arun Kamble wrote: Parameter guc_log_level needs to be sanitized based on GuC support and enable_guc_loading parameter since

Re: [Intel-gfx] [PATCH 06/11] drm/i915/guc: Only release GuC log object during submission_fini

2017-10-21 Thread Sagar Arun Kamble
On 10/19/2017 12:48 PM, Tvrtko Ursulin wrote: On 18/10/2017 17:04, Sagar Arun Kamble wrote: On 10/18/2017 6:42 PM, Tvrtko Ursulin wrote: On 18/10/2017 07:46, Sagar Arun Kamble wrote: GuC log runtime/relay channel data is released during i915 unregister, So only GuC log vma needs to be

Re: [Intel-gfx] [PATCH 01/14] drm/i915/guc: Do not use 0 for GuC doorbell cookie

2017-10-21 Thread Sagar Arun Kamble
On 10/20/2017 12:06 AM, Michał Winiarski wrote: Apparently, this value is reserved and may be interpreted as changing doorbell ownership. Even though we're not observing any side effects now, let's skip over it to be consistent with the spec. Suggested-by: Sagar Arun Kamble