On Mon, Aug 24, 2015 at 07:09:15AM +, Zhou, David(ChunMing) wrote:
> Hi Dan,
> Thanks for figuring out that.
> >274 min_offset = obj->placements[0].fpfn << PAGE_SHIFT;
> >275 max_offset = obj->placements[0].lpfn << PAGE_SHIFT;
> Maybe should be:
> min_offset = o
On 08/24/2015 10:16 PM, Rob Clark wrote:
> On Mon, Aug 24, 2015 at 4:20 PM, Samuel Pitoiset
> wrote:
>> Hi Hai,
>>
>> I don't know what those bits are used for, but I'm a bit curious about how
>> did you find them?
>>
>> Also, the next time don't forget to send patches related to envytools to
>>
rg/archives/dri-devel/attachments/20150824/0625da7c/attachment.html>
ttp://lists.freedesktop.org/archives/dri-devel/attachments/20150824/acf78ce6/attachment.html>
s had an update to
> version 6.1.
So can I close this?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/7f2a8bad/attachment.html>
Hi Hai,
I don't know what those bits are used for, but I'm a bit curious about
how did you find them?
Also, the next time don't forget to send patches related to envytools to
nouveau at lists.freedesktop.org
(or better send a pull request from github).
Thanks.
On 08/13/2015 11:44 PM, Hai Li w
:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/608ef967/attachment.html>
On 2015ë
08ì 16ì¼ 01:26, Gustavo Padovan wrote:
> From: Gustavo Padovan
>
> .prepare_plane() and .cleanup_plane() allows to perform extra operations
> before and after the update of planes. For FIMD for example this will
> be used to enable disable the shadow protection bit.
>
> Signed-off-
On Mon, Aug 24, 2015 at 8:00 PM, Eric B Munson wrote:
> On Mon, 24 Aug 2015, Konstantin Khlebnikov wrote:
>
>> On Mon, Aug 24, 2015 at 6:55 PM, Eric B Munson wrote:
>> > On Mon, 24 Aug 2015, Konstantin Khlebnikov wrote:
>> >
>> >> On Mon, Aug 24, 2015 at 6:09 PM, Eric B Munson
>> >> wrote:
>> >
https://bugzilla.kernel.org/show_bug.cgi?id=103271
--- Comment #6 from Kevin ---
I just uploaded the dmesg output. I have never done bisecting before. Is this a
good place to start?
https://wiki.archlinux.org/index.php/Bisecting_bugs
--
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=103271
--- Comment #5 from Kevin ---
Created attachment 185731
--> https://bugzilla.kernel.org/attachment.cgi?id=185731&action=edit
dmesg output while running linux-git-4.2rc8.r0.gc13dcf9-1-x86_64
This is the dmesg output while running 4.2rc8 built f
https://bugzilla.kernel.org/show_bug.cgi?id=103271
--- Comment #4 from Kevin ---
I did not change any hardware. I tried changing the connection to the monitor
because I had issues a few months back with DisplayPort but that didn't help
here. I don't seem to have an xorg log in /var/log/ but and t
Hi Jingoo,
å¨ 08/24/2015 03:40 PM, Jingoo Han åé:
> On 2015. 8. 24., at AM 9:43, Krzysztof Kozlowski
> wrote:
>> 2015-08-24 8:23 GMT+09:00 Rob Herring :
On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
Analogix dp driver is split from exynos dp driver, so we just
make an c
Hi Krzysztof,
å¨ 08/24/2015 12:20 PM, Krzysztof Kozlowski åé:
> On 24.08.2015 11:42, Yakir Yang wrote:
>> Hi Krzysztof,
>>
>> å¨ 08/23/2015 07:43 PM, Krzysztof Kozlowski åé:
>>> 2015-08-24 8:23 GMT+09:00 Rob Herring :
On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
> Analogi
On 08/24/2015 03:01 PM, Tiago Vignatti wrote:
> yup, I think so. So IIUC the main changes needed for the drivers
> implement 2D sync lies in the dma_buf_sync_2d structure only. I.e.
> there's nothing really to be changed in the common code, right?
Do we have any special requirements in how we want
On 08/24/2015 07:12 PM, Daniel Stone wrote:
> Hi,
>
> On 24 August 2015 at 18:10, Thomas Hellstrom wrote:
>> On 08/24/2015 07:04 PM, Daniel Stone wrote:
>>> On 24 August 2015 at 17:56, Thomas Hellstrom
>>> wrote:
On 08/24/2015 05:52 PM, Daniel Stone wrote:
> I still don't think this ame
On Mon, Aug 24, 2015 at 6:55 PM, Eric B Munson wrote:
> On Mon, 24 Aug 2015, Konstantin Khlebnikov wrote:
>
>> On Mon, Aug 24, 2015 at 6:09 PM, Eric B Munson wrote:
>> > On Mon, 24 Aug 2015, Vlastimil Babka wrote:
>> >
>> >> On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
>> >> >On Mon, Aug
On 08/24/2015 07:04 PM, Daniel Stone wrote:
> Hi,
>
> On 24 August 2015 at 17:56, Thomas Hellstrom wrote:
>> On 08/24/2015 05:52 PM, Daniel Stone wrote:
>>> I still don't think this ameliorates the need for batching: consider
>>> the case where you update two disjoint screen regions and want them
Hi, Daniel,
On 08/24/2015 05:52 PM, Daniel Stone wrote:
> Hi Thomas,
>
> On 24 August 2015 at 10:50, Thomas Hellstrom wrote:
>> In any case, Ideally I'd want the struct dma_buf_sync look something like
>>
>> enum dma_buf_sync_flags {
>> DMA_BUF_SYNC_READ = (1 << 0),
>> DMA_BUF_SYN
On Mon, Aug 24, 2015 at 6:09 PM, Eric B Munson wrote:
> On Mon, 24 Aug 2015, Vlastimil Babka wrote:
>
>> On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
>> >On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
>> >>On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
>>
>>
>> >>
On Mon, Aug 24, 2015 at 7:32 AM, Hai Li wrote:
> Hi Werner,
>
> Yes, the register is to adjust hs_zero.
> Could you share the panel's video timing and dphy timings (or the panel DT),
> used by downstream driver?
>
> The dphy timing calculations in the phy driver are from the excel sheet as
> wel
Am Montag, 24. August 2015, 09:48:27 schrieb Rob Herring:
> On Mon, Aug 24, 2015 at 7:57 AM, Russell King - ARM Linux
> > When we adopted the graph bindings for iMX DRM, I thought exactly at that
> > time "it would be nice if this could become the standard for binding DRM
> > components together" b
Hi,
On 24 August 2015 at 18:10, Thomas Hellstrom wrote:
> On 08/24/2015 07:04 PM, Daniel Stone wrote:
>> On 24 August 2015 at 17:56, Thomas Hellstrom
>> wrote:
>>> On 08/24/2015 05:52 PM, Daniel Stone wrote:
I still don't think this ameliorates the need for batching: consider
the case
Hi,
On 24 August 2015 at 17:56, Thomas Hellstrom wrote:
> On 08/24/2015 05:52 PM, Daniel Stone wrote:
>> I still don't think this ameliorates the need for batching: consider
>> the case where you update two disjoint screen regions and want them
>> both flushed. Either you issue two separate sync
Signed-off-by: Emil Velikov
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index c2a8ed1..1d7bd5b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -173,7 +173,7 @@ MAYBE_WARN="-Wall -Wextra \
-Wpacked -Wswitch-enum -Wmissing-format
We're about to remove the -Wno flag from configure.ac which will lead
to a lot of unnecessary spam.
Signed-off-by: Emil Velikov
---
intel/intel_decode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/intel/intel_decode.c b/intel/intel_decode.c
index 345d457..e7aef74 100644
--- a/intel/in
Cc: nouveau at lists.freedesktop.org
Signed-off-by: Emil Velikov
---
nouveau/abi16.c | 13 ++---
nouveau/nouveau.c | 6 +++---
2 files changed, 13 insertions(+), 6 deletions(-)
diff --git a/nouveau/abi16.c b/nouveau/abi16.c
index 4ca0bfb..59bc436 100644
--- a/nouveau/abi16.c
+++ b/nou
In the latest version of CUnit the fourth parameter of the CU_SuiteInfo
struct is pSetUpFunc rather than *pTests.
Seems like the CUnit ABI broke at some point, so let's the the robust
thing and use c99 designated initializers to correctly populate the
struct(s).
Cc: Alex Deucher
Cc: Leo Liu
Sig
The remaining two templates are modified on the fly, depending on the
type of test to be performed.
Cc: Alex Deucher
Cc: Leo Liu
Signed-off-by: Emil Velikov
---
tests/amdgpu/vce_ib.h | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/tests/amdgpu/vce
Cc: Alex Deucher
Cc: Leo Liu
Signed-off-by: Emil Velikov
---
tests/amdgpu/uvd_messages.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tests/amdgpu/uvd_messages.h b/tests/amdgpu/uvd_messages.h
index 44bcacc..00235cb 100644
--- a/tests/amdgpu/uvd_messages.h
+++ b
Cc: Alex Deucher
Cc: Leo Liu
Signed-off-by: Emil Velikov
---
tests/amdgpu/cs_tests.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/amdgpu/cs_tests.c b/tests/amdgpu/cs_tests.c
index 416f36b..dfbf5af 100644
--- a/tests/amdgpu/cs_tests.c
+++ b/tests/amdgpu/cs_tests.
Cc: freedreno at lists.freedesktop.org
Signed-off-by: Emil Velikov
---
freedreno/freedreno_priv.h | 6 +++---
freedreno/freedreno_ringbuffer.h | 2 +-
freedreno/kgsl/kgsl_bo.c | 2 +-
freedreno/kgsl/kgsl_device.c | 2 +-
freedreno/kgsl/kgsl_pipe.c | 2 +-
freedreno/kgsl/kg
Annotate the data as static const and use C99 designated initializers.
Signed-off-by: Emil Velikov
---
radeon/radeon_bo_gem.c | 23 ---
radeon/radeon_bo_int.h | 2 +-
radeon/radeon_cs_gem.c | 20 ++--
radeon/radeon_cs_int.h | 2 +-
4 files changed, 24 insert
Signed-off-by: Emil Velikov
---
libkms/linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libkms/linux.c b/libkms/linux.c
index b735527..6e0da83 100644
--- a/libkms/linux.c
+++ b/libkms/linux.c
@@ -149,7 +149,7 @@ struct create_record
int (*func)(int fd, struct km
Signed-off-by: Emil Velikov
---
tests/modetest/cursor.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tests/modetest/cursor.c b/tests/modetest/cursor.c
index 62a50ef..d8a19bd 100644
--- a/tests/modetest/cursor.c
+++ b/tests/modetest/cursor.c
@@ -70,7 +70,7 @@ stat
Signed-off-by: Emil Velikov
---
amdgpu/Makefile.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/amdgpu/Makefile.am b/amdgpu/Makefile.am
index 37f7198..cf7bc1b 100644
--- a/amdgpu/Makefile.am
+++ b/amdgpu/Makefile.am
@@ -25,7 +25,7 @@
include Makefile.sources
AM_CFLAGS =
Signed-off-by: Emil Velikov
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index f07507b..c2a8ed1 100644
--- a/configure.ac
+++ b/configure.ac
@@ -174,7 +174,7 @@ MAYBE_WARN="-Wall -Wextra \
-Wstrict-aliasing=2 -Winit-self \
-Wde
Just like we do for the original exec()
Cc: intel-gfx at lists.freedesktop.org
Signed-off-by: Emil Velikov
---
intel/intel_bufmgr_gem.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/intel/intel_bufmgr_gem.c b/intel/intel_bufmgr_gem.c
index cf55a53..5287419 100644
--- a/intel/intel_bufmg
Cc: intel-gfx at lists.freedesktop.org
Signed-off-by: Emil Velikov
---
intel/intel_bufmgr_fake.c | 2 +-
intel/intel_bufmgr_gem.c | 7 +++
intel/intel_decode.c | 7 ++-
3 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/intel/intel_bufmgr_fake.c b/intel/intel_bufmgr_fak
No real issue here, but let's fix these so that real issues don't get
lost in the spam.
Signed-off-by: Emil Velikov
---
tests/modetest/modetest.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c
index 3a545c3..3b01918 100644
--- a/tests/
Just remove the second (shadowing) declaration of ret.
Signed-off-by: Emil Velikov
---
tests/vbltest/vbltest.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tests/vbltest/vbltest.c b/tests/vbltest/vbltest.c
index 4200adb..e27f45c 100644
--- a/tests/vbltest/vbltest.c
+++ b/tests/vbltest/vblt
Hi Thomas,
On 24 August 2015 at 10:50, Thomas Hellstrom wrote:
> In any case, Ideally I'd want the struct dma_buf_sync look something like
>
> enum dma_buf_sync_flags {
> DMA_BUF_SYNC_READ = (1 << 0),
> DMA_BUF_SYNC_WRITE = (2 << 0),
> DMA_BUF_SYNC_RW = (3 << 0),
>
On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
> On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
>>>
>>>
>>> I am in the middle of implementing lock on fault this way, but I cannot
>>> see how we will hanlde mremap of a lock on fault region. Say we have
>>> the following:
>>>
>>>
On Mon, Aug 24, 2015 at 4:26 PM, Samuel Pitoiset
wrote:
>
>
> On 08/24/2015 10:16 PM, Rob Clark wrote:
>>
>> On Mon, Aug 24, 2015 at 4:20 PM, Samuel Pitoiset
>> wrote:
>>>
>>> Hi Hai,
>>>
>>> I don't know what those bits are used for, but I'm a bit curious about
>>> how
>>> did you find them?
>>>
On 2015. 8. 24., at AM 9:43, Krzysztof Kozlowski
wrote:
>
> 2015-08-24 8:23 GMT+09:00 Rob Herring :
>>> On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
>>> Analogix dp driver is split from exynos dp driver, so we just
>>> make an copy of exynos_dp.txt, and then simplify exynos_dp.txt
>>>
>>
All functions from the public API only operation on
struct g2d_context*, so this shouldn't break too much.
Make the context private since we don't want the
user to modify its content directly. Also remove
the defines that were only used for fields of
g2d_context.
Signed-off-by: Tobias Jakobi
---
On 08/24/2015 03:50 PM, Konstantin Khlebnikov wrote:
> On Mon, Aug 24, 2015 at 4:30 PM, Vlastimil Babka wrote:
>> On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
I am in the middle of implementing lock on fault this way, but I cannot
see how we will hanlde mremap of a lock
> But with this, the user must remember what areas are locked with
> >> > MLOCK_LOCKONFAULT and which are locked the with prepopulate so the
> >> > correct mremap flags can be used.
> >> >
> >>
> >> Yep. Shouldn't be hard. You anyway have to do some changes in user-space.
> >>
> >
> > Sorry if I wasn't clear enough in my last reply, I think forcing
> > userspace to track this is the wrong choice. The VM system is
> > responsible for tracking these attributes and should continue to be.
>
> Userspace tracks addresses and sizes of these areas. Plus mremap obviously
> works only with page granularity so memory allocator in userspace have to know
> a lot about these structures. So keeping one more bit isn't a rocket science.
>
Fair enough, however, my current implementation does not require that
userspace keep track of any extra information. With the VM_LOCKONFAULT
flag mremap() keeps the properties that were set with mlock() or
equivalent across remaps.
> >
> >>
> >> Much simpler for users-pace solution is a mm-wide flag which turns all
> >> further
> >> mlocks and MAP_LOCKED into lock-on-fault. Something like
> >> mlockall(MCL_NOPOPULATE_LOCKED).
> >
> > This set certainly adds the foundation for such a change if you think it
> > would be useful. That particular behavior was not part of my inital use
> > case though.
> >
>
> This looks like much easier solution: you don't need new syscall and after
> enabling that lock-on-fault mode userspace still can get old behaviour simply
> by touching newly locked area.
Again, this suggestion requires that userspace know more about VM than
with my implementation and will require it to walk an entire mapping
before use to fault it in if required. With the current implementation,
mlock continues to function as it has, with the additional flexibility
of being able to request that areas not be prepopulated.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/70960f61/attachment-0001.sig>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/b21e9f00/attachment.html>
On Mon, Aug 24, 2015 at 4:26 PM, Samuel Pitoiset
wrote:
> On 08/24/2015 10:16 PM, Rob Clark wrote:
>> On Mon, Aug 24, 2015 at 4:20 PM, Samuel Pitoiset
>> wrote:
>>>
>>> Hi Hai,
>>>
>>> I don't know what those bits are used for, but I'm a bit curious about
>>> how
>>> did you find them?
>>>
>>> Al
On Mon, Aug 24, 2015 at 4:20 PM, Samuel Pitoiset
wrote:
> Hi Hai,
>
> I don't know what those bits are used for, but I'm a bit curious about how
> did you find them?
>
> Also, the next time don't forget to send patches related to envytools to
> nouveau at lists.freedesktop.org
> (or better send a
Add a prefix to the messages printed to the console via
printf() and fprintf() so that one can easily see where
the message comes from.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 30 --
1 file changed, 16 insertions(+), 14 deletions(-)
diff --git a/exy
The function currently checks for each added command
if an overflow of the corresponding command buffers
occurs, but none of the callers ever checks the
return value.
Since all callers are now converted to use
g2d_check_space() simplify the function.
(1) The overflow checks become asserts, so the
The g2d_point_val union consists of two coordinates of 16
bits. Whenever this union is used though, both coordinates
are explicitly set. Hence prior initialization is unnecessary.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 19 ---
1 file changed, 19 deletions(-)
d
We now validate the blending mode via g2d_validate_mode()
prior to feeding it to g2d_get_blend_op().
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/exynos/exynos_fimg2d.c b/exynos/exynos_fimg2d.c
index 4274a94..d708e91 100644
--- a
Apply the same transformation as in g2d_blend().
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 67 +-
1 file changed, 39 insertions(+), 28 deletions(-)
diff --git a/exynos/exynos_fimg2d.c b/exynos/exynos_fimg2d.c
index 5acccf8..4274a94
Move parameter validation to the top and also validate
the select mode of the source image and the requested
blending operation before starting command submission.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 66 +-
1 file changed, 39
The G2D headers define a number of modes through enums
(like e.g. color, select, repeat, etc.).
This introduces g2d_validate_select_mode() and
g2d_validate_blending_op() which validate a
select mode or blending operation respectively.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 44
Parameter validation goes to the top. Repeat mode is
checked first to make computation of space easier.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 53 --
1 file changed, 30 insertions(+), 23 deletions(-)
diff --git a/exynos/exynos_f
Move the parameter validation before buffer space checking
so that we can exit early if it fails.
Also don't reset the G2D context anymore in this situation
(since the buffers are not partially submitted).
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 26 ++
1
The amount of commands (regular and GEM) doesn't depend
on the input here.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/exynos/exynos_fimg2d.c b/exynos/exynos_fimg2d.c
index 1ae8adf..9b7bcce 100644
--- a/exynos/exynos_fimg2d.c
+++
This is going to be used to check if the command buffers have
enough space left prior to actual submission of the commands.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/exynos/exynos_fimg2d.c b/exynos/exynos_fimg2d
Use g2d_add_base_addr() for source and destination base
address just like all other calls.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 14 ++
1 file changed, 2 insertions(+), 12 deletions(-)
diff --git a/exynos/exynos_fimg2d.c b/exynos/exynos_fimg2d.c
index 4a88e0c..85
Empty command buffers are no error, we just don't have
anything to do for flushing then.
Signed-off-by: Tobias Jakobi
---
exynos/exynos_fimg2d.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/exynos/exynos_fimg2d.c b/exynos/exynos_fimg2d.c
index 24a06d0..4a88e0c 100644
--- a
Hello,
during the discussion about the last patchset touching the
fimg2d code, it became apparent that the error handling for
the command submission is currently unsatisfactory.
This series rewrites the handling. All functions that submit
command buffers now first check if enough space is availab
[CCing mesa-dev as mesa will need similar fixes]
Hi Christian,
On 24/08/15 10:43, Christian König wrote:
> From: Christian König
>
> Fixes the same problem as "intel: Serialize drmPrimeFDToHandle with
> struct_mutex".
>
> Signed-off-by: Christian König
> ---
> amdgpu/amdgpu_bo.c | 9
On Fri, Aug 21, 2015 at 12:17 PM, Mark Brown wrote:
> On Fri, Aug 21, 2015 at 05:21:07PM +0530, maruthi srinivas wrote:
>> On Fri, Aug 21, 2015 at 4:48 AM, Mark Brown wrote:
>
>> > We already have a driver for the DesignWare I2S controller. To repeat
>> > the concern I raised in a slightly diffe
reedesktop.org/archives/dri-devel/attachments/20150824/71b5e51c/attachment.html>
On Fri, 2015-08-21 at 16:39 -0300, Danilo Cesar Lemes de Paula wrote:
> Using pandoc as the Markdown engine cause some minor side effects as
> pandoc includes main tags for almost everything.
> Original Markdown support approach removes those main tags, but it
> caused
> some inconsistencies when
Hi guys,
On 24 August 2015 at 09:20, Christian König wrote:
> Hi Mathias,
>
> thanks for the good help and no problem with the Signed-off-by line. If you
> don't object we will just add a "Signed-off-by: Mathias Tillman
> " line when we push this patch to the repository.
>
> It's just for tracki
On 08/24/2015 12:17 PM, Konstantin Khlebnikov wrote:
>>
>> I am in the middle of implementing lock on fault this way, but I cannot
>> see how we will hanlde mremap of a lock on fault region. Say we have
>> the following:
>>
>> addr = mmap(len, MAP_ANONYMOUS, ...);
>> mlock(addr, len, MLO
Hi Yakir,
Am Montag, 24. August 2015, 20:48:01 schrieb Yakir Yang:
> å¨ 08/24/2015 12:20 PM, Krzysztof Kozlowski åé:
> > On 24.08.2015 11:42, Yakir Yang wrote:
> >> Hi Krzysztof,
> >>
> >> å¨ 08/23/2015 07:43 PM, Krzysztof Kozlowski åé:
> >>> 2015-08-24 8:23 GMT+09:00 Rob Herring :
> >>
On 08/24/2015 02:42 PM, Thomas Hellstrom wrote:
> On 08/24/2015 07:12 PM, Daniel Stone wrote:
>> Hi,
>>
>> On 24 August 2015 at 18:10, Thomas Hellstrom
>> wrote:
>>> On 08/24/2015 07:04 PM, Daniel Stone wrote:
On 24 August 2015 at 17:56, Thomas Hellstrom
wrote:
> On 08/24/2015 05:
In commit
d1675198e: drm/i915: Integrate GuC-based command submission
the drm.tmpl include lines reference the intel_guc_submission.c but the
patch adds the file i915_guc_submission.c. drm.tmpl fails to build with:
docproc: .//drivers/gpu/drm/i915/intel_guc_submission.c:
No such file or direct
On Sun, Aug 23, 2015 at 06:23:14PM -0500, Rob Herring wrote:
> On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
> > + -analogix,color-depth:
> > + number of bits per colour component.
> > + COLOR_6 = 0, COLOR_8 = 1, COLOR_10 = 2, COLOR_12 = 3
>
> This s
On Mon, Aug 24, 2015 at 1:42 PM, Thomas Hellstrom
wrote:
> On 08/24/2015 07:12 PM, Daniel Stone wrote:
>> Hi,
>>
>> On 24 August 2015 at 18:10, Thomas Hellstrom
>> wrote:
>>> On 08/24/2015 07:04 PM, Daniel Stone wrote:
On 24 August 2015 at 17:56, Thomas Hellstrom
wrote:
> On 08/
Both patches are Reviewed-by: Jammy Zhou
Regards,
Jammy
-Original Message-
From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
Christian K?nig
Sent: Monday, August 24, 2015 5:44 PM
To: dri-devel at lists.freedesktop.org
Subject: [PATCH 2/2] amdgpu: serialize dr
> -Original Message-
> From: Jerome Glisse [mailto:j.glisse at gmail.com]
> Sent: Monday, August 24, 2015 9:48 AM
> To: cpaul at redhat.com
> Cc: Deucher, Alexander; Koenig, Christian; David Airlie; dri-
> devel at lists.freedesktop.org; linux-kernel at vger.kernel.org; Jerome
> Glisse;
>
On 24.08.2015 11:42, Yakir Yang wrote:
> Hi Krzysztof,
>
> å¨ 08/23/2015 07:43 PM, Krzysztof Kozlowski åé:
>> 2015-08-24 8:23 GMT+09:00 Rob Herring :
>>> On Wed, Aug 19, 2015 at 9:50 AM, Yakir Yang wrote:
Analogix dp driver is split from exynos dp driver, so we just
make an copy of
On Fri, Aug 21, 2015 at 9:31 PM, Eric B Munson wrote:
> On Fri, 21 Aug 2015, Michal Hocko wrote:
>
>> On Thu 20-08-15 13:03:09, Eric B Munson wrote:
>> > On Thu, 20 Aug 2015, Michal Hocko wrote:
>> >
>> > > On Wed 19-08-15 17:33:45, Eric B Munson wrote:
>> > > [...]
>> > > > The group which asked
On Mon, Aug 24, 2015 at 12:34 PM, Emil Velikov
wrote:
> Signed-off-by: Emil Velikov
Reviewed-by: Alex Deucher
> ---
> amdgpu/Makefile.am | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/amdgpu/Makefile.am b/amdgpu/Makefile.am
> index 37f7198..cf7bc1b 100644
> --- a/am
On Mon, Aug 24, 2015 at 12:34 PM, Emil Velikov
wrote:
> In the latest version of CUnit the fourth parameter of the CU_SuiteInfo
> struct is pSetUpFunc rather than *pTests.
>
> Seems like the CUnit ABI broke at some point, so let's the the robust
> thing and use c99 designated initializers to corr
On Mon, Aug 24, 2015 at 12:34 PM, Emil Velikov
wrote:
> The remaining two templates are modified on the fly, depending on the
> type of test to be performed.
>
> Cc: Alex Deucher
> Cc: Leo Liu
> Signed-off-by: Emil Velikov
Reviewed-by: Alex Deucher
> ---
> tests/amdgpu/vce_ib.h | 24 ++
On Mon, Aug 24, 2015 at 12:34 PM, Emil Velikov
wrote:
> Cc: Alex Deucher
> Cc: Leo Liu
> Signed-off-by: Emil Velikov
Reviewed-by: Alex Deucher
> ---
> tests/amdgpu/uvd_messages.h | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/tests/amdgpu/uvd_messages.h
On Mon, Aug 24, 2015 at 12:34 PM, Emil Velikov
wrote:
> Annotate the data as static const and use C99 designated initializers.
>
> Signed-off-by: Emil Velikov
Reviewed-by: Alex Deucher
> ---
> radeon/radeon_bo_gem.c | 23 ---
> radeon/radeon_bo_int.h | 2 +-
> radeon/rad
On Mon, Aug 24, 2015 at 12:34 PM, Emil Velikov
wrote:
> Cc: Alex Deucher
> Cc: Leo Liu
> Signed-off-by: Emil Velikov
Reviewed-by: Alex Deucher
> ---
> tests/amdgpu/cs_tests.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tests/amdgpu/cs_tests.c b/tests/amdgpu
lem then we can add opposite flag for it:
> >>
> >> "MREMAP_NOPOPULATE"
> >> - do not populate new segment of locked areas
> >> - do not copy normal areas if possible (anonymous/special must be copied)
> >>
> >> addr = mmap(len, MAP_ANONYMOUS, ...);
> >> mlock(addr, len, MLOCK_ONFAULT);
> >> ...
> >> addr2 = mremap(addr, len, 2 * len, MREMAP_NOPOPULATE);
> >> ...
> >>
> >
> > But with this, the user must remember what areas are locked with
> > MLOCK_LOCKONFAULT and which are locked the with prepopulate so the
> > correct mremap flags can be used.
> >
>
> Yep. Shouldn't be hard. You anyway have to do some changes in user-space.
>
Sorry if I wasn't clear enough in my last reply, I think forcing
userspace to track this is the wrong choice. The VM system is
responsible for tracking these attributes and should continue to be.
>
> Much simpler for users-pace solution is a mm-wide flag which turns all further
> mlocks and MAP_LOCKED into lock-on-fault. Something like
> mlockall(MCL_NOPOPULATE_LOCKED).
This set certainly adds the foundation for such a change if you think it
would be useful. That particular behavior was not part of my inital use
case though.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/be63e9b6/attachment-0001.sig>
scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/8cd587cc/attachment.html>
On 08/24/2015 03:41 AM, Jerome Glisse wrote:
> On Sat, Aug 22, 2015 at 12:00:21AM +0200, Thomas Hellstrom wrote:
>> On 08/21/2015 06:00 PM, Jerome Glisse wrote:
>>> On Fri, Aug 21, 2015 at 04:15:53PM +0200, Thomas Hellstrom wrote:
On 08/21/2015 03:32 PM, Jerome Glisse wrote:
> On Fri, Aug
From: Mathias Tillman
For readdir_r(), the next directory entry is returned in caller-allocted
buffer (pointered by pent here).
https://bugs.freedesktop.org/show_bug.cgi?id=91704
Signed-off-by: Jammy Zhou
---
xf86drm.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/x
ic's usecase, but it's somewhat ugly.
> >>
> >
> > I don't think that this is the right solution, I would be really
> > surprised as a user if an area I locked with MLOCK_ONFAULT was then
> > fully locked and prepopulated after mremap().
>
> If mremap is the only problem then we can add opposite flag for it:
>
> "MREMAP_NOPOPULATE"
> - do not populate new segment of locked areas
> - do not copy normal areas if possible (anonymous/special must be copied)
>
> addr = mmap(len, MAP_ANONYMOUS, ...);
> mlock(addr, len, MLOCK_ONFAULT);
> ...
> addr2 = mremap(addr, len, 2 * len, MREMAP_NOPOPULATE);
> ...
>
But with this, the user must remember what areas are locked with
MLOCK_LOCKONFAULT and which are locked the with prepopulate so the
correct mremap flags can be used.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/8db1e94e/attachment-0001.sig>
Hi!
On 08/22/2015 01:06 AM, Tiago Vignatti wrote:
> Hi back!
>
> On 08/20/2015 03:48 AM, Thomas Hellstrom wrote:
>> Hi, Tiago!
>
> Something that the Chrome OS folks told me today is whether we could
> change the sync API to use a syscall for that instead. Reason for that
> is to eventually fit th
From: Christian König
Fixes the same problem as "intel: Serialize drmPrimeFDToHandle with
struct_mutex".
Signed-off-by: Christian König
---
amdgpu/amdgpu_bo.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/amdgpu/amdgpu_bo.c b/amdgpu/amdgpu_bo.c
index dab3804..
From: Christian König
It's not used any more.
Signed-off-by: Christian König
---
amdgpu/amdgpu_cs.c | 10 --
amdgpu/amdgpu_internal.h | 3 ---
2 files changed, 13 deletions(-)
diff --git a/amdgpu/amdgpu_cs.c b/amdgpu/amdgpu_cs.c
index 41071fd..ae78a4c 100644
--- a/amdgpu/amdg
ves/dri-devel/attachments/20150824/77cbd2ab/attachment.html>
attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/b7b74d02/attachment.html>
ignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/993b4211/attachment.html>
think so. MAP_POPULATE works only when mmap happens.
> >Flag MREMAP_POPULATE might be a good idea. Just for symmetry.
>
> Maybe, but please do it as a separate series.
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo at kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: mailto:"dont at kvack.org"> email at kvack.org
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/8a8c13d4/attachment-0001.sig>
Hi Werner,
Yes, the register is to adjust hs_zero.
Could you share the panel's video timing and dphy timings (or the panel DT),
used by downstream driver?
The dphy timing calculations in the phy driver are from the excel sheet as
well, I can check if there is any issue inside the calculation co
quot;/%s",
> > + ent->d_name);
> > +
> > free(pent);
> > closedir(sysdir);
> >
> > - snprintf(dev_name, sizeof(dev_name),
> DRM_DIR_NAME "/%s",
> > - ent->d_name);
> > return strdup(dev_name);
> > }
> > }
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20150824/fb484601/attachment-0001.html>
1 - 100 of 113 matches
Mail list logo