On Tue, Aug 21, 2018 at 8:43 PM, John Stultz wrote:
> On Tue, Aug 21, 2018 at 7:59 AM, Noralf Trønnes wrote:
>> Den 21.08.2018 10.44, skrev Daniel Vetter:
>>> On Mon, Aug 20, 2018 at 11:44:56PM -0700, John Stultz wrote:
Since we don't have a drm_gem_cma_object reference in
drm_fb_h
On Tue, Aug 21, 2018 at 10:57:47AM -0300, Rodrigo Siqueira wrote:
> On 08/21, Petri Latvala wrote:
> > On Sat, Jul 07, 2018 at 08:24:39PM -0300, Rodrigo Siqueira wrote:
> > > Some modules name are larger than 5 characters, this can be a problem to
> > > add support for other modules. This patch, in
On Tue, Aug 21, 2018 at 11:22:45AM -0300, Rodrigo Siqueira wrote:
> On 08/21, Petri Latvala wrote:
> > On Sat, Jul 07, 2018 at 08:25:07PM -0300, Rodrigo Siqueira wrote:
> > > This commit adds a new option for forcing the use of a specific module
> > > indicated via command line. The force command
fre 2018-08-17 klockan 19:48 +0530 skrev Uma Shankar:
> Add a blob property for plane CSC usage.
>
> v2: Rebase
>
> v3: Fixed Sean, Paul's review comments. Moved the property from
> mode_config to drm_plane. Created a helper function to instantiate
> these properties and removed from drm_mode_cre
For buffer sharing, use dma-buf instead. We can't set smem_start to 0
unconditionally since that's used by the fbdev mmap default
implementation. And we have plenty of userspace which would like to
keep that working.
This might break legit userspace - if it does we need to look at a
case-by-cases
This was only added for the drm's fbdev emulation support, so that it
would try harder to show the Oops.
Unfortunately this never really worked reliably, and in practice ended
up pushing the real Oops off the screen due to plentyfull locking,
sleep-while-atomic and other issues. So we removed all
It was only used by the panic support in fbcon, which is now gone.
Remove this now dead code too.
Cc: Greg Kroah-Hartman
Cc: Kees Cook
Cc: Joe Perches
Cc: Daniel Vetter
Cc: Meng Xu
Cc: Nicolas Pitre
Cc: Thomas Meyer
Cc: Mike Frysinger
Cc: Bartlomiej Zolnierkiewicz
Cc: Hans de Goede
Cc: T
DRM drivers really, really, really don't want random userspace to
share buffer behind it's back, bypassing the dma-buf buffer sharing
machanism. For that reason we've ruthlessly rejected any IOCTL
exposing the physical address of any graphics buffer.
Unfortunately fbdev comes with that built-in. W
On Wed, Aug 22, 2018 at 10:54:03AM +0200, Daniel Vetter wrote:
> It was only used by the panic support in fbcon, which is now gone.
> Remove this now dead code too.
>
> Cc: Greg Kroah-Hartman
> Cc: Kees Cook
> Cc: Joe Perches
> Cc: Daniel Vetter
> Cc: Meng Xu
> Cc: Nicolas Pitre
> Cc: Thomas
== Series Details ==
Series: series starting with [1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag
URL : https://patchwork.freedesktop.org/series/48541/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695 -> Patchwork_9987 =
== Summary - SUCCESS ==
No regressions found.
This is used for handling future fences. Currently no driver use
these, and I think given the new timeline fence proposed by KHR it
would be better to have a more abstract interface for future fences.
Could be something simple like a struct dma_future_fence plus a
function to add a callback or wait
== Series Details ==
Series: drm/syncobj: Drop add/remove_callback from driver interface
URL : https://patchwork.freedesktop.org/series/48542/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/syncobj: Drop add/remove_callback from driver interface
+drivers/gpu/drm/drm_sync
On Tue, Aug 21, 2018 at 06:50:53PM -0700, Dhinakaran Pandiyan wrote:
> Rename PLANE_CTL_DECOMPRESSION_ENABLE to resemble the bpsec name -
> PLANE_CTL_RENDER_DECOMPRESSION_ENABLE
>
> Suggested-by: Rodrigo Vivi
> Cc: Daniel Vetter
> Signed-off-by: Dhinakaran Pandiyan
Reviewed-by: Ville Syrjälä
On Tue, Aug 21, 2018 at 06:50:52PM -0700, Dhinakaran Pandiyan wrote:
> Code looks cleaner with modifiers hidden inside this wrapper.
>
> Signed-off-by: Dhinakaran Pandiyan
> ---
> drivers/gpu/drm/i915/intel_display.c | 21 +++--
> drivers/gpu/drm/i915/intel_display.h | 1 +
> dr
== Series Details ==
Series: drm/syncobj: Drop add/remove_callback from driver interface
URL : https://patchwork.freedesktop.org/series/48542/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695 -> Patchwork_9988 =
== Summary - SUCCESS ==
No regressions found.
External
On Wed, Aug 22, 2018 at 08:40:19AM +, Lankhorst, Maarten wrote:
> fre 2018-08-17 klockan 19:48 +0530 skrev Uma Shankar:
> > Add a blob property for plane CSC usage.
> >
> > v2: Rebase
> >
> > v3: Fixed Sean, Paul's review comments. Moved the property from
> > mode_config to drm_plane. Created
== Series Details ==
Series: series starting with [1/4] fbdev: Drop FBINFO_CAN_FORCE_OUTPUT flag
URL : https://patchwork.freedesktop.org/series/48541/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695_full -> Patchwork_9987_full =
== Summary - SUCCESS ==
No regressions
This commit adds a new option for forcing the use of a specific driver
indicated via an environment variable.
v2 (Petri):
- Use an environment variable instead of command line
- Refactor the loop in __open_device
- Don't try to load kernel modules
Signed-off-by: Rodrigo Siqueira
Signed-off-by
On Tue, Aug 21, 2018 at 12:54:12PM -0700, Paulo Zanoni wrote:
> Em Ter, 2018-08-21 às 14:12 +0300, Imre Deak escreveu:
> > On Mon, Aug 20, 2018 at 04:11:27PM -0700, Paulo Zanoni wrote:
> > > Em Sex, 2018-08-17 às 16:41 -0700, Paulo Zanoni escreveu:
> > > > Em Qua, 2018-08-15 às 23:27 +0300, Imre De
Op 21-08-18 om 10:38 schreef Mahesh Kumar:
> This patch implements a callback function which will be called before
> crc read. In this function driver can implement any preparation work
> required for successfully reading CRC data.
>
> Changes Since V1:
> - rebase
>
> Cc: dri-de...@lists.freedeskt
Hi,
On Wed, Aug 22, 2018 at 12:53:58PM +0300, Ville Syrjälä wrote:
On Wed, Aug 22, 2018 at 08:40:19AM +, Lankhorst, Maarten wrote:
fre 2018-08-17 klockan 19:48 +0530 skrev Uma Shankar:
> Add a blob property for plane CSC usage.
>
> v2: Rebase
>
> v3: Fixed Sean, Paul's review comments. Move
== Series Details ==
Series: drm/syncobj: Drop add/remove_callback from driver interface
URL : https://patchwork.freedesktop.org/series/48542/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695_full -> Patchwork_9988_full =
== Summary - WARNING ==
Minor unknown changes c
For S0ix we want to deinit power domains (and so deactivate the DMC
firmware) exactly when the platform supports the DC9 state. To reach
S0ix we need DC9 on these platforms (for which the DMC FW needs to be
deactivated) while to reach S0ix on the rest of the DMC platforms we
need DC6 (which needs t
Hi all,
I think it's time to brainstorm a bit about the gitlab migration. Basic reasons:
- fd.o admins want to deprecate shell accounts and hand-rolled
infrastructure, because it's a pain to keep secure&updated.
- gitlab will allow us to add committers on our own, greatly
simplifying that proces
== Series Details ==
Series: drm/i915: Simplify condition to keep DMC active during S0ix
URL : https://patchwork.freedesktop.org/series/48556/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695 -> Patchwork_9989 =
== Summary - SUCCESS ==
No regressions found.
External
On Wed, Aug 22, 2018 at 02:26:02PM +0300, Imre Deak wrote:
> For S0ix we want to deinit power domains (and so deactivate the DMC
> firmware) exactly when the platform supports the DC9 state. To reach
> S0ix we need DC9 on these platforms (for which the DMC FW needs to be
> deactivated) while to rea
On Fri, Aug 17, 2018 at 09:24:05AM +0100, Chris Wilson wrote:
> The optimisation inherent in commit 6a2c4232ece1 ("drm/i915: Make the
> physical object coherent with GTT") relies on that once we allocated a
> cursor we would have coherent, zero overhead access to the scanout plane
> holding the cur
== Series Details ==
Series: drm/i915: Simplify condition to keep DMC active during S0ix
URL : https://patchwork.freedesktop.org/series/48556/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695_full -> Patchwork_9989_full =
== Summary - SUCCESS ==
No regressions found.
On 21/08/2018 13:06, Joonas Lahtinen wrote:
Quoting Kukanova, Svetlana (2018-08-13 16:44:49)
Joonas, sorry for interfering; could you please explain more regarding the
options for tracing scheduling events better than tracepoints?
After scheduling moves to GuC tools will have to switch to somet
ons 2018-08-22 klockan 12:11 +0100 skrev Brian Starkey:
> Hi,
>
> On Wed, Aug 22, 2018 at 12:53:58PM +0300, Ville Syrjälä wrote:
> > On Wed, Aug 22, 2018 at 08:40:19AM +, Lankhorst, Maarten wrote:
> > > fre 2018-08-17 klockan 19:48 +0530 skrev Uma Shankar:
> > > > Add a blob property for plane
On Wed, Aug 22, 2018 at 10:54:05AM +0200, Daniel Vetter wrote:
> For buffer sharing, use dma-buf instead. We can't set smem_start to 0
> unconditionally since that's used by the fbdev mmap default
> implementation. And we have plenty of userspace which would like to
> keep that working.
>
> This m
Hi,
On 8/22/2018 12:26 AM, Rodrigo Vivi wrote:
On Tue, Aug 21, 2018 at 09:30:21PM +0530, Kumar, Mahesh wrote:
Hi,
On 8/21/2018 8:27 PM, Kumar, Mahesh wrote:
Hi,
On 8/17/2018 11:50 PM, Rodrigo Vivi wrote:
On Thu, Jul 26, 2018 at 07:44:09PM +0530, Mahesh Kumar wrote:
IPC may cause underfl
On 22/08/2018 13:49, Tvrtko Ursulin wrote:
On 21/08/2018 13:06, Joonas Lahtinen wrote:
Quoting Kukanova, Svetlana (2018-08-13 16:44:49)
Joonas, sorry for interfering; could you please explain more
regarding the
options for tracing scheduling events better than tracepoints?
After scheduling m
On Wed, Aug 22, 2018 at 01:44:56PM +0200, Daniel Vetter wrote:
> Hi all,
>
> I think it's time to brainstorm a bit about the gitlab migration. Basic
> reasons:
>
> - fd.o admins want to deprecate shell accounts and hand-rolled
> infrastructure, because it's a pain to keep secure&updated.
>
> -
Quoting Tvrtko Ursulin (2018-08-22 15:49:52)
>
> On 21/08/2018 13:06, Joonas Lahtinen wrote:
> > Quoting Kukanova, Svetlana (2018-08-13 16:44:49)
> >> Joonas, sorry for interfering; could you please explain more regarding the
> >> options for tracing scheduling events better than tracepoints?
> >>
On Wed, Aug 22, 2018 at 12:11:42PM +0100, Brian Starkey wrote:
> Hi,
>
> On Wed, Aug 22, 2018 at 12:53:58PM +0300, Ville Syrjälä wrote:
> >On Wed, Aug 22, 2018 at 08:40:19AM +, Lankhorst, Maarten wrote:
> >> fre 2018-08-17 klockan 19:48 +0530 skrev Uma Shankar:
> >> > Add a blob property for p
On Wed, 22 Aug 2018, Daniel Vetter wrote:
> Hi all,
>
> I think it's time to brainstorm a bit about the gitlab migration. Basic
> reasons:
>
> - fd.o admins want to deprecate shell accounts and hand-rolled
> infrastructure, because it's a pain to keep secure&updated.
>
> - gitlab will allow us to
Chris Wilson writes:
> Quoting Mika Kuoppala (2018-08-21 08:58:26)
>> Chris Wilson writes:
>>
>> > Since we no longer maintain our read position in the CSB pointers
>> > register, it always returns 0 and not where we last read up to. As a
>> > result the CSB probing in the state dumper starts f
There have been cases where GPU engine has managed to run past
execbuffer ending due to reasons unknown at that time:
coherency problems, page table setup errors, hw glitches.
Let's try to contain a wild engine head by putting batch
buffer end commands into start and end of scratch page.
Leave two
There have been cases where GPU engine has managed to run past
execbuffer ending due to reasons unknown at that time:
coherency problems, page table setup errors, hw glitches.
Let's try to contain a wild engine head by putting batch
buffer end commands into start and end of scratch page.
v2: add
== Series Details ==
Series: drm/i915/gtt: Setup guards in scratch page (rev2)
URL : https://patchwork.freedesktop.org/series/48565/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Commit: drm/i915/gtt: Setup guards in scratch page
+drivers/gpu/drm/i915/i915_gem_gtt.c:1017:9: warning
Quoting Mika Kuoppala (2018-08-22 14:27:14)
> There have been cases where GPU engine has managed to run past
> execbuffer ending due to reasons unknown at that time:
> coherency problems, page table setup errors, hw glitches.
You are trading an obvious error for a subtle one; if userspace got its
== Series Details ==
Series: drm/i915/gtt: Setup guards in scratch page (rev2)
URL : https://patchwork.freedesktop.org/series/48565/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695 -> Patchwork_9990 =
== Summary - SUCCESS ==
No regressions found.
External URL:
htt
On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
> - Sticking to fdo bugzilla and disabling gitlab issues for at least
> drm-intel for the time being. Doing that migration in the same go is a
> bit much I think. Reassignment across bugzilla and gitlab will be an
> issue.
Can you elabor
From: Tvrtko Ursulin
According to the documentation, when programming the subslice count power-
gating configuration register, the value to be written into it on Gen9LP
should actually in the format of:
1 slice = 0x001
2 slices = 0x010
3 slices = 0x100
And not the popcount of the enabled
On 22/08/18 15:29, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
According to the documentation, when programming the subslice count power-
gating configuration register, the value to be written into it on Gen9LP
should actually in the format of:
1 slice = 0x001
2 slices = 0x010
3 slic
On Wed, Aug 22, 2018 at 3:13 PM, Jani Nikula
wrote:
> On Wed, 22 Aug 2018, Daniel Vetter wrote:
>> Hi all,
>>
>> I think it's time to brainstorm a bit about the gitlab migration. Basic
>> reasons:
>>
>> - fd.o admins want to deprecate shell accounts and hand-rolled
>> infrastructure, because it'
== Series Details ==
Series: drm/i915/gtt: Setup guards in scratch page (rev2)
URL : https://patchwork.freedesktop.org/series/48565/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4695_full -> Patchwork_9990_full =
== Summary - WARNING ==
Minor unknown changes coming with
== Series Details ==
Series: drm/i915: Fix subslice configuration on Gen9LP
URL : https://patchwork.freedesktop.org/series/48566/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4696 -> Patchwork_9991 =
== Summary - SUCCESS ==
No regressions found.
External URL:
https:
Hi Dan,
On 22 August 2018 at 12:44, Daniel Vetter wrote:
> Hi all,
>
> I think it's time to brainstorm a bit about the gitlab migration. Basic
> reasons:
>
> - fd.o admins want to deprecate shell accounts and hand-rolled
> infrastructure, because it's a pain to keep secure&updated.
>
> - gitlab
On 22/08/2018 15:29, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
According to the documentation, when programming the subslice count power-
gating configuration register, the value to be written into it on Gen9LP
should actually in the format of:
1 slice = 0x001
2 slices = 0x010
3 sli
On 22/08/2018 16:08, Lionel Landwerlin wrote:
On 22/08/2018 15:29, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
According to the documentation, when programming the subslice count
power-
gating configuration register, the value to be written into it on Gen9LP
should actually in the format of:
On 22/08/2018 16:17, Tvrtko Ursulin wrote:
On 22/08/2018 16:08, Lionel Landwerlin wrote:
On 22/08/2018 15:29, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
According to the documentation, when programming the subslice count
power-
gating configuration register, the value to be written into it
On 22/08/2018 16:22, Lionel Landwerlin wrote:
On 22/08/2018 16:17, Tvrtko Ursulin wrote:
On 22/08/2018 16:08, Lionel Landwerlin wrote:
On 22/08/2018 15:29, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
According to the documentation, when programming the subslice count
power-
gating configur
On Wed, Aug 22, 2018 at 06:32:33PM +0530, Kumar, Mahesh wrote:
> Hi,
>
>
> On 8/22/2018 12:26 AM, Rodrigo Vivi wrote:
> > On Tue, Aug 21, 2018 at 09:30:21PM +0530, Kumar, Mahesh wrote:
> > > Hi,
> > >
> > >
> > > On 8/21/2018 8:27 PM, Kumar, Mahesh wrote:
> > > > Hi,
> > > >
> > > >
> > > > O
On 22/08/2018 16:27, Tvrtko Ursulin wrote:
On 22/08/2018 16:22, Lionel Landwerlin wrote:
On 22/08/2018 16:17, Tvrtko Ursulin wrote:
On 22/08/2018 16:08, Lionel Landwerlin wrote:
On 22/08/2018 15:29, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
According to the documentation, when programmin
On Wed, Aug 22, 2018 at 10:19:19AM -0400, Adam Jackson wrote:
> On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
>
> > - Sticking to fdo bugzilla and disabling gitlab issues for at least
> > drm-intel for the time being. Doing that migration in the same go is a
> > bit much I think. Reass
Fine with me.
Reviewed-by: Jason Ekstrand
On Wed, Aug 22, 2018 at 4:29 AM Daniel Vetter
wrote:
> This is used for handling future fences. Currently no driver use
> these, and I think given the new timeline fence proposed by KHR it
> would be better to have a more abstract interface for future
== Series Details ==
Series: drm/i915: Fix subslice configuration on Gen9LP
URL : https://patchwork.freedesktop.org/series/48566/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4696_full -> Patchwork_9991_full =
== Summary - WARNING ==
Minor unknown changes coming with Pa
From: Tvrtko Ursulin
Bitfield width for configuring the active slice count has grown in Gen11
so we need to program the GEN8_R_PWR_CLK_STATE accordingly.
Current code was always requesting eight times the number of slices (due
writting to a bitfield starting three bits higher than it should). Th
Hi,
On Wed, 22 Aug 2018 at 16:02, Emil Velikov wrote:
> On 22 August 2018 at 12:44, Daniel Vetter wrote:
> > I think it's time to brainstorm a bit about the gitlab migration. Basic
> > reasons:
> >
> > - fd.o admins want to deprecate shell accounts and hand-rolled
> > infrastructure, because i
On 22/08/2018 17:18, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Bitfield width for configuring the active slice count has grown in Gen11
so we need to program the GEN8_R_PWR_CLK_STATE accordingly.
Current code was always requesting eight times the number of slices (due
writting to a bitfield s
Hi,
On Wed, 22 Aug 2018 at 15:44, Daniel Vetter wrote:
> On Wed, Aug 22, 2018 at 3:13 PM, Jani Nikula
> wrote:
> > Just a couple of concerns from drm/i915 perspective for starters:
> >
> > - Patchwork integration. I think we'll want to keep patchwork for at
> > least intel-gfx etc. for the ti
Hi Rodrigo,
On Wed, 22 Aug 2018 at 17:06, Rodrigo Vivi wrote:
> On Wed, Aug 22, 2018 at 10:19:19AM -0400, Adam Jackson wrote:
> > On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
> > > - Sticking to fdo bugzilla and disabling gitlab issues for at least
> > > drm-intel for the time being. D
== Series Details ==
Series: drm/i915/icl: Fix context slice count configuration
URL : https://patchwork.freedesktop.org/series/48570/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5cf33a6a09d9 drm/i915/icl: Fix context slice count configuration
-:10: WARNING:TYPO_SPELLING: 'wr
Guys and gals,
this is a *very* random list of people on the recipients list, but we
had a subtle TLB shootdown issue in the VM, and that brought up some
issues when people then went through the code more carefully.
I think we have a handle on the TLB shootdown bug itself. But when
people were di
On Wed, Aug 22, 2018 at 12:37:05PM +0200, Maarten Lankhorst wrote:
> Op 21-08-18 om 10:38 schreef Mahesh Kumar:
> > This patch implements a callback function which will be called before
> > crc read. In this function driver can implement any preparation work
> > required for successfully reading CR
== Series Details ==
Series: drm/i915/icl: Fix context slice count configuration
URL : https://patchwork.freedesktop.org/series/48570/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4696 -> Patchwork_9992 =
== Summary - SUCCESS ==
No regressions found.
External URL:
h
On Wed, Aug 22, 2018 at 05:37:22PM +0100, Daniel Stone wrote:
> Hi Rodrigo,
>
> On Wed, 22 Aug 2018 at 17:06, Rodrigo Vivi wrote:
> > On Wed, Aug 22, 2018 at 10:19:19AM -0400, Adam Jackson wrote:
> > > On Wed, 2018-08-22 at 16:13 +0300, Jani Nikula wrote:
> > > > - Sticking to fdo bugzilla and di
On 22/08/2018 17:33, Lionel Landwerlin wrote:
On 22/08/2018 17:18, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Bitfield width for configuring the active slice count has grown in Gen11
so we need to program the GEN8_R_PWR_CLK_STATE accordingly.
Current code was always requesting eight times th
On 22/08/2018 18:07, Tvrtko Ursulin wrote:
On 22/08/2018 17:33, Lionel Landwerlin wrote:
On 22/08/2018 17:18, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Bitfield width for configuring the active slice count has grown in
Gen11
so we need to program the GEN8_R_PWR_CLK_STATE accordingly.
Cur
Log the PSR mode/revision (PSR1 or PSR2) in the debugfs file
i915_edp_psr_status.
Suggested-by: Dhinakaran Pandiyan
Signed-off-by: Azhar Shaikh
---
Changes in v4:
- Fix the rebase error in v3 of adding typecast to bool
- in i915_edp_psr_status(), which is not needed
Changes in v3:
- rebased
Ch
On Wed, 2018-08-22 at 12:48 +0300, Ville Syrjälä wrote:
> On Tue, Aug 21, 2018 at 06:50:52PM -0700, Dhinakaran Pandiyan wrote:
> > Code looks cleaner with modifiers hidden inside this wrapper.
> >
> > Signed-off-by: Dhinakaran Pandiyan
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 21
== Series Details ==
Series: drm/i915/icl: Fix context slice count configuration
URL : https://patchwork.freedesktop.org/series/48570/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4696_full -> Patchwork_9992_full =
== Summary - WARNING ==
Minor unknown changes coming wi
Adding Felix because the KFD part of amdgpu is actually his responsibility.
If I'm not completely mistaken the release callback of the mmu_notifier
should take care of that for amdgpu.
Regards,
Christian.
Am 22.08.2018 um 18:44 schrieb Linus Torvalds:
Guys and gals,
this is a *very* random
On 22/08/2018 18:44, Linus Torvalds wrote:
> An example of something that *isn't* right, is the i915 kvm interface,
> which does
>
> use_mm(kvm->mm);
>
> on an mm that was initialized in virt/kvm/kvm_main.c using
>
> mmgrab(current->mm);
> kvm->mm = current->mm;
>
> whic
On Wed, 2018-08-22 at 10:23 -0700, Azhar Shaikh wrote:
> Log the PSR mode/revision (PSR1 or PSR2) in the debugfs file
> i915_edp_psr_status.
>
Reviewed-by: Dhinakaran Pandiyan
> Suggested-by: Dhinakaran Pandiyan
> Signed-off-by: Azhar Shaikh
> ---
> Changes in v4:
> - Fix the rebase error in
On Wed, Aug 22, 2018 at 11:21 AM Paolo Bonzini wrote:
>
> Yes, KVM is correct but the i915 bits are at least fishy. It's probably
> as simple as adding a mmget/mmput pair respectively in kvmgt_guest_init
> and kvmgt_guest_exit, or maybe mmget_not_zero.
Definitely mmget_not_zero(). If it was just
On Wed, Aug 22, 2018 at 11:09:21AM -0500, Jason Ekstrand wrote:
> Fine with me.
>
> Reviewed-by: Jason Ekstrand
Thanks for the review, applied to drm-misc-next.
-Daniel
>
> On Wed, Aug 22, 2018 at 4:29 AM Daniel Vetter
> wrote:
>
> > This is used for handling future fences. Currently no driv
On Wed, Aug 22, 2018 at 11:33 AM Linus Torvalds
wrote:
>
> On Wed, Aug 22, 2018 at 11:21 AM Paolo Bonzini wrote:
> >
> > Yes, KVM is correct but the i915 bits are at least fishy. It's probably
> > as simple as adding a mmget/mmput pair respectively in kvmgt_guest_init
> > and kvmgt_guest_exit, o
Hi Linus:
Thanks for letting us know that. We would fix this ASAP. The kvmgt.c
module is a part of GVT-g code. It's our fault that we didn't find this
mis-uses, not i915 or KVM guys. Wish they would feel better after seeing
this message.
Thanks,
Zhi.
On 08/23/18 00:44, Linus Torvalds wrote:
On Wed, Aug 22, 2018 at 7:44 PM Linus Torvalds
wrote:
> One of the complex ones is the amdgpu driver. It does a
> "use_mm(mmptr)" deep deep in the guts of a macro that ends up being
> used in fa few places, and it's very hard to tell if it's right.
>
> It looks almost certainly buggy (there is no
Code looks cleaner with modifiers hidden inside this wrapper.
v2: Remove const qualifier (Ville)
Signed-off-by: Dhinakaran Pandiyan
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_display.c | 21 +++--
drivers/gpu/drm/i915/intel_display.h | 1 +
drivers/gpu/drm/i915/i
Hi Dave,
A couple fixes for you that didn't quite make your -rc1 pull last week. I'm
sending this since Gustavo is busy organizing linuxdev-br.
drm-misc-next-fixes-2018-08-22:
- Add an unprepare delay to the tv123wam panel (Sean)
- Update seanpaul's email in MAINTAINERS (Sean)
Cc: seanp...@chro
On 2018-08-22 02:13 PM, Christian König wrote:
> Adding Felix because the KFD part of amdgpu is actually his
> responsibility.
>
> If I'm not completely mistaken the release callback of the
> mmu_notifier should take care of that for amdgpu.
You're right, but that's a bit fragile and convoluted.
On Wed, Aug 22, 2018 at 12:37 PM Oded Gabbay wrote:
>
> Having said that, I think we *are* protected by the mmu_notifier
> release because if the process suddenly dies, we will gracefully clean
> the process's data in our driver and on the H/W before returning to
> the mm core code. And before we
On Wed, Aug 22, 2018 at 10:58 PM Linus Torvalds
wrote:
>
> On Wed, Aug 22, 2018 at 12:37 PM Oded Gabbay wrote:
> >
> > Having said that, I think we *are* protected by the mmu_notifier
> > release because if the process suddenly dies, we will gracefully clean
> > the process's data in our driver a
== Series Details ==
Series: series starting with [v2] drm/i915: Add a small wrapper to check for
CCS modifiers. (rev2)
URL : https://patchwork.freedesktop.org/series/48524/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4697 -> Patchwork_9994 =
== Summary - SUCCESS ==
N
== Series Details ==
Series: Possible use_mm() mis-uses
URL : https://patchwork.freedesktop.org/series/48584/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8fa6553a2650 Possible use_mm() mis-uses
-:114: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description
(prefe
On Wed, Aug 22, 2018 at 12:44 PM Felix Kuehling wrote:
>
> You're right, but that's a bit fragile and convoluted. I'll fix KFD to
> handle this more robustly. See the attached (untested) patch.
Yes, this patch that makes the whole "has to use current mm" or uses
"get_task_mm()" looks good from a
== Series Details ==
Series: Possible use_mm() mis-uses
URL : https://patchwork.freedesktop.org/series/48584/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4697 -> Patchwork_9995 =
== Summary - SUCCESS ==
No regressions found.
External URL:
https://patchwork.freedesk
== Series Details ==
Series: series starting with [v2] drm/i915: Add a small wrapper to check for
CCS modifiers. (rev2)
URL : https://patchwork.freedesktop.org/series/48524/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_4697_full -> Patchwork_9994_full =
== Summary - FAILU
== Series Details ==
Series: Possible use_mm() mis-uses
URL : https://patchwork.freedesktop.org/series/48584/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4697_full -> Patchwork_9995_full =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_9995_full ne
On Thu, 2018-07-19 at 21:21 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Rename some of the tile_offset() functions to aligned_offset() since
> they operate on both linear and tiled functions. And we'll include
> _plane_ in the name of all the variants that take a plane state.
> Should m
On Thu, 2018-07-19 at 21:21 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Each plane may have different stride limitations. Let's add a new
> plane function to retutn the maximum stride for each plane. There's
> going to be some use for this outside the .atomic_check() stuff hence
> the s
On Wed, 2018-08-22 at 22:03 +, Souza, Jose wrote:
> On Thu, 2018-07-19 at 21:21 +0300, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Each plane may have different stride limitations. Let's add a new
> > plane function to retutn the maximum stride for each plane. There's
> > going to be
On Thu, 2018-07-19 at 21:22 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Let's assume that the primary plane for pipe A has the highest max
> stride of all planes, and we'll use that as the global limit when
> creating a new framebuffer.
Well it was already assuming that but using the n
== Series Details ==
Series: drm/i915/psr: Add PSR mode/revision to debugfs (rev4)
URL : https://patchwork.freedesktop.org/series/47902/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4697 -> Patchwork_9996 =
== Summary - SUCCESS ==
No regressions found.
External URL:
On Wed, Aug 15, 2018 at 12:34:05PM +0200, Maarten Lankhorst wrote:
> Add plane alpha blending support with the different blend modes.
> This has been tested on a icl to show the correct results,
> on earlier platforms small rounding errors cause issues. But this
> already happens case with fully tr
On Thu, 2018-07-19 at 21:22 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Make the main/aux surface stuff a bit more generic by using an array
> of structures. This will allow us to deal with both the main and aux
> surfaces with common code.
Nitpick: consider having a enum { SURFACE_MAI
1 - 100 of 125 matches
Mail list logo
