- 26 Sep, 2019 1 commit
-
-
Ting Fu authored
Signed-off-by:
Ting Fu <ting.fu@intel.com> Signed-off-by:
Ruiling Song <ruiling.song@intel.com>
-
- 11 Sep, 2019 1 commit
-
-
Lynne authored
-
- 12 Jun, 2019 1 commit
-
-
Ruiling Song authored
Signed-off-by:
Ruiling Song <ruiling.song@intel.com>
-
- 02 May, 2019 1 commit
-
-
James Darnley authored
-
- 03 Jan, 2019 1 commit
-
-
James Almer authored
Reviewed-by:
Paul B Mahol <onemda@gmail.com> Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 08 May, 2018 1 commit
-
-
Clément Bœsch authored
-
- 24 Mar, 2018 1 commit
-
-
Martin Vignali authored
-
- 08 Mar, 2018 1 commit
-
-
Yingming Fan authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 28 Jan, 2018 1 commit
-
-
Martin Vignali authored
-
- 19 Dec, 2017 2 commits
-
-
James Almer authored
This reverts commit adff97be. It currently fails on Windows targets. Signed-off-by:
James Almer <jamrial@gmail.com>
-
Martin Vignali authored
-
- 13 Dec, 2017 1 commit
-
-
Martin Vignali authored
-
- 03 Dec, 2017 1 commit
-
-
Martin Vignali authored
-
- 21 Nov, 2017 2 commits
-
-
Martin Vignali authored
-
Martin Vignali authored
-
- 17 Sep, 2017 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 08 Sep, 2017 1 commit
-
-
Clément Bœsch authored
On ARM platforms, accessing the PMU registers requires special user access permissions. Since there is no other way to get accurate timers, the current implementation of timers in FFmpeg rely on these registers. Unfortunately, enabling user access to these registers on Linux is not trivial, and generally involve compiling a random and unreliable github kernel module, or patching somehow your kernel. Such module is very unlikely to reach the upstream anytime soon. Quoting Robin Murphin from ARM: > Say you do give userspace direct access to the PMU; now run two or more > programs at once that believe they can use the counters for their own > "minimal-overhead" profiling. Have fun interpreting those results... > > And that's not even getting into the implications of scheduling across > different CPUs, CPUidle, etc. where the PMU state is completely beyond > userspace's control. In general, the plan to provide userspace with > something which might happen to just about work in a few corner cases, > but is meaningless, misleading or downright broken in all others, is to > never do so. As a result, the alternative is to use the Performance Monitoring Linux API which makes use of these registers internally (assuming the PMU of your ARM board is supported in the kernel, which is definitely not a given...). While the Linux API is obviously cross platform, it does have a significant overhead which needs to be taken into account. As a result, that mode is only weakly enabled on ARM platforms exclusively. Note on the non flexibility of the implementation: the timers (native FFmpeg vs Linux API) are selected at compilation time to prevent the need of function calls, which would result in a negative impact on the cycle counters.
-
- 13 Jul, 2017 1 commit
-
-
James Almer authored
Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 03 Jul, 2017 1 commit
-
-
Matthieu Bouron authored
-
- 28 Jun, 2017 1 commit
-
-
Clément Bœsch authored
This includes various fixes and improvements from James Almer. Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 21 Jun, 2017 1 commit
-
-
Diego Biurrun authored
None of them are specific to the YASM assembler. (Cherry-picked from libav commit 39e208f4) Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 14 Jun, 2017 2 commits
-
-
James Almer authored
Ported from libavutil/tests/float_dsp.c Signed-off-by:
James Almer <jamrial@gmail.com>
-
James Almer authored
Meant for DSP functions returning a float or double, as they'd fail if emms is called after every run on x86_32. Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 11 Apr, 2017 1 commit
-
-
James Almer authored
Tested-by:
Michael Niedermayer <michael@niedermayer.cc> Signed-off-by:
James Almer <jamrial@gmail.com>
-
- 01 Mar, 2017 1 commit
-
-
Diego Biurrun authored
None of them are specific to the YASM assembler.
-
- 22 Oct, 2016 1 commit
-
-
Alexandra Hájková authored
-
- 16 Oct, 2016 2 commits
-
-
Martin Storsjö authored
This, combined with clobbering the stack space prior to the call, increases the chances of finding cases where 32 bit parameters are erroneously treated as 64 bit. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 02 Oct, 2016 1 commit
-
-
Alexandra Hájková authored
Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
- 22 Sep, 2016 2 commits
-
-
Anton Khirnov authored
-
Anton Khirnov authored
-
- 03 Aug, 2016 1 commit
-
-
Ronald S. Bultje authored
Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
- 22 Jul, 2016 1 commit
-
-
Alexandra Hájková authored
Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
- 08 Jul, 2016 1 commit
-
-
Martin Storsjö authored
The tests are inspired by similar tests for vp9 by Ronald Bultje. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 21 Jun, 2016 1 commit
-
-
Martin Storsjö authored
The functions may not clean up properly after using MMX registers. For the normal testing calls, the checkasm_checked_call functions will do the cleanup (and check that functions that should clean up do it as well), but when benchmarking functions that don't clean up, we don't currently properly clean up at all. This causes issues if a benchmarked function is followed by testing of a function that is supposed to not clobber the MMX/FPU state but doesn't touch it at all. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 17 Jun, 2016 1 commit
-
-
Martin Storsjö authored
The tests are inspired by similar tests for vp9 by Ronald Bultje. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 12 Apr, 2016 1 commit
-
-
Ronald S. Bultje authored
-
- 18 Feb, 2016 1 commit
-
-
Diego Biurrun authored
-
- 14 Feb, 2016 1 commit
-
-
Timothy Gu authored
-
- 31 Jan, 2016 1 commit
-
-
Timothy Gu authored
-