On 12 October 2016 at 05:59, Linus Torvalds
wrote:
> What's the status of the 4.9 merge window pull request? The GPU side
> is the main remaining pile for this merge window according to
> linux-next. I'd hate to get a last-minute pull at the end of the week
I'm lining it up this morning, had sick
Hi Linus,
sorry for the delay, had sick wife/baby combo deal last week, which led to
a much reduced sleep pattern. during that I mismerged i915.
this email is all in small letters because my gpg key expired so I couldn't
sign the tag, and it's too early in the morning for me to go do gpg stuff.
On 11/10/16 09:04 PM, Christian König wrote:
> Am 11.10.2016 um 05:58 schrieb Michel Dänzer:
>> On 07/10/16 09:34 PM, Mike Lothian wrote:
>>> This has discussion has gone a little quiet
>>>
>>> Was there any agreement about what needed doing to get this working
>>> for i965/amdgpu?
>> Christian,
On Tue, Oct 11, 2016 at 04:50:04PM -0700, Ruchi Kandoi wrote:
> memtrack maintains a per-process list of shared buffer references, which is
> exported to userspace as /proc/[pid]/memtrack. Buffers can be optionally
> "tagged" with a short string: for example, Android userspace would use this
> ta
se:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/5f3992c5/attachment.html>
Added comments for new parameters.
Signed-off-by: Jiang Biao
---
drivers/gpu/drm/gma500/gtt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/gma500/gtt.c b/drivers/gpu/drm/gma500/gtt.c
index 8f69225..76aea2e 100644
--- a/drivers/gpu/drm/gma500/gtt.c
+++ b/drivers/gpu/drm/g
Hello Rex Zhu,
This is a semi-automatic email about new static checker warnings.
The patch 599a7e9fe1b6: "drm/amd/powerplay: implement smu7 hwmgr to
manager asics with smu ip version 7." from Sep 9, 2016, leads to the
following Smatch complaint:
drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/sm
debugfs_create_file() returns NULL on error, it only returns error
pointers if debugfs isn't enabled in the config and we checked for that
earlier so it can't happen.
Fixes: 4f4824b55650 ('drm/amd/amdgpu: Convert ring debugfs entries to binary')
Signed-off-by: Dan Carpenter
diff --git a/drivers/
A recent cleanup changed the kmalloc() + copy_from_user() to
memdup_user() but the error handling wasn't updated so we might call
kfree(-EFAULT) and crash.
Fixes: a6e3918bcdb1 ('GPU-DRM-Savage: Use memdup_user() rather than
duplicating')
Signed-off-by: Dan Carpenter
diff --git a/drivers/gpu/drm
On Wednesday, October 12, 2016 7:50 AM Ruchi Kandoi wrote:
> +/**
> + * struct ion_fd_data - metadata passed from userspace for a handle
s/fd/tag/ ?
> + * @handle: a handle
> + * @tag: a string describing the buffer
> + *
> + * For ION_IOC_TAG userspace populates the handle field with
> + * the
Interestingly, I am able to reload i915 and drm. Our CI has tests for
i915 unload/reload, but does not check drm. In any case the config problem
should not impact the reloadability of i915.
==
Sorry that I didn't make myself clear. In order to replace the default i915
module with an updated o
On Wed, Oct 12, 2016 at 03:08:24AM +, Sun, Jing A wrote:
> Interestingly, I am able to reload i915 and drm. Our CI has tests for
> i915 unload/reload, but does not check drm. In any case the config
> problem should not impact the reloadability of i915.
> ==
> Sorry that I didn't make myself
On Tue, Oct 11, 2016 at 10:24:23PM +0100, Brian Starkey wrote:
> On Tue, Oct 11, 2016 at 10:02:43PM +0200, Daniel Vetter wrote:
> > The problem with just that is that there's lots of different things
> > that can feed into the overall needs_modeset variable. That's why we
> > split it up into multi
On Tue, Oct 11, 2016 at 04:15:04PM -0700, Stefan Agner wrote:
> The current fbdev emulation does not allow to push back changes in
> width, height or depth to KMS, hence reject any changes with an
> error. This makes sure that fbdev ioctl's fail properly and user
> space does not assume that change
Hi Eric,
On Tue, Oct 11, 2016 at 12:01:14PM -0700, Eric Anholt wrote:
>Brian Starkey writes:
>
>> Hi,
>>
>> This RFC series introduces a new connector type:
>> DRM_MODE_CONNECTOR_WRITEBACK
>> It is a follow-on from a previous discussion: [1]
>>
>> Writeback connectors are used to expose the memo
part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/faacb826/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/b1e0e045/attachment.html>
https://bugzilla.kernel.org/show_bug.cgi?id=177041
--- Comment #1 from Michel Dänzer ---
Can you try a newer kernel, ideally 4.8.y? I seem to remember running into this
before, but no longer with current kernels. Unfortunately, I don't remember
specifically how this was fixed.
--
You are recei
Am 12.10.2016 um 08:17 schrieb Dan Carpenter:
> debugfs_create_file() returns NULL on error, it only returns error
> pointers if debugfs isn't enabled in the config and we checked for that
> earlier so it can't happen.
>
> Fixes: 4f4824b55650 ('drm/amd/amdgpu: Convert ring debugfs entries to binary
I think "installing a kernel with my changes for both drm and i915" takes more
time and effort to complete than "only updating DRM/i915 modules without
rebuilding the whole kernel". In some cases, that's beneficial.
Also reloadablility is always a good thing to have and I truly hope
Hajda/Iwai'
Am 12.10.2016 um 01:50 schrieb Ruchi Kandoi:
> This patchstack adds memtrack hooks into dma-buf and ion. If there's upstream
> interest in memtrack, it can be extended to other memory allocators as well,
> such as GEM implementations.
We have run into similar problems before. Because of this I alr
because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/d66af789/attachment.html>
gt;xres_virtual, var->yres_virtual,
>
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/51786b07/attachment.sig>
From: Michel Dänzer
Signed-off-by: Michel Dänzer
---
The corresponding kernel changes have landed in Linus' tree.
include/drm/drm.h | 1 +
include/drm/drm_mode.h | 39 ---
xf86drmMode.c | 16
xf86drmMode.h | 3 +++
The drm callback ->detect and ->get_modes seems is not power safe,
they may be called when device is power off, do register access on
detect or get_modes will cause system die.
Here is the path call ->detect before analogix_dp power on
[] analogix_dp_detect+0x44/0xdc
[]
drm_helper_probe_single_co
On a laptop that tracks the latest stable release (Ie, it now runs
v4.8.1) I see this WARNING
   WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)
Full trace pasted below. I never saw this WARNING before v4.8. Since
v4.8 I've had it in all (four, actually) boots.
What am I expected to do about
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/e2118efc/attachment.html>
On Tue, Oct 11, 2016 at 04:15:04PM -0700, Stefan Agner wrote:
> The current fbdev emulation does not allow to push back changes in
> width, height or depth to KMS, hence reject any changes with an
> error. This makes sure that fbdev ioctl's fail properly and user
> space does not assume that change
On Wed, 12 Oct 2016, "Sun, Jing A" wrote:
> I think "installing a kernel with my changes for both drm and i915"
> takes more time and effort to complete than "only updating DRM/i915
> modules without rebuilding the whole kernel". In some cases, that's
> beneficial.
It's possible to change and reb
On ke, 2016-10-12 at 11:56 +0200, Paul Bolle wrote:
> On a laptop that tracks the latest stable release (Ie, it now runs
> v4.8.1) I see this WARNING
> Â Â Â WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)
>
> Full trace pasted below. I never saw this WARNING before v4.8. Since
> v4.8 I've had it
> A recent cleanup changed the kmalloc() + copy_from_user() to
> memdup_user() but the error handling wasn't updated so we might call
> kfree(-EFAULT) and crash.
>
> Fixes: a6e3918bcdb1 ('GPU-DRM-Savage: Use memdup_user() rather than
> duplicating')
> Signed-off-by: Dan Carpenter
>
> diff --git
On 11 October 2016 at 10:33, Jani Nikula wrote:
> On Tue, 11 Oct 2016, "Sun, Jing A" wrote:
>> It's needed that DRM Driver module could be removed and reloaded after
>> kernel booting on the projects that I have been working on, and I hope
>> such module type change could be accepted. Looks like
On ti, 2016-10-11 at 12:03 -0700, Robert Bragg wrote:
> > > +Â Â Â Â Â Â Â Â case DRM_I915_PERF_PROP_MAX:
> > > +Â Â Â Â Â Â Â Â Â Â Â Â BUG();
> >
> > We already handle this case above, but I guess we still need this in
> > order to silence gcc...
>
> right, and preferable to h
>> Date: Thu, 18 Aug 2016 21:28:58 +0200
>>
>> The kfree() function was called in a few cases by the
>> savage_bci_cmdbuf() function during error handling
>> even if a passed variable contained a null pointer.
>>
>> Adjust jump targets according to the Linux coding style convention.
>>
>> Signed-of
On Wed, 2016-10-12 at 14:08 +0300, Joonas Lahtinen wrote:
> Bisecting the offending commit between v4.8 and v4.8.1 would be a good
> start.
That would be between v4.7 and v4.8. (I guess my report was ambiguous.)
That might take some time. Because bisecting always takes a long time
and especially
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/527f1b70/attachment.html>
Hi Grazvydas and Alex,
We needed to disable dpm when rmmod amdgpu for this issue.
I am checking the function of disable dpm task.
Best Regards
Rex
-Original Message-
From: Alex Deucher [mailto:alexdeuc...@gmail.com]
Sent: Wednesday, October 12, 2016 4:01 AM
To: Grazvydas Ignotas; Zhu,
On Wed, 12 Oct 2016, Emil Velikov wrote:
> On 11 October 2016 at 10:33, Jani Nikula
> wrote:
>> On Tue, 11 Oct 2016, "Sun, Jing A" wrote:
>>> It's needed that DRM Driver module could be removed and reloaded after
>>> kernel booting on the projects that I have been working on, and I hope
>>> suc
On Wed, 12 Oct 2016, Paul Bolle wrote:
> On Wed, 2016-10-12 at 14:08 +0300, Joonas Lahtinen wrote:
>> Bisecting the offending commit between v4.8 and v4.8.1 would be a good
>> start.
>
> That would be between v4.7 and v4.8. (I guess my report was ambiguous.)
>
> That might take some time. Because
On Wed, 2016-10-12 at 17:34 +0300, Jani Nikula wrote:
> In the mean time, please file a bug over at [1] so we don't lose
> track.
Done: Â https://bugs.freedesktop.org/show_bug.cgi?id=98214
Paul Bolle
On Wed, Oct 12, 2016 at 6:22 AM, Mark yao wrote:
>
> I'm not familiar with the analogix driver, maybe use a power reference count
> would better then direct power on/off analogix_dp.
>
> Does anyone has the idea to protect detect and get_modes context?
>
I'm not sure a reference count is going to
Hi Michel,
On 12 October 2016 at 10:41, Michel Dänzer wrote:
> From: Michel Dänzer
>
> Signed-off-by: Michel Dänzer
> ---
>
> The corresponding kernel changes have landed in Linus' tree.
>
> include/drm/drm.h | 1 +
> include/drm/drm_mode.h | 39 ---
On 2016-10-12 03:42, Ville Syrjälä wrote:
> On Tue, Oct 11, 2016 at 04:15:04PM -0700, Stefan Agner wrote:
>> The current fbdev emulation does not allow to push back changes in
>> width, height or depth to KMS, hence reject any changes with an
>> error. This makes sure that fbdev ioctl's fail prop
e bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/29951c2a/attachment.html>
On Wed, Oct 12, 2016 at 08:55:45AM -0700, Stefan Agner wrote:
> On 2016-10-12 03:42, Ville Syrjälä wrote:
> > On Tue, Oct 11, 2016 at 04:15:04PM -0700, Stefan Agner wrote:
> >> The current fbdev emulation does not allow to push back changes in
> >> width, height or depth to KMS, hence reject any
On Wed, Oct 12, 2016 at 5:20 AM, Christian König
wrote:
> Am 12.10.2016 um 08:17 schrieb Dan Carpenter:
>>
>> debugfs_create_file() returns NULL on error, it only returns error
>> pointers if debugfs isn't enabled in the config and we checked for that
>> earlier so it can't happen.
>>
>> Fixes: 4
On 2016-10-12 09:12, Ville Syrjälä wrote:
> On Wed, Oct 12, 2016 at 08:55:45AM -0700, Stefan Agner wrote:
>> On 2016-10-12 03:42, Ville Syrjälä wrote:
>> > On Tue, Oct 11, 2016 at 04:15:04PM -0700, Stefan Agner wrote:
>> >> The current fbdev emulation does not allow to push back changes in
>> >
Hello Eric Anholt,
The patch d5b1a78a772f: "drm/vc4: Add support for drawing 3D frames."
from Nov 30, 2015, leads to the following static checker warning:
drivers/gpu/drm/vc4/vc4_gem.c:797 vc4_wait_for_seqno_ioctl_helper()
warn: ret is never (-4)
drivers/gpu/drm/vc4/vc4_gem.c
On Wed, 2016-10-12 at 14:06 +0200, Paul Bolle wrote:
> That might take some time. Because bisecting always takes a long time
> and especially since hitting this WARNING sometimes takes over an hour.
> Anyhow, please prod me if I stay silent for too long.
For the record: I just had to power cycle t
> -Original Message-
> From: Markus Trippelsdorf [mailto:markus at trippelsdorf.de]
> Sent: Wednesday, October 12, 2016 4:40 PM
> To: Deucher, Alexander
> Cc: Koenig, Christian; dri-devel at lists.freedesktop.org
> Subject: commit a481daa88fd (drm/radeon: always apply pci shutdown
> callbac
Since:
commit a481daa88fd4d6b54f25348972bba10b5f6a84d0
Author: Alex Deucher
Date: Thu Sep 22 14:43:50 2016 -0400
drm/radeon: always apply pci shutdown callbacks
We can't properly detect all hypervisors and we
need this to properly tear down the hardware.
I cannot reboot my machin
been using to implement the VGA hack we use on the CHIP.
> >
> > Can you send that patch?
>
> Actually, Ville suggested a slightly different approach: use the
> ->src and ->dst in drm_plane_state.
After more tests, it turns out that it's actually simpler than
that
The hardware is able to take negative coordinates.
Sorry for the noise,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/14a89d77/attachment.sig>
On 10/11/2016 04:50 PM, Ruchi Kandoi wrote:
> Any process holding a reference to these buffers will keep the kernel from
> reclaiming its backing pages. mm counters don't provide a complete picture of
> these allocations, since they only account for pages that are mapped into a
> process's address
Hi Inki,
On 08/15/2016 10:40 PM, Inki Dae wrote:
>>
>> okay the very first commit that added IOMMU support
>> introduced the code that rejects non-contig gem memory
>> type without IOMMU.
>>
>> commit 0519f9a12d0113caab78980c48a7902d2bd40c2c
>> Author: Inki Dae
>> Date: Sat Oct 20 07:53:42 201
On 10/12/2016 05:11 PM, Shuah Khan wrote:
+ Fixing Krzysztof Kozlowski address.
> Hi Inki,
>
> On 08/15/2016 10:40 PM, Inki Dae wrote:
>
>>>
>>> okay the very first commit that added IOMMU support
>>> introduced the code that rejects non-contig gem memory
>>> type without IOMMU.
>>>
>>> commit
^
> Presumably this could be removed?
I think so. Want to send the patch?
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20161012/6d50a618/attachment.sig>
56 matches
Mail list logo
