== Series Details ==
Series: drm/i915: Support Async Flip on Linear buffers (rev3)
URL : https://patchwork.freedesktop.org/series/103137/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11849 -> Patchwork_103137v3
Summary
== Series Details ==
Series: Protect vma destruction with the object lock
URL : https://patchwork.freedesktop.org/series/105902/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11849 -> Patchwork_105902v1
Summary
---
== Series Details ==
Series: Fix TLB invalidate issues with Broadwell (rev3)
URL : https://patchwork.freedesktop.org/series/105167/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11849 -> Patchwork_105167v3
Summary
---
== Series Details ==
Series: Fix TLB invalidate issues with Broadwell (rev3)
URL : https://patchwork.freedesktop.org/series/105167/
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: Fix TLB invalidate issues with Broadwell (rev3)
URL : https://patchwork.freedesktop.org/series/105167/
State : warning
== Summary ==
Error: dim checkpatch failed
3daefa3c9e78 drm/i915/gt: Serialize GRDOM access between multiple engine resets
-:109:
On 30/06/2022 20:12, Zanoni, Paulo R wrote:
Can you please explain what happens when we try to write to a range
that's bound as read-only?
It will be mapped as read-only in device page table. Hence any
write access will fail. I would expect a CAT error reported.
What's a CAT error? Does this
== Series Details ==
Series: drm/i915/dp: wait on timeout before retry (rev4)
URL : https://patchwork.freedesktop.org/series/105660/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11848 -> Patchwork_105660v4
Summary
---
Thanks,
Oak
> -Original Message-
> From: Intel-gfx On Behalf Of
> Niranjana Vishwanathapura
> Sent: July 1, 2022 6:51 PM
> To: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org
> Cc: Zanoni, Paulo R ; Hellstrom, Thomas
> ; Auld, Matthew ;
> Vetter, Daniel ;
On Mon, Jul 04, 2022 at 08:30:08AM +0200, Christian König wrote:
Am 28.06.22 um 00:47 schrieb Lucas De Marchi:
Instead of always falling back to memcpy_fromio() for any size, prefer
using read{b,w,l}(). When reading struct members it's common to read
individual integer variables individually.
Intel Gen do support Async Flip is supported on linear buffers. Since we
didn't had a use case, it was not enabled. Now that as part of hybrid
graphics for unsupported hardware pixel formats, its being converted to
linear memory and then flipped, hence enabling!
This patch enables support for
On Mon, Jul 04, 2022 at 12:53:52PM +0530, Arun R Murthy wrote:
> On linktraining error/timeout before retry need to wait for 400usec as
> per the DP CTS spec1.2
s/CTS//
> Under section 2.7.2 AUX Transaction Response/Reply Time-outs
> AUX Replier (the uPacket RX) must start sending the reply back
> On Mon, Jul 04, 2022 at 12:53:52PM +0530, Arun R Murthy wrote:
> > On linktraining error/timeout before retry need to wait for 400usec as
> > per the DP CTS spec1.2
>
> s/CTS//
>
> > Under section 2.7.2 AUX Transaction Response/Reply Time-outs AUX
> > Replier (the uPacket RX) must start
Currently we guarantee that vmas stay alive when the object lock is held
only if we also hold a private vm reference. In order to relax the latter
requirement, take the object lock also when destroying vmas from the
vm destruction path.
Signed-off-by: Thomas Hellström
---
Protecting vma destruction with the object lock is already
implemented everywhere as part of the "Remove short-term pinning" work,
except in the vm destructor where the reasoning was that most code that
needs to keep vmas alive also holds a vm reference.
However this complicates lifetime rules
> -Original Message-
> From: Murthy, Arun R
> Sent: Monday, July 4, 2022 12:54 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: ville.syrj...@linux.intel.com; Zanoni, Paulo R ;
> tprev...@gmail.com; Shankar, Uma ; Nikula, Jani
> ; Murthy, Arun R
> Subject: [PATCH] drm/i915/dp: wait on
From: Chris Wilson
Avoid trying to invalidate the TLB in the middle of performing an
engine reset, as this may result in the reset timing out. Currently,
the TLB invalidate is only serialised by its own mutex, forgoing the
uncore lock, but we can take the uncore->lock as well to serialise
the
Since vma destruction from the vm destruction path now takes the
object lock, we no longer need to take a vm reference from
i915_gem_object_unbind to make sure vmas are kept alive, the
required object lock taken across i915_gem_object_unbind is
sufficient.
Also skip retrying on
> -Original Message-
> From: Nikula, Jani
> Sent: Friday, July 1, 2022 4:45 PM
> To: Murthy, Arun R ; intel-gfx@lists.freedesktop.org
> Cc: ville.syrj...@linux.intel.com; Zanoni, Paulo R ;
> tprev...@gmail.com; Shankar, Uma ; Murthy, Arun R
>
> Subject: Re: [PATCHv3] drm/i915/dp: wait
On linktraining error/timeout before retry need to wait for 400usec as
per the DP CTS spec1.2
Under section 2.7.2 AUX Transaction Response/Reply Time-outs
AUX Replier (the uPacket RX) must start sending the reply back to the AUX
requester (the uPacket TX) within the response period of 300μs. The
On 01/07/2022 15:54, Summers, Stuart wrote:
On Fri, 2022-07-01 at 09:37 +0100, Tvrtko Ursulin wrote:
On 01/07/2022 01:11, Umesh Nerlige Ramappa wrote:
On Thu, Jun 30, 2022 at 09:00:28PM +, Stuart Summers wrote:
In the driver teardown, we are unregistering the gt prior
to unregistering
On Fri, 1 Jul 2022 08:56:53 +0100
Tvrtko Ursulin wrote:
> On 30/06/2022 17:01, Mauro Carvalho Chehab wrote:
> > Em Thu, 30 Jun 2022 09:12:41 +0100
> > Tvrtko Ursulin escreveu:
> >
> >> On 30/06/2022 08:32, Mauro Carvalho Chehab wrote:
> >>> Em Wed, 29 Jun 2022 17:02:59 +0100
> >>> Tvrtko
> -Original Message-
> From: Murthy, Arun R
> Sent: Monday, July 4, 2022 11:07 AM
> To: Shankar, Uma ; Nikula, Jani
> ;
> intel-gfx@lists.freedesktop.org
> Cc: ville.syrj...@linux.intel.com; Zanoni, Paulo R ;
> tprev...@gmail.com
> Subject: RE: [PATCHv3] drm/i915/dp: wait on timeout
i915 selftest hangcheck is causing the i915 driver timeouts, as reported
by Intel CI bot:
http://gfx-ci.fi.intel.com/cibuglog-ng/issuefilterassoc/24297?query_key=42a999f48fa6ecce068bc8126c069be7c31153b4
When such test runs, the only output is:
[ 68.811639] i915: Performing live
From: Chris Wilson
Don't allow two engines to be reset in parallel, as they would both
try to select a reset bit (and send requests to common registers)
and wait on that register, at the same time. Serialize control of
the reset requests/acks using the uncore->lock, which will also ensure
that
> > -Original Message-
> > From: Nikula, Jani
> > Sent: Friday, July 1, 2022 4:45 PM
> > To: Murthy, Arun R ;
> > intel-gfx@lists.freedesktop.org
> > Cc: ville.syrj...@linux.intel.com; Zanoni, Paulo R
> > ; tprev...@gmail.com; Shankar, Uma
> > ; Murthy, Arun R
> > Subject: Re: [PATCHv3]
== Series Details ==
Series: drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr (rev2)
URL : https://patchwork.freedesktop.org/series/105883/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11842_full -> Patchwork_105883v2_full
On 6/29/22 12:56, Geert Uytterhoeven wrote:
> The DRM fbdev emulation layer does not support pushing back
> changes to fb_var_screeninfo to KMS.
>
> However, drm_fb_helper still implements the fb_ops.fb_check_var() and
> fb_ops.fb_set_par() callbacks, but the former fails to validate various
>
== Series Details ==
Series: drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr (rev2)
URL : https://patchwork.freedesktop.org/series/105883/
State : warning
== Summary ==
Error: dim checkpatch failed
d4f96890b01e drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr
== Series Details ==
Series: drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr (rev2)
URL : https://patchwork.freedesktop.org/series/105883/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11842 -> Patchwork_105883v2
== Series Details ==
Series: drm/i915/gt: Add general DSS steering iterator to intel_gt_mcr (rev2)
URL : https://patchwork.freedesktop.org/series/105883/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
30 matches
Mail list logo
