The test doesn't consider immutable properties
Legacy Test: The test trys to set the property, but if the property
is immutable the test fails.
Added conditions to check if the property is immutable.
Atomic Test: The immutable properties are added and
On Tue, Jun 20, 2017 at 06:36:11PM +, Pandiyan, Dhinakaran wrote:
>
>
>
> On Tue, 2017-06-20 at 16:03 +0300, ville.syrj...@linux.intel.com wrote:
> > From: Ville Syrjälä
> >
> > Make the code less confusiong by always using the top 9 bits of the
> > LPC bridge device ID to detect the PCH t
On Tue, Jun 20, 2017 at 11:16 AM, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that broke user
On Tue, Jun 20, 2017 at 02:27:38PM -0400, Bhawanpreet Lakha wrote:
> The test doesn't consider immutable properties
>
> Legacy Test: The test trys to set the property, but if the property
> is immutable the test fails.
> Added conditions to check if the pr
On Tue, 2017-06-20 at 11:16 +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that brok
On 2017-06-20 03:03 PM, Ville Syrjälä wrote:
> On Tue, Jun 20, 2017 at 02:27:38PM -0400, Bhawanpreet Lakha wrote:
>> The test doesn't consider immutable properties
>>
>> Legacy Test: The test trys to set the property, but if the property
>> is immutable the test fails.
>>
Trying to do a modeset from within a reset is fraught with danger. We
can fall into a cyclic deadlock where the modeset is waiting on a
previous modeset that is waiting on a request, and since the GPU hung
that request completion is waiting on the reset. As modesetting doesn't
allow its locks to be
Quoting Michel Thierry (2017-06-20 18:24:56)
> On 20/06/17 04:03, Tvrtko Ursulin wrote:
> >
> > On 20/06/2017 10:57, Chris Wilson wrote:
> >> Next chunk from Michel finally reviewed, after a little hiatus as the
> >> series uncovered a deadlock with concurrent resets.
> >>
> >> Will apply if no obj
== Series Details ==
Series: drm/i915: Break modeset deadlocks on reset (rev2)
URL : https://patchwork.freedesktop.org/series/26059/
State : success
== Summary ==
Series 26059v2 drm/i915: Break modeset deadlocks on reset
https://patchwork.freedesktop.org/api/1.0/series/26059/revisions/2/mbox/
Quoting Tvrtko Ursulin (2017-06-20 16:47:06)
>
> On 20/06/2017 13:43, Chris Wilson wrote:
> > i915_vma_move_to_active() takes the execobject flags and not a boolean!
> > Instead of passing EXEC_OBJECT_WRITE we passed true [i.e.
> > EXEC_OBJECT_NEEDS_FENCE] causing us to start tracking the
> > vma-
In
commit 91eefc05f0ac71902906b2058360e61bd25137fe
Author: Daniel Vetter
Date: Wed Dec 14 00:08:10 2016 +0100
drm: Tighten locking in drm_mode_getconnector
I reordered the logic a bit in that IOCTL, but that broke userspace
since it'll get the new mode list, but not the new property value
On Tue, Jun 20, 2017 at 9:32 PM, Pandiyan, Dhinakaran
wrote:
> Isn't this overwriting the -EFAULT return in case copy_to_user() failed
> while copying the modes ?
Indeed, thanks for spotting this. New patch in-flight.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 5
On Tue, Jun 20, 2017 at 10:28:37PM +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that
== Series Details ==
Series: drm: Fix GETCONNECTOR regression (rev2)
URL : https://patchwork.freedesktop.org/series/26034/
State : warning
== Summary ==
Series 26034v2 drm: Fix GETCONNECTOR regression
https://patchwork.freedesktop.org/api/1.0/series/26034/revisions/2/mbox/
Test kms_force_conn
On Tue, 2017-06-20 at 22:28 +0200, Daniel Vetter wrote:
> In
>
> commit 91eefc05f0ac71902906b2058360e61bd25137fe
> Author: Daniel Vetter
> Date: Wed Dec 14 00:08:10 2016 +0100
>
> drm: Tighten locking in drm_mode_getconnector
>
> I reordered the logic a bit in that IOCTL, but that brok
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Tuesday, June 20, 2017 11:00 PM
> To: Gerd Hoffmann
> Cc: Zhang, Tina ; intel-gfx@lists.freedesktop.org;
> linux-
> ker...@vger.kernel.org; Kirti Wankhede ; Chen,
> Xiaoguang ; intel-gvt-...@lists.f
On Tue, 20 Jun 2017 23:01:53 +
"Zhang, Tina" wrote:
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Tuesday, June 20, 2017 11:00 PM
> > To: Gerd Hoffmann
> > Cc: Zhang, Tina ; intel-gfx@lists.freedesktop.org;
> > linux-
> > ker...@vger.
This patch should be merged to intel-gvt-dev. Here just for the review.
Thanks.
BR,
Tina
> -Original Message-
> From: Patchwork [mailto:patchw...@emeril.freedesktop.org]
> Sent: Tuesday, June 20, 2017 10:06 PM
> To: Zhang, Tina
> Cc: intel-gfx@lists.freedesktop.org
> Subject: ✗ Fi.CI.BAT
Hi all,
We are pleased to announce an update of Intel GVT-g for Xen.
Intel GVT-g is a full GPU virtualization solution with mediated pass-through,
starting from 4th generation Intel Core(TM) processors with Intel processor
graphics. A virtual GPU instance is maintained for each VM, with part of
Hi all,
We are pleased to announce an update of Intel GVT-g for KVM.
Intel GVT-g for KVM (a.k.a. KVMGT) is a full GPU virtualization solution with
mediated pass-through, starting from 5th generation Intel Core(TM) processors
with Intel processor graphics. A virtual GPU instance is maintained f
height of plane was require to swap width/height in case of 90/270
rotation. Now src structure contains already swapped values, So we
don't have to calculate height of the plane.
Signed-off-by: Mahesh Kumar
Reviewed-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/intel_pm.c | 4 +---
1 file chan
use same cpp value in different phase of plane WM caluclation.
Signed-off-by: Mahesh Kumar
Reviewed-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/intel_pm.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm
This patch introduce addition wrapper for fixed point 16.16 operations.
Which will be used by later patches to avoid direct member variables
access of fixed_16_16_t structure.
add_fixed16 : takes 2 fixed_16_16_t variable & returns fixed_16_16_t
add_fixed16_u32 : takes fixed_16_16_t & u32 variable
Plane configuration parameters doesn't change for each WM-level
calculation. Currently we compute same parameters 8 times for each
wm-level.
This patch optimizes it by calculating these parameters in beginning
& reuses during each level-wm calculation.
Signed-off-by: Mahesh Kumar
Acked-by: Maarte
This patch creates a new function for clamping u64 to fixed16.
And make use of this function in other fixed16 wrappers.
Signed-off-by: Mahesh Kumar
---
drivers/gpu/drm/i915/i915_drv.h | 28
1 file changed, 12 insertions(+), 16 deletions(-)
diff --git a/drivers/gpu/d
This patch make naming of fixed-point wrappers consistent
operation__<1st operand>_<2nd operand>
also shorten the name for fixed_16_16 to fixed16
s/u32_to_fixed_16_16/u32_to_fixed16
s/fixed_16_16_to_u32/fixed16_to_u32
s/fixed_16_16_to_u32_round_up/fixed16_to_u32_round_up
s/min_fixed_16_16/min_fixe
This patch combines fixed_16_16_div & fixed_16_16_div_u64 wrappers.
And new fixed_16_16_div wrapper always performs division operation in
u64 internally, to avoid any data loss which was happening in earlier
version of wrapper.
earlier wrapper was converting u32 to fixed16 in 32 bit so we were
loos
GEN > 9 require transition WM to be programmed if IPC is enabled.
This patch calculates & enable transition WM for supported platforms.
If transition WM is enabled, Plane read requests are sent at high
priority until filling above the transition watermark, then the
requests are sent at lower priori
This series Include patches for:
clean fixed16.16 naming & make them consistent
optimize wm calculation code
enable/Implement trans wm calculation
Changes Since V1:
- Split fixed16 cleanup code in more logical patches (Maarten)
- make intel_compute_linetime_wm function st
== Series Details ==
Series: Fixed16.16 wrapper cleanup & wm optimization (rev3)
URL : https://patchwork.freedesktop.org/series/25692/
State : success
== Summary ==
Series 25692v3 Fixed16.16 wrapper cleanup & wm optimization
https://patchwork.freedesktop.org/api/1.0/series/25692/revisions/3/mb
101 - 130 of 130 matches
Mail list logo
