Isn't this patch trying to stop removing for all BOs from bo list?
-David
Original Message
Subject: Re: [PATCH 11/11] drm/amdgpu: stop removing BOs from the LRU during CS
From: Christian König
To: "Zhou, David(ChunMing)" ,"Koenig, Christian" ,"Olsak, Marek" ,"Liang,
Prike"
Hi
Am 15.05.19 um 16:22 schrieb Gerd Hoffmann:
> On Wed, May 15, 2019 at 09:05:54AM +0200, Thomas Zimmermann wrote:
>> Hi,
>>
>> most of this patch set still needs reviews.
>>
>> If it's too large for merging or reviewing at once, I could move the
>> driver changes into separate patch sets. The
On Wed, May 15, 2019 at 12:32 AM Torsten Duwe wrote:
>
> On Tue, 14 May 2019 10:48:40 -0700
> Vasily Khoruzhick wrote:
>
> > > + anx6345: anx6345@38 {
> > > + compatible = "analogix,anx6345";
> > > + reg = <0x38>;
> > > + reset-gpios = < 3 24
https://bugs.freedesktop.org/show_bug.cgi?id=93546
--- Comment #8 from Hadrien Nilsson ---
Unfortunately I do not have a Radeon HD 4870 anymore so I have no way to retest
this bug.
--
You are receiving this mail because:
You are the assignee for the
Hi,
On Wed, May 15, 2019 at 11:20 AM Sean Paul wrote:
> > + if (IS_ERR(hdmi->default_state) &&
> > + !IS_ERR(hdmi->unwedge_state)) {
> > + dev_warn(dev,
> > + "Unwedge requires default
Avoid that we ping/pong the buffers when we stop to pin DMA-buf
exports by using the allowed domains for exported buffers.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
This way we can even pipeline imported BO evictions.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo_util.c | 18 +-
1 file changed, 1 insertion(+), 17 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
b/drivers/gpu/drm/ttm/ttm_bo_util.c
index
Pipeline removal of the BOs backing store when no placement is given
during validation.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index
Instead of relying on the DRM functions just implement our own import
functions. This prepares support for taking care of unpinned DMA-buf.
v2: enable for all exporters, not just amdgpu, fix invalidation
handling, lock reservation object while setting callback
v3: change to new dma_buf attach
The caching of SGT's is actually quite harmful and should probably removed
altogether when all drivers are audited.
Start by providing a separate DMA-buf export implementation in amdgpu. This is
also a prerequisite of unpinned DMA-buf handling.
v2: fix unintended recursion, remove debugging
Den 15.05.2019 11.09, skrev Sam Ravnborg:
> Hi Noralf.
>
> On Mon, May 06, 2019 at 08:01:35PM +0200, Noralf Trønnes wrote:
>> Move the modeset commit code to drm_client_modeset.
>> No changes except exporting API.
>>
>> v2: Move to drm_client_modeset.c instead of drm_client.c
>>
>>
On Thu, May 02, 2019 at 03:53:33PM -0700, Douglas Anderson wrote:
> See the PhD thesis in the comments in this patch for details, but to
> summarize this adds a hacky "unwedge" feature to the dw_hdmi i2c bus to
> workaround what appears to be a hardware errata. This relies on a
> pinctrl entry to
BO list? No, we stop removing them from the LRU.
But we still move them to the end of the LRU before releasing them.
Christian.
Am 15.05.19 um 16:21 schrieb Zhou, David(ChunMing):
Isn't this patch trying to stop removing for all BOs from bo list?
-David
Original Message
On Wed, May 15, 2019 at 09:05:54AM +0200, Thomas Zimmermann wrote:
> Hi,
>
> most of this patch set still needs reviews.
>
> If it's too large for merging or reviewing at once, I could move the
> driver changes into separate patch sets. The vbox driver's changes have
> been accepted by Hans
Hi Noralf.
On Wed, May 15, 2019 at 04:51:04PM +0200, Noralf Trønnes wrote:
> Hi Sam,
>
> [looks like Thundebird decided to throw away my reply, so I'll try again]
I guess it awaits moderator approval as the from address was different
from what you otherwise used - I got both mails.
>
> Den
Hi
From: Douglas Anderson
Date: Thu, May 2, 2019 at 3:38 PM
To: Heiko Stuebner, Sandy Huang, Andrzej Hajda, Laurent Pinchart
Cc: , Neil Armstrong,
, Sean Paul, Douglas Anderson, Zheng Yang, Sam
Ravnborg, ,
, Ville Syrjälä, David Airlie, Jernej
Skrabec, Daniel Vetter
> On Rockchip rk3288-based
From: Sean Paul
dev_pm_domain_attach_by_name() can return NULL, so we should check for
that case when we're about to dereference gxpd.
Fixes: 9325d4266afd ("drm/msm/gpu: Attach to the GPU GX power domain")
Cc: Jordan Crouse
Cc: Rob Clark
Signed-off-by: Sean Paul
---
Hi,
On Wed, May 15, 2019 at 10:58 AM Sean Paul wrote:
> On Thu, May 02, 2019 at 03:38:07PM -0700, Douglas Anderson wrote:
> > On Rockchip rk3288-based Chromebooks when you do a suspend/resume
> > cycle:
> >
> > 1. You lose the ability to detect an HDMI device being plugged in.
> >
> > 2. If
Hi Sam,
[looks like Thundebird decided to throw away my reply, so I'll try again]
Den 15.05.2019 11.04, skrev Sam Ravnborg:
> Hi Noralf.
>
> I have read through the cahnes a copuple of times not and feel confident
> to add my r-b if the comments are considered.
>
> On Mon, May 06, 2019 at
On Tue, May 14, 2019 at 12:57:28PM +0530, Sabyasachi Gupta wrote:
> Remove dpu_kms.h which is included more than once
>
> Signed-off-by: Sabyasachi Gupta
Thanks for your patch, I've applied it to drm-misc-next-fixes.
Note for next time: The patch didn't apply cleanly since dpu_dbg.h has been
Ah, sorry, I missed "+ ttm_bo_move_to_lru_tail(bo,
NULL);".
Right, moving them to end before releasing is fixing my concern.
Sorry for noise.
-David
Original Message
Subject: Re: [PATCH 11/11] drm/amdgpu: stop removing BOs from the LRU during CS
From:
On the exporter side we add optional explicit pinning callbacks. If those
callbacks are implemented the framework no longer caches sg tables and the
map/unmap callbacks are always called with the lock of the reservation object
held.
On the importer side we add an optional invalidate callback.
This commit adds support for KOE's 5.7" display.
Signed-off-by: Lukasz Majewski
Reviewed-by: Rob Herring
---
Previous discussion (and Rob's Reviewed-by) about this patch
https://patchwork.kernel.org/patch/10339595/
It must have been lost during the development process, so
I do resend it now.
On Thu, May 02, 2019 at 03:38:07PM -0700, Douglas Anderson wrote:
> On Rockchip rk3288-based Chromebooks when you do a suspend/resume
> cycle:
>
> 1. You lose the ability to detect an HDMI device being plugged in.
>
> 2. If you're using the i2c bus built in to dw_hdmi then it stops
> working.
>
On Wed, May 15, 2019 at 11:36:33AM -0700, Doug Anderson wrote:
> Hi,
>
> On Wed, May 15, 2019 at 11:20 AM Sean Paul wrote:
>
> > > + if (IS_ERR(hdmi->default_state) &&
> > > + !IS_ERR(hdmi->unwedge_state)) {
> > > +
On Wed, May 15, 2019 at 11:01:26AM -0700, Doug Anderson wrote:
> Hi,
>
> On Wed, May 15, 2019 at 10:58 AM Sean Paul wrote:
>
> > On Thu, May 02, 2019 at 03:38:07PM -0700, Douglas Anderson wrote:
> > > On Rockchip rk3288-based Chromebooks when you do a suspend/resume
> > > cycle:
> > >
> > > 1.
That is a good point, but actually not a problem in practice.
See the change to ttm_eu_fence_buffer_objects:
- ttm_bo_add_to_lru(bo);
+ if (list_empty(>lru))
+ ttm_bo_add_to_lru(bo);
+ else
+
Hi Wen,
On Wed, May 15, 2019 at 02:42:08AM +, Wen He wrote:
> Disable checking for required pixel clock rate if ARCH_LAYERSCPAE
> is enable.
>
> Signed-off-by: Alison Wang
> Signed-off-by: Wen He
> ---
> change in description:
> - This check that only supported one pixel clock
This commit adds documentation entry description for KOE's 5.7" display.
Signed-off-by: Lukasz Majewski
---
Previous discussion (and Rob's Reviewed-by) about this patch
https://patchwork.kernel.org/patch/10339595/
Changes for v4:
- Rebase on top of newest mainline
SHA1:
On 15/05/2019 03:42, Wen He wrote:
Disable checking for required pixel clock rate if ARCH_LAYERSCPAE
is enable.
Signed-off-by: Alison Wang
Signed-off-by: Wen He
---
change in description:
- This check that only supported one pixel clock required clock rate
compare with dts
On Tue, May 14, 2019 at 11:06:25PM +0530, Uma Shankar wrote:
> HDR metadata block is introduced in CEA-861.3 spec.
> Parsing the same to get the panel's HDR metadata.
>
> v2: Rebase and added Ville's POC changes to the patch.
>
> v3: No Change
>
> v4: Addressed Shashank's review comments
>
>
On Wed, May 15, 2019 at 04:55:16PM +0300, Dan Carpenter wrote:
> On Wed, May 15, 2019 at 03:40:14PM +0200, Daniel Vetter wrote:
> > On Wed, May 15, 2019 at 03:29:25PM +0200, Noralf Trønnes wrote:
> > > drm_fb_helper_hotplug_event() should tolerate the fb_helper argument being
> > > NULL. Commit
On 2019-05-15 21:45, Ville Syrjälä wrote:
> On Wed, May 15, 2019 at 07:33:10PM +, Jonas Karlman wrote:
>> On 2019-05-15 21:10, Ville Syrjälä wrote:
>>> On Tue, May 14, 2019 at 11:06:23PM +0530, Uma Shankar wrote:
This patch adds a blob property to get HDR metadata
information from
On Wed, May 15, 2019 at 3:39 PM Jordan Crouse wrote:
>
> On Wed, May 15, 2019 at 01:00:52PM -0400, Sean Paul wrote:
> > From: Sean Paul
> >
> > dev_pm_domain_attach_by_name() can return NULL, so we should check for
> > that case when we're about to dereference gxpd.
> >
> > Fixes: 9325d4266afd
On Wed, May 15, 2019 at 4:54 AM Daniel Vetter wrote:
>
> On Tue, May 14, 2019 at 04:05:13PM +0200, Christian König wrote:
> > Hi Daniel,
> >
> > since we are not moving forward with this I've separated the change out of
> > the larger patchset.
> >
> > Any objections to this now? It's basically
Hi Da.*,
Some more fixes for -next. As predicted more panfrost cleanup.
We also have 4 msm patches that Rob and I figured should just go through -misc
instead of spinning up an msm-fixes branch. If we pooled together all msm fixes
for 5.2, maybe the -fixes branch would have been warranted, but
On 5/9/2019 2:04 PM, Kenny Ho wrote:
> The drm resource being measured and limited here is the GEM buffer
> objects. User applications allocate and free these buffers. In
> addition, a process can allocate a buffer and share it with another
> process. The consumer of a shared buffer can also
On Fri, May 10, 2019 at 3:07 AM Colin King wrote:
>
> From: Colin Ian King
>
> There is a spelling mistake in a DRM_ERROR error message. Fix this.
>
> Signed-off-by: Colin Ian King
Applied. thanks!
Alex
> ---
> drivers/gpu/drm/amd/amdgpu/df_v3_6.c | 2 +-
> 1 file changed, 1 insertion(+),
On 2019-05-15 21:10, Ville Syrjälä wrote:
> On Tue, May 14, 2019 at 11:06:23PM +0530, Uma Shankar wrote:
>> This patch adds a blob property to get HDR metadata
>> information from userspace. This will be send as part
>> of AVI Infoframe to panel.
>>
>> It also implements get() and set() functions
On Tue, May 14, 2019 at 11:06:26PM +0530, Uma Shankar wrote:
> Enable Dynamic Range and Mastering Infoframe for HDR
> content, which is defined in CEA 861.3 spec.
>
> The metadata will be computed based on blending
> policy in userspace compositors and passed as a connector
> property blob to
On Tue, May 14, 2019 at 11:06:34PM +0530, Uma Shankar wrote:
> Added state readout for DRM infoframe and enabled
> state validation for DRM infoframe.
>
> v2: Addressed Ville's review comments and dropped the
> unused drm infoframe read at intel_hdmi_init.
>
> Signed-off-by: Uma Shankar
> ---
>
On Wed, May 15, 2019 at 10:08 PM Alex Deucher wrote:
>
> On Wed, May 15, 2019 at 4:54 AM Daniel Vetter wrote:
> >
> > On Tue, May 14, 2019 at 04:05:13PM +0200, Christian König wrote:
> > > Hi Daniel,
> > >
> > > since we are not moving forward with this I've separated the change out
> > > of
On Wed, May 15, 2019 at 5:06 PM Clément Péron wrote:
>
> Hi Robin,
>
> On Tue, 14 May 2019 at 23:57, Robin Murphy wrote:
> >
> > On 2019-05-14 10:22 pm, Clément Péron wrote:
> > > Hi,
> > >
> > > On Tue, 14 May 2019 at 17:17, Clément Péron wrote:
> > >>
> > >> Hi,
> > >>
> > >> On Tue, 14 May
On Tue, May 14, 2019 at 11:06:31PM +0530, Uma Shankar wrote:
> This patch enables modeset whenever HDR metadata
> needs to be updated to sink.
>
> v2: Addressed Shashank's review comments.
>
> v3: Added Shashank's RB.
>
> v4: Addressed Ville's review comments.
>
> Signed-off-by: Ville Syrjälä
On Wed, May 15, 2019 at 4:52 PM Daniel Vetter wrote:
>
> On Wed, May 15, 2019 at 10:08 PM Alex Deucher wrote:
> >
> > On Wed, May 15, 2019 at 4:54 AM Daniel Vetter wrote:
> > >
> > > On Tue, May 14, 2019 at 04:05:13PM +0200, Christian König wrote:
> > > > Hi Daniel,
> > > >
> > > > since we are
On Wed, May 15, 2019 at 07:33:10PM +, Jonas Karlman wrote:
> On 2019-05-15 21:10, Ville Syrjälä wrote:
> > On Tue, May 14, 2019 at 11:06:23PM +0530, Uma Shankar wrote:
> >> This patch adds a blob property to get HDR metadata
> >> information from userspace. This will be send as part
> >> of
On Wed, May 15, 2019 at 5:26 PM Welty, Brian wrote:
> On 5/9/2019 2:04 PM, Kenny Ho wrote:
> > There are four control file types,
> > stats (ro) - display current measured values for a resource
> > max (rw) - limits for a resource
> > default (ro, root cgroup only) - default values for a resource
https://bugs.freedesktop.org/show_bug.cgi?id=109085
sudheer changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |sudheerj0...@gmail.com
On Tue, May 14, 2019 at 3:57 PM Peteris Rudzusiks
wrote:
>
> On Tue, May 14, 2019 at 04:55:05PM +1000, Ben Skeggs wrote:
> > On Sun, 12 May 2019 at 04:23, Peteris Rudzusiks
> > wrote:
> > >
> > > nv50_head_atomic_duplicate_state() makes a copy of nv50_head_atom
> > > struct. This patch adds
On Wed, 15 May 2019 at 06:57, Colin King wrote:
>
> From: Colin Ian King
>
> There is a spelling mistake in a warning message. Fix it.
Thanks, merged.
>
> Signed-off-by: Colin Ian King
> ---
> drivers/gpu/drm/nouveau/nvkm/subdev/bios/init.c | 2 +-
> 1 file changed, 1 insertion(+), 1
Hey Linus,
Bunch of fixes for the merge window closure, doesn't seem to be
anything too major or serious in there.
It does add TU117 turing modesetting to nouveau but it's just an
enable for preexisting code.
Dave.
amdgpu:
- gpu reset at load crash fix
- ATPX hotplug fix for when dGPU is off
-
https://bugs.freedesktop.org/show_bug.cgi?id=109380
Lakshmi changed:
What|Removed |Added
Summary|[CI][BAT] |[CI][BAT]
https://bugs.freedesktop.org/show_bug.cgi?id=103234
--- Comment #26 from sandy jiil ---
Whenever you need to remove password in window 10 you can visit here
https://removepasswordwindows10.xyz/ to remove your sign in password and use
your PC.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=108514
--- Comment #35 from sandy jiil ---
Whatsapp is well known messenger app.It is used worldwide for messaging when we
download status from it we can face problem. By the use of this site
https://downloadstatus.xyz we can download it for free.
--
Quoting Masahiro Yamada (2019-05-15 05:37:53)
> The top level Makefile adds -Wall globally:
>
> KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs \
>
> I see two "-Wall" added for compiling under drivers/gpu/drm/i915/.
Does it matter? Is the statement in i915/Makefile
https://bugs.freedesktop.org/show_bug.cgi?id=109380
--- Comment #3 from CI Bug Log ---
A CI Bug Log filter associated to this bug has been updated:
{- CHAMELIUM: igt@kms_chamelium@*suspend* - warn - Last errno: 113, No route to
host -}
{+ CHAMELIUM: igt@kms_chamelium@* - warn/fail - Last errno:
Hi Prike,
no, that can lead to massive problems in a real OOM situation and is not
something we can do here.
Christian.
Am 15.05.19 um 04:00 schrieb Liang, Prike:
Hi Christian ,
I just wonder when encounter ENOMEM error during pin amdgpu BOs can we
retry validate again as below.
With
Hi,
most of this patch set still needs reviews.
If it's too large for merging or reviewing at once, I could move the
driver changes into separate patch sets. The vbox driver's changes have
been accepted by Hans already. So only keeping the core changes plus
vbox would be an option.
Best regards
Hi,
On Tue, 2019-05-14 at 16:28 +0200, Daniel Vetter wrote:
> On Tue, May 14, 2019 at 4:13 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Tue, 2019-05-14 at 13:09 +0200, Daniel Vetter wrote:
> > > On Mon, May 13, 2019 at 7:14 PM Paul Kocialkowski
> > > wrote:
> > > > Hey,
> > > >
> > > > Le
Hi Dave & Daniel,
A fix to close a race opportunity between IRQ handler and RCU.
Two fixes that are also stable, disabling FBC on GLK and HSW EDP fastset
correction.
These patches definitely caused conflicts when merged, resolutions should
be all good.
Regards, Joonas
***
On Wed, May 15, 2019 at 09:43:24AM +0200, Paul Kocialkowski wrote:
> Hi,
>
> On Tue, 2019-05-14 at 16:28 +0200, Daniel Vetter wrote:
> > On Tue, May 14, 2019 at 4:13 PM Paul Kocialkowski
> > wrote:
> > > Hi,
> > >
> > > On Tue, 2019-05-14 at 13:09 +0200, Daniel Vetter wrote:
> > > > On Mon, May
Hi,
On Wed, 2019-05-15 at 10:37 +0300, Pekka Paalanen wrote:
> On Tue, 14 May 2019 16:34:01 +0200
> Daniel Vetter wrote:
>
> > On Tue, May 14, 2019 at 3:36 PM Pekka Paalanen wrote:
> > > On Tue, 14 May 2019 13:02:09 +0200
> > > Daniel Vetter wrote:
> > >
> > > > On Tue, May 14, 2019 at
Hi Noralf.
On Mon, May 06, 2019 at 08:01:35PM +0200, Noralf Trønnes wrote:
> Move the modeset commit code to drm_client_modeset.
> No changes except exporting API.
>
> v2: Move to drm_client_modeset.c instead of drm_client.c
>
> Signed-off-by: Noralf Trønnes
Reviewed-by: Sam Ravnborg
Assumes
Hi Noralf.
I have read through the cahnes a copuple of times not and feel confident
to add my r-b if the comments are considered.
On Mon, May 06, 2019 at 08:01:33PM +0200, Noralf Trønnes wrote:
> It now only contains the modeset so use that directly instead and attach
> a modeset array to
On Tue, 14 May 2019 10:48:40 -0700
Vasily Khoruzhick wrote:
> > + anx6345: anx6345@38 {
> > + compatible = "analogix,anx6345";
> > + reg = <0x38>;
> > + reset-gpios = < 3 24 GPIO_ACTIVE_LOW>; /* PD24
> > */
> > + dvdd25-supply =
On Wed, May 15, 2019 at 10:37:31AM +0300, Pekka Paalanen wrote:
> On Tue, 14 May 2019 16:34:01 +0200
> Daniel Vetter wrote:
>
> > On Tue, May 14, 2019 at 3:36 PM Pekka Paalanen wrote:
> > >
> > > On Tue, 14 May 2019 13:02:09 +0200
> > > Daniel Vetter wrote:
> > >
> > > > On Tue, May 14, 2019
On Tue, May 14, 2019 at 02:31:18PM +0200, Christian König wrote:
> From: Chunming Zhou
>
> heavy gpu job could occupy memory long time, which lead other user fail to
> get memory.
>
> basically pick up Christian idea:
>
> 1. Reserve the BO in DC using a ww_mutex ticket (trivial).
> 2. If we
On Tue, May 14, 2019 at 04:05:13PM +0200, Christian König wrote:
> Hi Daniel,
>
> since we are not moving forward with this I've separated the change out of
> the larger patchset.
>
> Any objections to this now? It's basically a 1:1 move of the functionality
> from DRM to DMA-buf.
For my big
On Tue, May 14, 2019 at 04:05:14PM +0200, Christian König wrote:
> To allow a smooth transition from pinning buffer objects to dynamic
> invalidation we first start to cache the sg_table for an attachment.
>
> v2: keep closer to the DRM implementation
>
> Signed-off-by: Christian König
i915
Hi Noralf.
On Mon, May 06, 2019 at 08:01:34PM +0200, Noralf Trønnes wrote:
> This makes the necessary changes so the commit code can be moved out to
> drm_client as-is in the next patch. It's split up to ease review.
>
> Signed-off-by: Noralf Trønnes
Reviewed-by: Sam Ravnborg
Hi Noralf
On Mon, May 06, 2019 at 08:01:37PM +0200, Noralf Trønnes wrote:
> This prepares the modeset code so it can be moved out as-is in the next
> patch.
>
> v3: Remove stray newline
>
> Signed-off-by: Noralf Trønnes
> Reviewed-by: Maxime Ripard
Reviewed-by: Sam Ravnborg
On Tue, May 14, 2019 at 11:36:18AM -0700, Brendan Higgins wrote:
> On Tue, May 14, 2019 at 02:05:05PM +0200, Daniel Vetter wrote:
> > On Tue, May 14, 2019 at 8:04 AM Brendan Higgins
> > wrote:
> > >
> > > On Mon, May 13, 2019 at 04:44:51PM +0200, Daniel Vetter wrote:
> > > > On Sat, May 11, 2019
On Tue, May 14, 2019 at 02:31:25PM +0200, Christian König wrote:
> Let userspace try again if we really run into a deadlock during eviction.
>
> This has a low chance of live locking, but with guaranteed forward process.
>
> Signed-off-by: Christian König
> ---
> drivers/gpu/drm/ttm/ttm_bo.c |
On 5/14/19 5:36 PM, Ezequiel Garcia wrote:
On Tue, 2019-05-14 at 08:38 -0500, Rob Herring wrote:
On Mon, May 13, 2019 at 12:56 PM Ezequiel Garcia wrote:
Currently, there is some logic to make devfreq optional,
but it fails to cover some cases such as !CONFIG_PM_DEVFREQ.
Fails how?
On 5/14/19 1:38 AM, Brendan Higgins wrote:
> On Fri, May 10, 2019 at 03:13:40PM -0700, Frank Rowand wrote:
>> On 5/10/19 9:17 AM, Logan Gunthorpe wrote:
>>>
>>>
>>> On 2019-05-09 11:18 p.m., Frank Rowand wrote:
>>>
YES, kselftest has in-kernel tests. (Excuse the shouting...)
>>>
>>> Cool.
Hi,
On Tue, 14 May 2019 at 12:29, Neil Armstrong wrote:
>
> Hi,
>
> On 13/05/2019 17:14, Daniel Vetter wrote:
> > On Sun, May 12, 2019 at 07:46:00PM +0200, peron.c...@gmail.com wrote:
> >> From: Clément Péron
> >>
> >> Hi,
> >>
> >> The Allwinner H6 has a Mali-T720 MP2. The drivers are
> >>
On Tue, May 14, 2019 at 04:55:05PM +1000, Ben Skeggs wrote:
> On Sun, 12 May 2019 at 04:23, Peteris Rudzusiks
> wrote:
> >
> > nv50_head_atomic_duplicate_state() makes a copy of nv50_head_atom
> > struct. This patch adds copying of struct member named "or", which
> > previously was left
On 2019-05-14 6:14 p.m., Frank Rowand wrote:
> The high level issue is to provide reviewers with enough context to be
> able to evaluate the patch series. That is probably not very obvious
> at this point in the thread. At this point I was responding to Logan's
> response to me that I should
On 5/11/19 10:33 AM, Theodore Ts'o wrote:
> On Fri, May 10, 2019 at 02:12:40PM -0700, Frank Rowand wrote:
>> However, the reply is incorrect. Kselftest in-kernel tests (which
>> is the context here) can be configured as built in instead of as
>> a module, and built in a UML kernel. The UML
Hi all,
based on Maxime's sunxi-dt64-for-5.2, here is what I found so far
still missing in the device tree. Those bits and pieces have already
been submitted but were not yet applied. Currently I also have the
uart1 for bluetooth here, but I'm unsure about the bindings for the
in-kernel btuart.
On Tue, 14 May 2019 16:34:01 +0200
Daniel Vetter wrote:
> On Tue, May 14, 2019 at 3:36 PM Pekka Paalanen wrote:
> >
> > On Tue, 14 May 2019 13:02:09 +0200
> > Daniel Vetter wrote:
> >
> > > On Tue, May 14, 2019 at 10:18 AM Ser, Simon wrote:
> > > >
> > > > On Tue, 2019-05-14 at 11:02
On Wed, May 15, 2019 at 10:38:28AM +0200, Daniel Vetter wrote:
> On Tue, May 14, 2019 at 02:31:18PM +0200, Christian König wrote:
> > From: Chunming Zhou
> >
> > heavy gpu job could occupy memory long time, which lead other user fail to
> > get memory.
> >
> > basically pick up Christian idea:
https://bugs.freedesktop.org/show_bug.cgi?id=93546
--- Comment #7 from Jim Spencer ---
I can produce a trace file without any issue.
https://bit.ly/2CVHGCM
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
Hi Alexander,
On Thu, Jan 17, 2019 at 2:39 PM Alexander Shiyan wrote:
> We have two *_CLASS_DEVICE kernel config options (LCD_CLASS_DEVICE
> and BACKLIGHT_LCD_DEVICE) that do the same job.
> The patch removes useless BACKLIGHT_LCD_SUPPORT option
> and converts LCD_CLASS_DEVICE into a menu.
>
>
Am 15.05.19 um 10:58 schrieb Daniel Vetter:
On Tue, May 14, 2019 at 04:05:14PM +0200, Christian König wrote:
To allow a smooth transition from pinning buffer objects to dynamic
invalidation we first start to cache the sg_table for an attachment.
v2: keep closer to the DRM implementation
Am 15.05.19 um 10:45 schrieb Daniel Vetter:
On Wed, May 15, 2019 at 10:38:28AM +0200, Daniel Vetter wrote:
On Tue, May 14, 2019 at 02:31:18PM +0200, Christian König wrote:
From: Chunming Zhou
heavy gpu job could occupy memory long time, which lead other user fail to get
memory.
basically
> -Original Message-
> From: Dan Carpenter
> Sent: Wednesday, May 15, 2019 5:52 PM
> To: Deucher, Alexander ; Wang, Kevin(Yang)
>
> Cc: Koenig, Christian ; Zhou, David(ChunMing)
> ; David Airlie ; Daniel Vetter
> ; Huang, Ray ; Gao, Likun
> ; Gui, Jack ; amd-
>
Am 15.05.19 um 11:27 schrieb Christian König:
Am 15.05.19 um 10:45 schrieb Daniel Vetter:
On Wed, May 15, 2019 at 10:38:28AM +0200, Daniel Vetter wrote:
On Tue, May 14, 2019 at 02:31:18PM +0200, Christian König wrote:
From: Chunming Zhou
heavy gpu job could occupy memory long time, which
Am 15.05.19 um 10:40 schrieb Daniel Vetter:
On Tue, May 14, 2019 at 02:31:25PM +0200, Christian König wrote:
Let userspace try again if we really run into a deadlock during eviction.
This has a low chance of live locking, but with guaranteed forward process.
Signed-off-by: Christian König
There is a typo so the code unlocks twice instead of taking the lock and
then releasing it.
Fixes: f14a323db5b0 ("drm/amd/powerplay: implement update enabled feature state
to smc for smu11")
Signed-off-by: Dan Carpenter
---
drivers/gpu/drm/amd/powerplay/amdgpu_smu.c | 2 +-
1 file changed, 1
Am 15.05.19 um 10:45 schrieb Daniel Vetter:
On Wed, May 15, 2019 at 10:38:28AM +0200, Daniel Vetter wrote:
On Tue, May 14, 2019 at 02:31:18PM +0200, Christian König wrote:
From: Chunming Zhou
heavy gpu job could occupy memory long time, which lead other user fail to get
memory.
basically
https://bugs.freedesktop.org/show_bug.cgi?id=110659
Michel Dänzer changed:
What|Removed |Added
Version|git |unspecified
On Wed, May 15, 2019 at 3:25 PM Chris Wilson wrote:
>
> Quoting Masahiro Yamada (2019-05-15 05:37:53)
> > The top level Makefile adds -Wall globally:
> >
> > KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs
> > \
> >
> > I see two "-Wall" added for compiling under
https://bugs.freedesktop.org/show_bug.cgi?id=97055
--- Comment #24 from Alan Martin ---
Can I simply just say what a comfort to find somebody that really knows what
they're discussing on the internet.
You definitely understand how to bring an issue to light and make it important.
drm_fb_helper_hotplug_event() should tolerate the fb_helper argument being
NULL. Commit 03a9606e7fee ("drm/fb-helper: Avoid race with DRM userspace")
introduced a fb_helper dereference before the NULL check.
Fixup by moving the dereference after the NULL check.
Fixes: 03a9606e7fee
On Wed, May 15, 2019 at 03:29:25PM +0200, Noralf Trønnes wrote:
> drm_fb_helper_hotplug_event() should tolerate the fb_helper argument being
> NULL. Commit 03a9606e7fee ("drm/fb-helper: Avoid race with DRM userspace")
> introduced a fb_helper dereference before the NULL check.
> Fixup by moving
On Tue, 14 May 2019 16:19:02 -0700
Brendan Higgins wrote:
> Hmmm...probably premature to bring this up, but Documentation/dev-tools/
> is kind of thrown together.
Wait a minute, man... *I* created that directory, are you impugning my
work? :)
But yes, "kind of thrown together" is a good
On Wed, May 15, 2019 at 03:40:14PM +0200, Daniel Vetter wrote:
> On Wed, May 15, 2019 at 03:29:25PM +0200, Noralf Trønnes wrote:
> > drm_fb_helper_hotplug_event() should tolerate the fb_helper argument being
> > NULL. Commit 03a9606e7fee ("drm/fb-helper: Avoid race with DRM userspace")
> >
On Tue, May 14, 2019 at 11:06:23PM +0530, Uma Shankar wrote:
> This patch adds a blob property to get HDR metadata
> information from userspace. This will be send as part
> of AVI Infoframe to panel.
>
> It also implements get() and set() functions for HDR output
> metadata property.The blob data
On Wed, May 15, 2019 at 01:00:52PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> dev_pm_domain_attach_by_name() can return NULL, so we should check for
> that case when we're about to dereference gxpd.
>
> Fixes: 9325d4266afd ("drm/msm/gpu: Attach to the GPU GX power domain")
> Cc: Jordan
1 - 100 of 107 matches
Mail list logo
