he xdp frame onto the destination CPU ptr_ring.
>>>>> This can occur on any cpu, thus multi-producer. On processing side,
>>>>> there is only the kthread created by the cpumap entry and bound to the
>>>>> specific cpu that is consuming entries. So
this adding latency, I choose to also flush every 8
frames (CPU_MAP_BULK_SIZE).
Looking at code I see this is also explained in a comment:
/* General idea: XDP packets getting XDP redirected to another CPU,
* will maximum be stored/queued for one driver ->poll() call. It is
* guaranteed that
On Tue, 21 May 2024 09:11:08 -0600
Shuah Khan wrote:
> Any thoughts on this patch?
Sorry, this one fell through the cracks. Daniel Bristot has been
maintaining his tools and I thought this was one of his changes.
I'll take a look at it.
-- Steve
On 4/3/24 19:10, Shuah Khan wrote:
Fix the following -Wformat-security compile warnings adding missing
format arguments:
latency-collector.c: In function ‘show_available’:
latency-collector.c:938:17: warning: format not a string literal and
no format arguments [-Wformat-security]
938
Fix the following -Wformat-security compile warnings adding missing
format arguments:
latency-collector.c: In function ‘show_available’:
latency-collector.c:938:17: warning: format not a string literal and
no format arguments [-Wformat-security]
938 | warnx(no_tracer_msg
Use tools/build/ makefiles to build latency-collector, inheriting
the benefits of it. For example: Before this patch, a missing
tracefs/traceevents headers will result in fail like this:
~/linux/tools/tracing/latency $ make
cc -Wall -Wextra -g -O2 -o latency-collector latency-collector.c
On 3/15/24 15:53, Arnaldo Carvalho de Melo wrote:
> On Fri, Mar 15, 2024 at 03:48:58PM +0100, Daniel Bristot de Oliveira wrote:
>> On 3/15/24 15:24, Daniel Bristot de Oliveira wrote:
>>> Use tools/build/ makefiles to build latency-collector, inheriting
>>> the benefits
On Fri, Mar 15, 2024 at 03:48:58PM +0100, Daniel Bristot de Oliveira wrote:
> On 3/15/24 15:24, Daniel Bristot de Oliveira wrote:
> > Use tools/build/ makefiles to build latency-collector, inheriting
> > the benefits of it. For example: Before this patch, a missing
> > tracef
On 3/15/24 15:24, Daniel Bristot de Oliveira wrote:
> Use tools/build/ makefiles to build latency-collector, inheriting
> the benefits of it. For example: Before this patch, a missing
> tracefs/traceevents headers will result in fail
Use tools/build/ makefiles to build latency-collector, inheriting
the benefits of it. For example: Before this patch, a missing
tracefs/traceevents headers will result in fail like this:
%< ---
~/linux/tools/tracing/latency $ make
Use tools/build/ makefiles to build latency-collector, inheriting
the benefits of it. For example, having a proper way to
handle dependencies.
Inspired on perf and objtool.
Suggested-by: Linus Torvalds
Signed-off-by: Daniel Bristot de Oliveira
---
tools/tracing/latency/.gitignore | 1
From: Pratik R. Sampat
The cpuidle latency selftest provides support to systematically extract,
analyse and present IPI and timer based wakeup latencies for each CPU
and each idle state available on the system.
The selftest leverages test_cpuidle_latency module's debugfs interface
to int
default 0xa8001c00 if PPC_BOOK3E_64
+
+config CPUIDLE_LATENCY_SELFTEST
+ tristate "Cpuidle latency selftests"
+ depends on CPU_IDLE
+ help
+ Provides a kernel module that run tests using the IPI and
+ timers to measure cpuidle latency.
+
+ Sa
all/20210430082804.38018-1-psam...@linux.ibm.com/
Userspace selftest:
https://lkml.org/lkml/2020/9/2/356
A kernel module + userspace driver to estimate the wakeup latency
caused by going into stop states. The motivation behind this program is
to find significant deviations behind advertised late
On Tue 19 Jan 11:45 CST 2021, AngeloGioacchino Del Regno wrote:
> In order to fine-tune the frequency scaling from various governors,
> allow to set a maximum transition latency from OPPs, which may be
> different depending on the SoC.
>
Acked-by: Bjorn Andersson
Regards,
Bjorn
From: Zhengjun Xing
In the system with very few file pages, it is easy to reproduce
"nr_isolated_file > nr_inactive_file", then too_many_isolated return true,
shrink_inactive_list enter "msleep(100)", the long latency will happen.
The test case to reproduce it is very si
Hi Ulrich-san,
> From: Ulrich Hecht, Sent: Thursday, April 15, 2021 6:36 PM
>
> Since the transition to hrtimers there is no more need to set a minimum
> RX timeout to work around latency issues.
>
> Signed-off-by: Ulrich Hecht
Thank you for the patch!
Reviewed-by: Yoshih
Since the transition to hrtimers there is no more need to set a minimum
RX timeout to work around latency issues.
Signed-off-by: Ulrich Hecht
---
drivers/tty/serial/sh-sci.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/tty/serial/sh-sci.c b/drivers
t should run on in
>default(quick) mode.
> 2. The source CPU to source CPU interaction in the IPI test will always
> result in a lower latency and cause a bias in the average, hence
>avoid adding the latency to be averaged for same cpu IPIs. The
>latency will still
The cpuidle latency selftest provides support to systematically extract,
analyse and present IPI and timer based wakeup latencies for each CPU
and each idle state available on the system.
The selftest leverages test-cpuidle_latency module's debugfs interface
to interact and extract la
n a lower latency and cause a bias in the average, hence
avoid adding the latency to be averaged for same cpu IPIs. The
latency will still be displayed in the detailed logs.
RFC v3: https://lkml.org/lkml/2021/4/4/31
---
A kernel module + userspace driver to estimate the wakeup latency
caused
--- /dev/null
+++ b/drivers/cpuidle/test-cpuidle_latency.c
@@ -0,0 +1,157 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Module-based API test facility for cpuidle latency using IPIs and timers
+ */
+
+#include
+#include
+#include
+
+/*
+ * IPI based wakeup latencies
+ * Measure time taken
On Fri, Apr 9, 2021 at 12:43 AM Pratik Sampat wrote:
> On 09/04/21 10:53 am, Doug Smythies wrote:
> > I tried V3 on a Intel i5-10600K processor with 6 cores and 12 CPUs.
> > The core to cpu mappings are:
> > core 0 has cpus 0 and 6
> > core 1 has cpus 1 and 7
> > core 2 has cpus 2 and 8
> > core 3
ng the average.
In the verbose mode I'll omit all the threads of CPU0 and in the default
(quick) mode just CPU0's latency can be omitted while computing average.
Thank you,
Pratik
Example, where I used the -v option for all CPUs:
--IPI Latency Test---
--Baseline IPI Latency measureme
low states. Myself, I wouldn't include them in the results.
Example, where I used the -v option for all CPUs:
--IPI Latency Test---
--Baseline IPI Latency measurement: CPU Busy--
SRC_CPU DEST_CPU IPI_Latency(ns)
00 101
01 790
02 609
The cpuidle latency selftest provides support to systematically extract,
analyse and present IPI and timer based wakeup latencies for each CPU
and each idle state available on the system.
The selftest leverages test-cpuidle_latency module's debugfs interface
to interact and extract la
--- /dev/null
+++ b/drivers/cpuidle/test-cpuidle_latency.c
@@ -0,0 +1,157 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Module-based API test facility for cpuidle latency using IPIs and timers
+ */
+
+#include
+#include
+#include
+
+/*
+ * IPI based wakeup latencies
+ * Measure time taken
the system is in a coherent state after the tests have run
4. Correct the return status of a CPU that cannot be off-lined.
RFC v2: https://lkml.org/lkml/2021/4/1/615
---
A kernel module + userspace driver to estimate the wakeup latency
caused by going into stop states. The motivation behind this program
Hello Doug,
Thanks for your review.
On 02/04/21 4:57 am, Doug Smythies wrote:
Hi Pratik,
On Thu, Apr 1, 2021 at 4:45 AM Pratik Rajesh Sampat
wrote:
...
To run this test specifically:
$ make -C tools/testing/selftests TARGETS="cpuidle" run_tests
I have not become any smarter than I was with
Hi Pratik,
On Thu, Apr 1, 2021 at 4:45 AM Pratik Rajesh Sampat
wrote:
>
...
> To run this test specifically:
> $ make -C tools/testing/selftests TARGETS="cpuidle" run_tests
I have not become any smarter than I was with version 1,
and still assumed that the "$" meant regular user.
Please put it
reated differently of if they
are more CPUs that cannot have its idle state properties changed.
RFC v1: https://lkml.org/lkml/2021/3/15/492
---
A kernel module + userspace driver to estimate the wakeup latency
caused by going into stop states. The motivation behind this program is
to find sign
--- /dev/null
+++ b/drivers/cpuidle/test-cpuidle_latency.c
@@ -0,0 +1,157 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Module-based API test facility for cpuidle latency using IPIs and timers
+ */
+
+#include
+#include
+#include
+
+/*
+ * IPI based wakeup latencies
+ * Measure time taken
The cpuidle latency selftest provides support to systematically extract,
analyse and present IPI and timer based wakeup latencies for each CPU
and each idle state available on the system.
The selftest leverages test-cpuidle_latency module's debugfs interface
to interact and extract la
nux/tools/testing/selftests/cpuidle$ cat
cpuidle.log.v3-1
--IPI Latency Test---
--Baseline IPI Latency measurement: CPU Busy--
SRC_CPU DEST_CPU IPI_Latency(ns)
00 140
01 632
02 675
03 671
04
r tasks scheduled from time to time on an otherwise idle core.
> In the full per-CPU logs at tools/testing/selftests/cpuidle/cpuidle.log can
> you
> spot any obvious outliers per-CPU state?
Yes.
I'll just paste in an example cpuidle.log file having used the -v option
below, along
From: Xu Wang
Fix semicolon.cocci warning:
tools/tracing/latency/latency-collector.c:1021:2-3: Unneeded semicolon
Link: https://lkml.kernel.org/r/20210308022459.59881-1-vu...@iscas.ac.cn
Reviewed-by: Viktor Rosendahl
Signed-off-by: Xu Wang
Signed-off-by: Steven Rostedt (VMware)
---
tools
e which runs for all the
threads of each CPU with the following: "sudo ./cpuidle.sh -v". While latency
mostly matters for per-core basis but it still maybe a good idea to see if
that changes anything with the observations.
--
Thanks and regards,
Pratik
My system is very idle:
Example (f
Hi Pratik,
It just so happens that I have been trying Artem's version this last
week, so I tried yours.
On Mon, Mar 15, 2021 at 4:49 AM Pratik Rajesh Sampat
wrote:
>
...
> To run this test specifically:
> $ make -C tools/testing/selftests TARGETS="cpuidle" run_tests
While I suppose it should ha
A kernel module + userspace driver to estimate the wakeup latency
caused by going into stop states. The motivation behind this program is
to find significant deviations behind advertised latency and residency
values.
The patchset measures latencies for two kinds of events. IPIs and Timers
As this
--- /dev/null
+++ b/drivers/cpuidle/test-cpuidle_latency.c
@@ -0,0 +1,157 @@
+// SPDX-License-Identifier: GPL-2.0-or-later
+/*
+ * Module-based API test facility for cpuidle latency using IPIs and timers
+ */
+
+#include
+#include
+#include
+
+/*
+ * IPI based wakeup latencies
+ * Measure time taken
The cpuidle latency selftest provides support to systematically extract,
analyse and present IPI and timer based wakeup latencies for each CPU
and each idle state available on the system.
The selftest leverages test-cpuidle_latency module's debugfs interface
to interact and extract la
me is recorded in struct page as scan
time.
- When the page is accessed, hint page fault will occur. The scan
time is gotten from the struct page. And The hint page fault
latency is defined as
hint page fault time - scan time
The shorter the hint page fault latency of a page is, the highe
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: fsl_sai: Add pm qos cpu latency support
commit: 6d85d770c171972c0f33f74b84bf0fedc111e89f
All being well this means that it will be integrated into the linux-next
tree (usually som
From: Alex Deucher
commit 910f1601addae3e430fc7d3cd589d7622c5df693 upstream.
This reverts commit 4a3dea8932d3b1199680d2056dd91d31d94d70b7.
This causes blank screens for some users.
Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1388
Cc: Alvin Lee
Cc: Jun Lei
Cc: Rodrigo Siqueira
Revie
From: Alex Deucher
commit 910f1601addae3e430fc7d3cd589d7622c5df693 upstream.
This reverts commit 4a3dea8932d3b1199680d2056dd91d31d94d70b7.
This causes blank screens for some users.
Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1388
Cc: Alvin Lee
Cc: Jun Lei
Cc: Rodrigo Siqueira
Revie
Hi Steve,
I am not sure what is the correct approach to handle this latency-collector
fix. Can you take it into your queue?
best regards,
Viktor
Colin Ian King (1):
tracing/tools: fix a couple of spelling mistakes
tools/tracing/latency/latency-collector.c | 6 +++---
1 file changed, 3
On Thu, 25 Feb 2021 17:52:47 +0100
Viktor Rosendahl wrote:
> Hi Steve,
>
> I am not sure what is the correct approach to handle this latency-collector
> fix. Can you take it into your queue?
Yes I can take it. I was going to just pull this in for the next merge
window as it'
On SoCs such as i.MX7ULP, cpuidle has some levels which
may disable system/bus clocks, so need to add pm_qos to
prevent cpuidle from entering low level idles and make sure
system/bus clocks are enabled when sai is active.
Signed-off-by: Shengjiu Wang
---
sound/soc/fsl/fsl_sai.c | 12
test campaign every time a latency
problem has been fixed.
It uses inotify to detect changes to /sys/kernel/tracing/trace.
When a latency is detected, it will either sleep or print
immediately, depending on a function that act as an unfair coin
toss.
If immediate print is chosen, it means that we
From: Alex Deucher
commit cf050f96e0970a557601953ed7269d07a7885078 upstream.
This reverts commit 4a3dea8932d3b1199680d2056dd91d31d94d70b7.
This causes blank screens for some users.
Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1482
Cc: Alvin Lee
Cc: Jun Lei
Cc: Rodrigo Siqueira
Revie
On Mon, 15 Feb 2021 11:54:08 +
wrote:
> Just a quick update: I was able to reproduce this weird behavior that I wrote
> about but it turned out to be a problem with my testing.
>
> The test was faulty because of a mistake that I had made.
>
> Sorry for the extra noise.
No problem. Thanks f
On Fri, 2021-02-12 at 13:16 +0100, Viktor Rosendahl wrote:
>
>
> However, for some reason I cannot reproduce the behavior now, allthough I use
> exactly the same kernel.
>
> Because humans are more often at fault than computers, I cannot deny the
> possibility that I would have misconfigured som
Changes since v11
* I added a .gitignore in the tools/tracing/latency directory.
Changes since v10
* Using libtracefs to control ftrace and find /sys/kernel/tracing
* New options to list available tracers, select the tracer and other
ftrace parameters
* A signal handler to restore the
ime a latency
problem has been fixed.
It uses inotify to detect changes to /sys/kernel/tracing/trace.
When a latency is detected, it will either sleep or print
immediately, depending on a function that act as an unfair coin
toss.
If immediate print is chosen, it means that we open
/sys/kernel/tr
guess
> > this
> > is likely to be another regression in the preemptirqsoff tracer.
>
> Not sure what you mean by the above. I'd be interested in fixing it if is
> really a problem.
Sorry, my bad; I should have been more specific.
Yesterday, when I tested the latency-collec
ime a latency
problem has been fixed.
It uses inotify to detect changes to /sys/kernel/tracing/trace.
When a latency is detected, it will either sleep or print
immediately, depending on a function that act as an unfair coin
toss.
If immediate print is chosen, it means that we open
/sys/kernel/tr
gt; +# SPDX-License-Identifier: GPL-2.0
> +# Makefile for vm tools
> +#
> +VAR_CFLAGS := $(shell pkg-config --cflags libtracefs 2>/dev/null)
> +VAR_LDLIBS := $(shell pkg-config --libs libtracefs 2>/dev/null)
> +
> +TARGETS = latency-collector
> +CFLAGS = -Wall -W
e the finding of
> tracefs files. It can also make it easier for you to enable a tracer.
>
I also changed the latency-collector to enable the tracer. I added a few
options for chosing the tracer and for setting up the relevant ftrace
parameters.
I also added a signal handler, so that the
o work with the latency tracers.
The above mentioned commit dit not only change the behavior but also added
an option to emulate the old behavior. The idea with this patch is to
enable this pause-on-trace option when the latency tracers are used.
Link: https://lkml.kernel.org/r/2021011
On 2/6/2021 3:09 AM, Namhyung Kim wrote:
On Fri, Feb 5, 2021 at 11:38 PM Liang, Kan wrote:
On 2/5/2021 6:08 AM, Namhyung Kim wrote:
On Wed, Feb 3, 2021 at 5:14 AM wrote:
From: Kan Liang
The instruction latency information can be recorded on some platforms,
e.g., the Intel Sapphire
> On 05-Feb-2021, at 8:21 PM, Liang, Kan wrote:
>
>
>
> On 2/5/2021 7:55 AM, Athira Rajeev wrote:
>>>> Because in other archs, the var2_w of ‘perf_sample_weight’ could be used
>>>> to capture something else than the Local INSTR Latency.
>>>
On Fri, Feb 5, 2021 at 11:38 PM Liang, Kan wrote:
>
> On 2/5/2021 6:08 AM, Namhyung Kim wrote:
> > On Wed, Feb 3, 2021 at 5:14 AM wrote:
> >>
> >> From: Kan Liang
> >>
> >> The instruction latency information can be recorded on some platforms,
&
> On 04-Feb-2021, at 8:49 PM, Liang, Kan wrote:
>
>
>
> On 2/4/2021 8:11 AM, Athira Rajeev wrote:
>>> On 03-Feb-2021, at 1:39 AM, kan.li...@linux.intel.com wrote:
>>>
>>> From: Kan Liang
>>>
>>> The instruction latency inform
On 2/5/2021 7:55 AM, Athira Rajeev wrote:
Because in other archs, the var2_w of ‘perf_sample_weight’ could be used to
capture something else than the Local INSTR Latency.
Can we have some weak function to populate the header string ?
I agree that the var2_w has different meanings among
On 2/5/2021 6:08 AM, Namhyung Kim wrote:
On Wed, Feb 3, 2021 at 5:14 AM wrote:
From: Kan Liang
The instruction latency information can be recorded on some platforms,
e.g., the Intel Sapphire Rapids server. With both memory latency
(weight) and the new instruction latency information
On Wed, Feb 3, 2021 at 5:14 AM wrote:
>
> From: Kan Liang
>
> The instruction latency information can be recorded on some platforms,
> e.g., the Intel Sapphire Rapids server. With both memory latency
> (weight) and the new instruction latency information, users can easily
>
On 2/4/2021 8:11 AM, Athira Rajeev wrote:
On 03-Feb-2021, at 1:39 AM, kan.li...@linux.intel.com wrote:
From: Kan Liang
The instruction latency information can be recorded on some platforms,
e.g., the Intel Sapphire Rapids server. With both memory latency
(weight) and the new instruction
> On 03-Feb-2021, at 1:39 AM, kan.li...@linux.intel.com wrote:
>
> From: Kan Liang
>
> The instruction latency information can be recorded on some platforms,
> e.g., the Intel Sapphire Rapids server. With both memory latency
> (weight) and the new instruction latency i
me is recorded in struct page as scan
time.
- When the page is accessed, hint page fault will occur. The scan
time is gotten from the struct page. And The hint page fault
latency is defined as
hint page fault time - scan time
The shorter the hint page fault latency of a page is, the highe
Em Tue, Feb 02, 2021 at 12:09:10PM -0800, kan.li...@linux.intel.com escreveu:
> From: Kan Liang
>
> The instruction latency information can be recorded on some platforms,
> e.g., the Intel Sapphire Rapids server. With both memory latency
> (weight) and the new instruction late
From: Viktor Rosendahl
Eaerlier, tracing was disabled when reading the trace file. This behavior
was changed with:
commit 06e0a548bad0 ("tracing: Do not disable tracing when reading the
trace file").
This doesn't seem to work with the latency tracers.
The above mentioned comm
From: Kan Liang
The instruction latency information can be recorded on some platforms,
e.g., the Intel Sapphire Rapids server. With both memory latency
(weight) and the new instruction latency information, users can easily
locate the expensive load instructions, and also understand the time
-License-Identifier: GPL-2.0
> +# Makefile for vm tools
> +#
> +TARGETS = latency-collector
> +CFLAGS = -Wall -Wextra -g -O2
> +LDFLAGS = -lpthread
> +
> +all: $(TARGETS)
> +
> +%: %.c
> + $(CC) $(CFLAGS) -o $@ $< $(LDFLAGS)
> +
> +clean:
> + $(RM)
quot;).
>
> This doesn't seem to work with the latency tracers.
>
> The above mentioned commit dit not only change the behavior but also added
> an option to emulate the old behavior. The idea with this patch is to
> enable this pause-on-trace option when the latency tracers
In order to fine-tune the frequency scaling from various governors,
allow to set a maximum transition latency from OPPs, which may be
different depending on the SoC.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/cpufreq/qcom-cpufreq-hw.c | 7 +++
1 file changed, 7 insertions
From: Kan Liang
The instruction latency information can be recorded on some platforms,
e.g., the Intel Sapphire Rapids server. With both memory latency
(weight) and the new instruction latency information, users can easily
locate the expensive load instructions, and also understand the time
In order to fine-tune the frequency scaling from various governors,
allow to set a maximum transition latency from OPPs, which may be
different depending on the SoC.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/cpufreq/qcom-cpufreq-hw.c | 7 +++
1 file changed, 7 insertions
Eaerlier, tracing was disabled when reading the trace file. This behavior
was changed with:
commit 06e0a548bad0 ("tracing: Do not disable tracing when reading the
trace file").
This doesn't seem to work with the latency tracers.
The above mentioned commit dit not only change t
ime a latency
problem has been fixed.
It uses inotify to detect changes to /sys/kernel/debug/tracing/trace.
When a latency is detected, it will either sleep or print
immediately, depending on a function that act as an unfair coin
toss.
If immediate print is chosen, it means that we open
/sys/kernel/
From: Jiang Biao
Many 100us+ latencies have been deteceted in vmstat_shepherd()
on CPX platform which has 208 logic cpus. And vmstat_shepherd is
queued every second, which could make the case worse.
Add schedule point in vmstat_shepherd() to erase the latency.
Signed-off-by: Jiang Biao
gt; > > > > > [ 5] 7.00-8.00 sec 110 MBytes 923 Mbits/sec 32628
> > > > > > KBytes
> > > > > > [ 5] 8.00-9.00 sec 110 MBytes 923 Mbits/sec 81537
> > > > > > KBytes
> > > > > > [ 5]
t; > > > [ 5] 9.00-10.00 sec 110 MBytes 923 Mbits/sec 10577
> > > > > KBytes
> > > > > - - - - - - - - - - - - - - - - - - - - - - - - -
> > > > > [ ID] Interval Transfer Bitrate Retr
> > > &
c 1056
> > > > sender
> > > > [ 5] 0.00-10.00 sec 1.07 GBytes 923 Mbits/sec
> > > > receiver
> > > >
> > > > But this only confirms that the fix i experience is a side effect.
> > > >
>
uld
> > add this and a dmesg log to the buzilla? It seems like other people
> > should be seeing the same problem, so I'm hoping to grub around on the
> > web to see if there are similar reports involving these devices.
>
> ASUS Pro WS X570-ACE with AMD Ryzen 9
x i experience is a side effect.
> >
> > The original code is still wrong :)
>
> What exactly is this machine? Brand, model, config? Maybe you could
> add this and a dmesg log to the buzilla? It seems like other people
> should be seeing the same problem, so I'm hoping to
ou could
add this and a dmesg log to the buzilla? It seems like other people
should be seeing the same problem, so I'm hoping to grub around on the
web to see if there are similar reports involving these devices.
https://bugzilla.kernel.org/show_bug.cgi?id=209725
Here's one that is s
e:
> > > > > > On Sun, Dec 13, 2020 at 12:47 AM Bjorn Helgaas
> > > > > > wrote:
> > > > > > > On Sat, Oct 24, 2020 at 10:55:46PM +0200, Ian Kumlien wrote:
> > > > > > > > Make pcie_aspm_check_latency comply with the PCIe
, Ian Kumlien wrote:
> > > > > > > Make pcie_aspm_check_latency comply with the PCIe spec,
> > > > > > > specifically:
> > > > > > > "5.4.1.2.2. Exit from the L1 State"
> > > > > > >
> > > > >
0 at 12:47 AM Bjorn Helgaas
> > > > wrote:
> > > > > On Sat, Oct 24, 2020 at 10:55:46PM +0200, Ian Kumlien wrote:
> > > > > > Make pcie_aspm_check_latency comply with the PCIe spec,
> > > > > > specifically:
> > >
_latency comply with the PCIe spec, specifically:
> > > > > "5.4.1.2.2. Exit from the L1 State"
> > > > >
> > > > > Which makes it clear that each switch is required to
> > > > > initiate a transition within 1μs from re
Bjorn Helgaas wrote:
> > > On Sat, Oct 24, 2020 at 10:55:46PM +0200, Ian Kumlien wrote:
> > > > Make pcie_aspm_check_latency comply with the PCIe spec, specifically:
> > > > "5.4.1.2.2. Exit from the L1 State"
> > > >
> > > > Which mak
mply with the PCIe spec, specifically:
> > > "5.4.1.2.2. Exit from the L1 State"
> > >
> > > Which makes it clear that each switch is required to initiate a
> > > transition within 1μs from receiving it, accumulating this latency and
> > > then we h
On Wed, Nov 11, 2020 at 11:59:05PM +0800, Frankie Chang wrote:
> On Wed, 2020-11-11 at 16:12 +0100, Greg Kroah-Hartman wrote:
> > On Wed, Nov 11, 2020 at 11:03:06PM +0800, Frankie Chang wrote:
> > > On Wed, 2020-11-11 at 08:34 +0100, Greg Kroah-Hartman wrote:
> > > > > - The reason why printing the
On Wed, 2020-11-11 at 16:12 +0100, Greg Kroah-Hartman wrote:
> On Wed, Nov 11, 2020 at 11:03:06PM +0800, Frankie Chang wrote:
> > On Wed, 2020-11-11 at 08:34 +0100, Greg Kroah-Hartman wrote:
> > > > - The reason why printing the related information to
> > > > kernel information log but not trace
On Wed, Nov 11, 2020 at 11:03:06PM +0800, Frankie Chang wrote:
> On Wed, 2020-11-11 at 08:34 +0100, Greg Kroah-Hartman wrote:
> > > - The reason why printing the related information to
> > > kernel information log but not trace buffer is that
> > > some abnormal transactions may be pending for
of custom registration functions.
Change from v2:
- create transaction latency module to monitor slow transaction.
Change from v1:
- first patchset.
Frankie.Chang (3):
binder: move structs from core file to header file
binder: add trace at free transaction.
binder: add transaction late
On Wed, Nov 11, 2020 at 11:02:44AM +0800, Frankie Chang wrote:
> From: "Frankie.Chang"
>
> Record start/end timestamp for binder transaction.
> When transaction is completed or transaction is free,
> it would be checked if transaction latency over threshold
> (defa
On Wed, Nov 11, 2020 at 11:02:41AM +0800, Frankie Chang wrote:
>
> Frankie.Chang (3):
> binder: move structs from core file to header file
> binder: add trace at free transaction.
> binder: add transaction latency tracer
>
> drivers/android/Kconfig
Frankie.Chang (3):
binder: move structs from core file to header file
binder: add trace at free transaction.
binder: add transaction latency tracer
drivers/android/Kconfig | 8 +
drivers/android/Makefile| 1 +
drivers/android/binder.c
ead of custom registration functions.
Change from v2:
- create transaction latency module to monitor slow transaction.
Change from v1:
- first patchset.
Frankie.Chang (3):
binder: move structs from core file to header file
binder: add trace at free transaction.
binder: add transact
1 - 100 of 1675 matches
Mail list logo
