On Mon, Oct 31, 2022 at 06:01:11PM +0530, Aravind Iddamsetty wrote:
On XE_LPM+ platforms the media engines are carved out into a separate
GT but have a common GGTMMADR address range which essentially makes
the GGTT address space to be shared between media and render GT.
BSPEC: 63834
Cc: Matt Ro
== Series Details ==
Series: drm/i915/mtl: Media GT and Render GT share common GGTT (rev2)
URL : https://patchwork.freedesktop.org/series/110321/
State : failure
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/110321/revisions/2/mbox/ not
applied
Applying: drm/i91
On Thu, 3 Nov 2022 15:43:26 -0700
Daniel Latypov wrote:
> On Thu, Nov 3, 2022 at 8:23 AM Mauro Carvalho Chehab
> wrote:
> >
> > Hi,
> >
> > I'm facing a couple of issues when testing KUnit with the i915 driver.
> >
> > The DRM subsystem and the i915 driver has, for a long time, his own
> > way t
Hi Lucas,
> -Original Message-
> From: De Marchi, Lucas
> Sent: Friday, November 4, 2022 12:36 PM
> To: Iddamsetty, Aravind
> Cc: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915/mtl: Media GT and Render GT share
> common GGTT
>
Hi,
Not really driver I looked at before but since you copied me some
comments below.
On 03/11/2022 15:55, Alexander Usyskin wrote:
When driver wakes up the firmware from the low power stand,
it is sending a memory ready message.
The send is done via synchronous/blocking function to ensure
On 03/11/2022 18:08, Umesh Nerlige Ramappa wrote:
On Thu, Nov 03, 2022 at 12:28:46PM +, Tvrtko Ursulin wrote:
On 03/11/2022 00:11, Umesh Nerlige Ramappa wrote:
Engine busyness samples around a 10ms period is failing with busyness
ranging approx. from 87% to 115%. The expected range is +/
Hi,
On 04/11/2022 05:41, Steven Rostedt wrote:
From: "Steven Rostedt (Google)"
Before a timer is freed, timer_shutdown_sync() must be called.
Link: https://lore.kernel.org/all/20220407161745.7d675...@gandalf.local.home/
Cc: "Noralf Trønnes"
Cc: David Airlie
Cc: Daniel Vetter
Cc: Jani Ni
On Fri, Nov 04, 2022 at 10:49:39AM +0530, Nautiyal, Ankit K wrote:
> Patch looks good to me.
>
> Minor suggestions inline:
>
> On 10/26/2022 5:09 PM, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Currently when opeating in split gamma mode we do the
> nitpick: 'operating' typo.
> > "skip
On 03/11/2022 19:16, John Harrison wrote:
On 11/3/2022 02:38, Tvrtko Ursulin wrote:
On 03/11/2022 09:18, Tvrtko Ursulin wrote:
On 03/11/2022 01:33, John Harrison wrote:
On 11/2/2022 07:20, Tvrtko Ursulin wrote:
On 02/11/2022 12:12, Jani Nikula wrote:
On Tue, 01 Nov 2022, john.c.harri...@in
== Series Details ==
Series: Add DP MST DSC support to i915 (rev16)
URL : https://patchwork.freedesktop.org/series/101492/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12337_full -> Patchwork_101492v16_full
Summary
---
On Thu, 03 Nov 2022, "Navare, Manasi" wrote:
> On Thu, Nov 03, 2022 at 11:32:22AM +0530, Swati Sharma wrote:
>> Lets use RUNTIME_INFO->has_dsc since platforms supporting dsc has this
>> flag enabled.
>>
>> This is done based on the review comments received on
>> https://patchwork.freedesktop.org/
On 11/3/22 16:14, Thomas Zimmermann wrote:
> Uncouple the parameter drm_leak_fbdev_smem from the implementation by
> setting a flag in struct drm_fb_helper. This will help to move the
> generic fbdev emulation into its own source file, while keeping the
> parameter in drm_fb_helper.c. No functional
On 11/3/22 16:14, Thomas Zimmermann wrote:
> Clarify documentation in the use of struct drm_driver.last_close and
> struct drm_mode_config_funcs.output_poll_changed. Those callbacks should
> not be said for fbdev implementations on top of struct drm_client_funcs.
>
> Signed-off-by: Thomas Zimmerma
On Sat, Oct 29, 2022 at 09:12:27AM +0200, Fabio M. De Francesco wrote:
> Date: Sat, 29 Oct 2022 09:12:27 +0200
> From: "Fabio M. De Francesco"
> Subject: Re: [PATCH 0/9] drm/i915: Replace kmap_atomic() with
> kmap_local_page()
Hi Fabio, thanks for your review!! (I'm sorry I missed the previous m
On Sat, Oct 29, 2022 at 01:17:03PM +0200, Fabio M. De Francesco wrote:
> Date: Sat, 29 Oct 2022 13:17:03 +0200
> From: "Fabio M. De Francesco"
> Subject: Re: [PATCH 1/9] drm/i915: Use kmap_local_page() in
> gem/i915_gem_object.c
>
> On luned? 17 ottobre 2022 11:37:17 CEST Zhao Liu wrote:
> > Fro
On Thu, Nov 03, 2022 at 09:51:23AM -0700, Ira Weiny wrote:
> Date: Thu, 3 Nov 2022 09:51:23 -0700
> From: Ira Weiny
> Subject: Re: [PATCH 1/9] drm/i915: Use kmap_local_page() in
> gem/i915_gem_object.c
>
> On Sat, Oct 29, 2022 at 01:17:03PM +0200, Fabio M. De Francesco wrote:
> > On luned? 17 ot
On Thu, Nov 03, 2022 at 08:22:04PM +0100, Fabio M. De Francesco wrote:
> Date: Thu, 03 Nov 2022 20:22:04 +0100
> From: "Fabio M. De Francesco"
> Subject: Re: [PATCH 1/9] drm/i915: Use kmap_local_page() in
> gem/i915_gem_object.c
>
> On gioved? 3 novembre 2022 17:51:23 CET Ira Weiny wrote:
> > On
== Series Details ==
Series: series starting with [1/2] drm/i915/pps: Add get_pps_idx() hook as part
of pps_get_register() cleanup (rev2)
URL : https://patchwork.freedesktop.org/series/109820/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12342 -> Patchwork_109820v2
=
From: Ville Syrjälä
This reverts commit f3387d5883ad92e9a54306fa3dff97d4f0581d78.
---
kernel/sched/core.c | 49 -
1 file changed, 17 insertions(+), 32 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index f519f44cd4c7..cb2aa2b54c7a
From: Peter Zijlstra
On Wed, Nov 02, 2022 at 06:57:51PM +0200, Ville Syrjälä wrote:
> On Thu, Oct 27, 2022 at 06:53:23PM +0200, Peter Zijlstra wrote:
> > On Thu, Oct 27, 2022 at 04:09:01PM +0300, Ville Syrjälä wrote:
> > > On Wed, Oct 26, 2022 at 01:43:00PM +0200, Peter Zijlstra wrote:
> >
> > >
On Sat, Oct 29, 2022 at 03:32:08PM +0200, Fabio M. De Francesco wrote:
> Date: Sat, 29 Oct 2022 15:32:08 +0200
> From: "Fabio M. De Francesco"
> Subject: Re: [PATCH 2/9] drm/i915: Use kmap_local_page() in
> gem/i915_gem_pyhs.c
>
> On luned? 17 ottobre 2022 11:37:18 CEST Zhao Liu wrote:
> > From:
On Thu, 2022-11-03 at 19:43 -0400, Matthew Rosato wrote:
> On 11/3/22 5:56 PM, Alex Williamson wrote:
> > On Wed, 2 Nov 2022 16:01:45 +0100
> > Eric Farman wrote:
> >
> > > Hi all,
> > >
> > > Here is an update to the vfio-ccw lifecycle changes that have
> > > been discussed
> > > in various fo
On Thu, 2022-11-03 at 19:22 -0400, Matthew Rosato wrote:
> On 11/2/22 11:01 AM, Eric Farman wrote:
> > Now that the mdev parent data is split out into its own struct,
> > it is safe to move the remaining private data to follow the
> > mdev probe/remove lifecycle. The mdev parent data will remain
>
== Series Details ==
Series: series starting with [CI,1/2] Revert "freezer, sched: Rewrite core
freezer logic fix"
URL : https://patchwork.freedesktop.org/series/110529/
State : warning
== Summary ==
Error: make htmldocs had i915 warnings
./drivers/gpu/drm/i915/i915_perf_types.h:319: warning:
On Fri, 4 Nov 2022 08:49:55 +0100
Mauro Carvalho Chehab wrote:
> On Thu, 3 Nov 2022 15:43:26 -0700
> Daniel Latypov wrote:
>
> > On Thu, Nov 3, 2022 at 8:23 AM Mauro Carvalho Chehab
> > wrote:
> > >
> > > Hi,
> > >
> > > I'm facing a couple of issues when testing KUnit with the i915 driver.
== Series Details ==
Series: series starting with [CI,1/2] Revert "freezer, sched: Rewrite core
freezer logic fix"
URL : https://patchwork.freedesktop.org/series/110529/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12342 -> Patchwork_110529v1
== Series Details ==
Series: KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if
current->mm is not NULL (rev2)
URL : https://patchwork.freedesktop.org/series/110492/
State : warning
== Summary ==
Error: dim checkpatch failed
1bcd7d5d971a KUnit issues - Was: [igt-dev] [PATCH R
== Series Details ==
Series: KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if
current->mm is not NULL (rev2)
URL : https://patchwork.freedesktop.org/series/110492/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12342 -> Patchwork_110492v2
===
Hi Alex,
Here's the (last?) update to the vfio-ccw lifecycle changes that I've sent
recently, and were previously discussed at various points [1][2].
Patches 1-5 rework the behavior of the vfio-ccw driver's private struct.
In summary, the mdev pieces are split out of vfio_ccw_private and into a
n
There's already a device initialization callback that is used to
initialize the release completion workaround that was introduced
by commit ebb72b765fb49 ("vfio/ccw: Use the new device life cycle
helpers").
Move the other elements of the vfio_ccw_private struct that
require distinct initialization
There's enough separation between the parent and private structs now,
that it is fine to remove the release completion hack.
Signed-off-by: Eric Farman
Reviewed-by: Kevin Tian
Reviewed-by: Matthew Rosato
---
drivers/s390/cio/vfio_ccw_ops.c | 14 +-
drivers/s390/cio/vfio_ccw_pri
These places all rely on the ability to jump from a private
struct back to the subchannel struct. Rather than keeping a
copy in our back pocket, let's use the relationship provided
by the vfio_device embedded within the private.
Signed-off-by: Eric Farman
Reviewed-by: Matthew Rosato
---
drivers
Now that the mdev parent data is split out into its own struct,
it is safe to move the remaining private data to follow the
mdev probe/remove lifecycle. The mdev parent data will remain
where it is, and follow the subchannel and the css driver
interfaces.
Signed-off-by: Eric Farman
Reviewed-by: M
Now that we have a reasonable separation of structs that follow
the subchannel and mdev lifecycles, there's no reason we can't
call the official vfio_alloc_device routine for our private data,
and behave like everyone else.
Signed-off-by: Eric Farman
Reviewed-by: Kevin Tian
Acked-by: Alex Willia
Move the stuff associated with the mdev parent (and thus the
subchannel struct) into its own struct, and leave the rest in
the existing private structure.
The subchannel will point to the parent, and the parent will point
to the private, for the areas where one or both are needed. Further
separati
With the "mess" sorted out, we should be able to inline the
vfio_free_device call introduced by commit cb9ff3f3b84c
("vfio: Add helpers for unifying vfio_device life cycle")
and remove them from driver release callbacks.
Signed-off-by: Eric Farman
Reviewed-by: Jason Gunthorpe
Reviewed-by: Kevin
On Thu, 3 Nov 2022 at 00:14, Brian Norris wrote:
>
> On Wed, Nov 02, 2022 at 12:18:37PM +, Matthew Auld wrote:
> > On Tue, 1 Nov 2022 at 21:58, Brian Norris wrote:
> > >
> > > On Fri, Oct 28, 2022 at 5:24 PM Patchwork
> > > wrote:
> > > >
> > > > Patch Details
> > > > Series:drm/i915: Set PR
On Thu, Nov 03, 2022 at 10:10:14PM -0700, Dixit, Ashutosh wrote:
On Thu, 03 Nov 2022 11:07:05 -0700, Umesh Nerlige Ramappa wrote:
Hi Umesh,
PMU reads the GT timestamp as a 2x32 mmio read and since upper and lower
32 bit registers are read in a loop, there is a latency involved in
getting th
On Fri, Nov 04, 2022 at 08:29:38AM +, Tvrtko Ursulin wrote:
On 03/11/2022 18:08, Umesh Nerlige Ramappa wrote:
On Thu, Nov 03, 2022 at 12:28:46PM +, Tvrtko Ursulin wrote:
On 03/11/2022 00:11, Umesh Nerlige Ramappa wrote:
Engine busyness samples around a 10ms period is failing with bus
On Thu, 3 Nov 2022 at 00:14, Brian Norris wrote:
>
> On Wed, Nov 02, 2022 at 12:18:37PM +, Matthew Auld wrote:
> > On Tue, 1 Nov 2022 at 21:58, Brian Norris wrote:
> > >
> > > On Fri, Oct 28, 2022 at 5:24 PM Patchwork
> > > wrote:
> > > >
> > > > Patch Details
> > > > Series:drm/i915: Set PR
On 04/11/2022 14:58, Umesh Nerlige Ramappa wrote:
On Fri, Nov 04, 2022 at 08:29:38AM +, Tvrtko Ursulin wrote:
On 03/11/2022 18:08, Umesh Nerlige Ramappa wrote:
On Thu, Nov 03, 2022 at 12:28:46PM +, Tvrtko Ursulin wrote:
On 03/11/2022 00:11, Umesh Nerlige Ramappa wrote:
Engine busy
== Series Details ==
Series: Add KUnit support for i915 driver
URL : https://patchwork.freedesktop.org/series/110483/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12339_full -> Patchwork_110483v1_full
Summary
---
**
== Series Details ==
Series: vfio-ccw parent rework (rev3)
URL : https://patchwork.freedesktop.org/series/109899/
State : warning
== Summary ==
Error: make htmldocs had i915 warnings
./drivers/gpu/drm/i915/i915_perf_types.h:319: warning: Function parameter or
member 'lock' not described in 'i
Hi Matthew, Rafael,
On 10/27/22 14:09, Rafael J. Wysocki wrote:
> On Thu, Oct 27, 2022 at 12:37 PM Hans de Goede wrote:
>>
>> Hi,
>>
>> On 10/27/22 11:52, Matthew Garrett wrote:
>>> On Thu, Oct 27, 2022 at 11:39:38AM +0200, Hans de Goede wrote:
>>>
The *only* behavior which actually is new i
== Series Details ==
Series: vfio-ccw parent rework (rev3)
URL : https://patchwork.freedesktop.org/series/109899/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12344 -> Patchwork_109899v3
Summary
---
**SUCCESS**
N
On Thu, Nov 3, 2022 at 10:48 PM Steven Rostedt wrote:
>
> Ideally, I would have the first patch go into this rc cycle, which is mostly
> non functional as it will allow the other patches to come in via the
> respective
> subsystems in the next merge window.
Ack.
I also wonder if we could do the
== Series Details ==
Series: drm/fb-helper: Untangle fbdev emulation and helpers (rev3)
URL : https://patchwork.freedesktop.org/series/109942/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12339_full -> Patchwork_109942v3_full
==
From: John Harrison
When trying to analyse bug reports from CI, customers, etc. it can be
difficult to work out exactly what is happening on which GT in a
multi-GT system. So add GT oriented debug/error message wrappers. If
used instead of the drm_ equivalents, you get the same output but with
a
From: John Harrison
Use the new GT oriented output message helpers where possible.
Signed-off-by: John Harrison
---
drivers/gpu/drm/i915/gt/uc/intel_guc.c| 25 +++--
drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c| 9 +-
.../gpu/drm/i915/gt/uc/intel_guc_capture.c| 50 --
dr
From: John Harrison
When trying to analyse bug reports from CI, customers, etc. it can be
difficult to work out exactly what is happening on which GT in a
multi-GT system. So add GT oriented debug/error message wrappers. If
used instead of the drm_ equivalents, you get the same output but with
a
On Wed, Nov 02, 2022 at 10:10:47AM -0700, Daniele Ceraolo Spurio wrote:
> There is no userspace user for this CS yet, we only need it for internal
> kernel ops (e.g. HuC, PXP), so don't expose it.
>
> v2: even if it's not exposed, rename the engine so it is easier to
> identify in the debug logs (
On 11/4/2022 03:01, Tvrtko Ursulin wrote:
On 03/11/2022 19:16, John Harrison wrote:
On 11/3/2022 02:38, Tvrtko Ursulin wrote:
On 03/11/2022 09:18, Tvrtko Ursulin wrote:
On 03/11/2022 01:33, John Harrison wrote:
On 11/2/2022 07:20, Tvrtko Ursulin wrote:
On 02/11/2022 12:12, Jani Nikula wrote:
== Series Details ==
Series: Add GT oriented dmesg output
URL : https://patchwork.freedesktop.org/series/110550/
State : warning
== Summary ==
Error: dim checkpatch failed
3c6bc62f46e5 drm/i915/gt: Add GT oriented dmesg output
-:22: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_gt' - possible
On Fri, Nov 04, 2022 at 12:15:59AM +0530, Badal Nilawar wrote:
> This workaround is added for Media tile of MTL A step. It is to help
> pcode workaround which handles the hardware issue seen during package C2/C3
> transitions due to RC6 entry/exit transitions on Media tile. As a part of
> workaro
== Series Details ==
Series: mei: add timeout to send
URL : https://patchwork.freedesktop.org/series/110495/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12339_full -> Patchwork_110495v1_full
Summary
---
**FAILURE**
== Series Details ==
Series: Add GT oriented dmesg output
URL : https://patchwork.freedesktop.org/series/110550/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12344 -> Patchwork_110550v1
Summary
---
**SUCCESS**
No
On 10/31/2022 18:26, Patchwork wrote:
Project List - Patchwork *Patch Details*
*Series:* drm/i915/guc: Remove excessive line feeds in state dumps
*URL:* https://patchwork.freedesktop.org/series/110343/
*State:*failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_1
On 11/2/2022 12:21 PM, john.c.harri...@intel.com wrote:
From: John Harrison
If a context has already been registered prior to first submission
then context init code was not being called. The noticeable effect of
that was the scheduling priority was left at zero (meaning super high
priority)
On 11/4/2022 11:53, Ceraolo Spurio, Daniele wrote:
On 11/2/2022 12:21 PM, john.c.harri...@intel.com wrote:
From: John Harrison
If a context has already been registered prior to first submission
then context init code was not being called. The noticeable effect of
that was the scheduling priori
On Fri, 4 Nov 2022 08:48:28 +
Tvrtko Ursulin wrote:
> If it stays all DRM drivers in one patch then I guess it needs to go via
> drm-misc, which for i915 would be okay I think in this case since patch
> is extremely unlikely to clash with anything. Or split it up per driver
> and then we c
== Series Details ==
Series: drm/i915/mtl: Add Wa_14017073508 for SAMedia
URL : https://patchwork.freedesktop.org/series/110502/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12339_full -> Patchwork_110502v1_full
Summary
--
On 10/31/2022 8:36 PM, Badal Nilawar wrote:
From: Vinay Belgaumkar
By defaut idle mesaging is disabled for GSC CS so to unblock RC6
entry on media tile idle messaging need to be enabled.
C6 entry instead of RC6. Also *needs*.
Bspec: 71496
Cc: Daniele Ceraolo Spurio
Signed-off-by: Vinay B
On Fri, Nov 04, 2022 at 01:40:53AM -0400, Steven Rostedt wrote:
>
> Back in April, I posted an RFC patch set to help mitigate a common issue
> where a timer gets armed just before it is freed, and when the timer
> goes off, it crashes in the timer code without any evidence of who the
> culprit was
On 11/2/2022 21:45, Patchwork wrote:
Project List - Patchwork *Patch Details*
*Series:* Fix for two GuC issues (rev2)
*URL:* https://patchwork.freedesktop.org/series/110269/
*State:*failure
*Details:*
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110269v2/index.html
CI B
On Fri, 4 Nov 2022 12:22:32 -0700
Guenter Roeck wrote:
> Unfortunately the renaming caused some symbol conflicts.
>
> Global definition: timer_shutdown
>
> File Line
> 0 time.c93 static inline void timer_shutdown(struct
> clock_event_device *evt)
> 1 arm_arch_timer.c
On Thu, Nov 03, 2022 at 04:38:16AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Tuesday, November 1, 2022 8:26 PM
> > And this:
> >
> > /*
> > * If the device does not have
> > IOMMU_CAP_ENFORCE_CACHE_COHERENCY then
> > * any domain later attached to it will also no
Reviewed-by: Tony Krowiak : vfio_ap part
On 11/2/22 11:01 AM, Eric Farman wrote:
With the "mess" sorted out, we should be able to inline the
vfio_free_device call introduced by commit cb9ff3f3b84c
("vfio: Add helpers for unifying vfio_device life cycle")
and remove them from driver release call
On Mon, Sep 12, 2022 at 12:17 AM Michał Winiarski
wrote:
>
> IDR is deprecated, and since XArray manages its own state with internal
> locking, it simplifies the locking on DRM side.
> Additionally, don't use the IRQ-safe variant, since operating on drm
> minor is not done in IRQ context.
>
> Sign
On Wed, Nov 02, 2022 at 10:51:40PM +0200, Ville Syrjälä wrote:
> On Thu, Jul 14, 2022 at 01:24:14PM +0900, Naoya Horiguchi wrote:
> > +/*
> > + * pud_huge() returns 1 if @pud is hugetlb related entry, that is normal
> > + * hugetlb entry or non-present (migration or hwpoisoned) hugetlb entry.
> > +
On 10/31/22 6:11 PM, jim.cro...@gmail.com wrote:
On Mon, Oct 31, 2022 at 7:07 AM Ville Syrjälä
wrote:
On Sun, Oct 30, 2022 at 08:42:52AM -0600, jim.cro...@gmail.com wrote:
On Thu, Oct 27, 2022 at 2:10 PM Ville Syrjälä
wrote:
On Thu, Oct 27, 2022 at 01:55:39PM -0600, jim.cro...@gmail.com w
On Fri, Nov 4, 2022 at 12:50 AM Mauro Carvalho Chehab
wrote:
>
> On Thu, 3 Nov 2022 15:43:26 -0700
> Daniel Latypov wrote:
>
> > On Thu, Nov 3, 2022 at 8:23 AM Mauro Carvalho Chehab
> > wrote:
> > >
> > > Hi,
> > >
> > > I'm facing a couple of issues when testing KUnit with the i915 driver.
> >
On 24/10/2022 22.11, Gwan-gyeong Mun wrote:
> From: Kees Cook
>
> Implement a robust overflows_type() macro to test if a variable or
> constant value would overflow another variable or type. This can be
> used as a constant expression for static_assert() (which requires a
> constant expression[1]
On Thu, Nov 3, 2022 at 8:23 AM Mauro Carvalho Chehab
wrote:
>
> Hi,
>
> I'm facing a couple of issues when testing KUnit with the i915 driver.
>
> The DRM subsystem and the i915 driver has, for a long time, his own
> way to do unit tests, which seems to be added before KUnit.
>
> I'm now checking
On Fri, Nov 4, 2022 at 12:42 PM Steven Rostedt wrote:
>
> Linus, should I also add any patches that has already been acked by the
> respective maintainer?
No, I'd prefer to keep only the ones that are 100% unambiguously not
changing any semantics.
Linus
On Tue, Nov 01, 2022 at 08:21:20AM +, Tian, Kevin wrote:
> > From: Jason Gunthorpe
> > Sent: Wednesday, October 26, 2022 2:51 AM
> >
> > +int vfio_iommufd_bind(struct vfio_device *vdev, struct iommufd_ctx *ictx)
> > +{
> > + u32 ioas_id;
> > + u32 device_id;
> > + int ret;
> > +
> > +
On Fri, 4 Nov 2022 15:42:09 -0400
Steven Rostedt wrote:
> $ git grep '\btimer_shutdown'
> arch/arm/mach-spear/time.c:static inline void timer_shutdown(struct
> clock_event_device *evt)
> arch/arm/mach-spear/time.c: timer_shutdown(evt);
> arch/arm/mach-spear/time.c: timer_shutdown(evt);
>
On Fri, Nov 04, 2022 at 03:42:09PM -0400, Steven Rostedt wrote:
> On Fri, 4 Nov 2022 12:22:32 -0700
> Guenter Roeck wrote:
>
> > Unfortunately the renaming caused some symbol conflicts.
> >
> > Global definition: timer_shutdown
> >
> > File Line
> > 0 time.c93 static i
On Fri, Nov 04, 2022 at 04:38:34PM -0400, Steven Rostedt wrote:
> On Fri, 4 Nov 2022 15:42:09 -0400
> Steven Rostedt wrote:
>
[ ... ]
>
> > drivers/clocksource/timer-fttmr010.c: fttmr010->timer_shutdown(evt);
> > drivers/clocksource/timer-fttmr010.c: fttmr010->timer_shutdown(evt);
> > driver
On Sat, Nov 05, 2022 at 12:59:30AM +0900, Naoya Horiguchi wrote:
> On Wed, Nov 02, 2022 at 10:51:40PM +0200, Ville Syrjälä wrote:
> > On Thu, Jul 14, 2022 at 01:24:14PM +0900, Naoya Horiguchi wrote:
> > > +/*
> > > + * pud_huge() returns 1 if @pud is hugetlb related entry, that is normal
> > > + *
From: Ville Syrjälä
For MTL, changing cdclk from between certain frequencies has
both squash and crawl. Use the current cdclk config and
the new(desired) cdclk config to construtc a mid cdclk config.
Set the cdclk twice:
- Current cdclk -> mid cdclk
- mid cdclk -> desired cdclk
v2: Add check in
As per bSpec MTL has 38.4 MHz Reference clock.
Adding the cdclk tables and cdclk_funcs that MTL
will use.
v2: Revert to using bxt_get_cdclk()
BSpec: 65243
Cc: Clint Taylor
Signed-off-by: Anusha Srivatsa
Reviewed-by: Clint Taylor
---
drivers/gpu/drm/i915/display/intel_cdclk.c | 22 +++
== Series Details ==
Series: series starting with [1/2] drm/i915/display: Do both crawl and squash
when changing cdclk
URL : https://patchwork.freedesktop.org/series/110554/
State : warning
== Summary ==
Error: dim checkpatch failed
a2db805524d6 drm/i915/display: Do both crawl and squash when
Hi,
On Wed, Oct 19, 2022 at 10:54:34AM +0100, Tvrtko Ursulin wrote:
> Don't know if this is real or not yet, hit it while running selftests a bit.
> Something to keep an eye on.
>
> [ 2928.370577] ODEBUG: init destroyed (active state 0) object type:
> i915_sw_fence hint: sw_fence_dummy_notify+0
== Series Details ==
Series: series starting with [1/2] drm/i915/display: Do both crawl and squash
when changing cdclk
URL : https://patchwork.freedesktop.org/series/110554/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12346 -> Patchwork_110554v1
On Fri, Nov 04, 2022 at 01:40:53AM -0400, Steven Rostedt wrote:
>
> Back in April, I posted an RFC patch set to help mitigate a common issue
> where a timer gets armed just before it is freed, and when the timer
> goes off, it crashes in the timer code without any evidence of who the
> culprit was
Engine busyness samples around a 10ms period is failing with busyness
ranging approx. from 87% to 115%. The expected range is +/- 5% of the
sample period.
When determining busyness of active engine, the GuC based engine
busyness implementation relies on a 64 bit timestamp register read. The
latenc
PMU reads the GT timestamp as a 2x32 mmio read and since upper and lower
32 bit registers are read in a loop, there is a latency involved between
getting the GT timestamp and the CPU timestamp. As part of the
resolution, refactor intel_uncore_read64_2x32 to acquire forcewake and
uncore lock prior t
Engine busyness samples around a 10ms period is failing with busyness
ranging approx. from 87% to 115%. The expected range is +/- 5% of the
sample period.
When determining busyness of active engine, the GuC based engine
busyness implementation relies on a 64 bit timestamp register read. The
latenc
On 11/4/2022 4:26 PM, Brian Norris wrote:
Hi,
On Wed, Oct 19, 2022 at 10:54:34AM +0100, Tvrtko Ursulin wrote:
Don't know if this is real or not yet, hit it while running selftests a bit.
Something to keep an eye on.
[ 2928.370577] ODEBUG: init destroyed (active state 0) object type:
i915_s
On 11/4/2022 5:38 PM, Ceraolo Spurio, Daniele wrote:
On 11/4/2022 4:26 PM, Brian Norris wrote:
Hi,
On Wed, Oct 19, 2022 at 10:54:34AM +0100, Tvrtko Ursulin wrote:
Don't know if this is real or not yet, hit it while running
selftests a bit. Something to keep an eye on.
[ 2928.370577] ODE
== Series Details ==
Series: Fix live busy stats selftest failure
URL : https://patchwork.freedesktop.org/series/110557/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On 11/4/2022 10:25 AM, john.c.harri...@intel.com wrote:
From: John Harrison
When trying to analyse bug reports from CI, customers, etc. it can be
difficult to work out exactly what is happening on which GT in a
multi-GT system. So add GT oriented debug/error message wrappers. If
used instead
== Series Details ==
Series: series starting with [CI,1/2] Revert "freezer, sched: Rewrite core
freezer logic fix"
URL : https://patchwork.freedesktop.org/series/110529/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12342_full -> Patchwork_110529v1_full
==
== Series Details ==
Series: Fix live busy stats selftest failure
URL : https://patchwork.freedesktop.org/series/110557/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12346 -> Patchwork_110557v1
Summary
---
**SUCCESS
On Fri, Nov 04, 2022 at 02:38:03PM +, Matthew Auld wrote:
> On Thu, 3 Nov 2022 at 00:14, Brian Norris wrote:
> > I'm still curious about the reported failures, but maybe they require
> > some particular sequence of tests? I also don't have the full
> > igt-gpu-tools set running, so maybe they
== Series Details ==
Series: KUnit issues - Was: [igt-dev] [PATCH RFC v2 8/8] drm/i915: check if
current->mm is not NULL (rev2)
URL : https://patchwork.freedesktop.org/series/110492/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12342_full -> Patchwork_110492v2_full
=
On Wed, Nov 02, 2022 at 12:21:08PM -0700, john.c.harri...@intel.com wrote:
From: John Harrison
If a context has already been registered prior to first submission
then context init code was not being called. The noticeable effect of
that was the scheduling priority was left at zero (meaning supe
Back in April, I posted an RFC patch set to help mitigate a common issue
where a timer gets armed just before it is freed, and when the timer
goes off, it crashes in the timer code without any evidence of who the
culprit was. I got side tracked and never finished up on that patch set.
Since this
From: "Steven Rostedt (Google)"
Before a timer is released, timer_shutdown_sync() must be called.
Link: https://lore.kernel.org/all/20221104054053.431922...@goodmis.org/
Cc: "Noralf Trønnes"
Cc: David Airlie
Cc: Daniel Vetter
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc: Tvrtko
From: "Steven Rostedt (Google)"
Before a timer is freed, timer_shutdown_sync() must be called.
Link: https://lore.kernel.org/all/20221104054053.431922...@goodmis.org/
Cc: "Noralf Trønnes"
Cc: David Airlie
Cc: Daniel Vetter
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc: Tvrtko Ur
100 matches
Mail list logo
