rding!
Couldn't synthesize bpf events.
[ perf record: Woken up 0 times to write data ]
[ perf record: Captured and wrote 1.824 MB perf.data (67 samples) ]
Terminated
# ls -lh perf.data
-rw--- 1 root root 1.9M Jul 17 14:05 perf.data
Signed-off-by: Jiwei Sun
---
v4 changes:
- Just show o
rding!
Couldn't synthesize bpf events.
[ perf record: Woken up 0 times to write data ]
[ perf record: Captured and wrote 1.824 MB perf.data (67 samples) ]
Terminated
# ls -lh perf.data
-rw--- 1 root root 1.9M Jul 17 14:05 perf.data
Signed-off-by: Jiwei Sun
---
v4 changes:
- Just show o
Hello Arnaldo & Jirka,
Do you have any other suggestions regarding the patch?
Any suggestions are welcome. Thank you very much.
Regards,
Jiwei
On 2019e9409f 25f% 15:06, Jiwei Sun wrote:
> The patch adds a new option to limit the output file size, then based
> on it, we can create
Hi Jirka,
On 2019e9410f 21f% 21:41, Jiri Olsa wrote:
> On Wed, Sep 25, 2019 at 03:06:37PM +0800, Jiwei Sun wrote:
>
> SNIP
>
>> SEE ALSO
>>
>> linkperf:perf-stat[1], linkperf:perf-list[1]
>> diff --git a/tools/perf/builtin-record.c b/
The patch adds a new option to limit the output file size, then based
on it, we can create a wrapper of the perf command that uses the option
to avoid exhausting the disk space by the unconscious user.
Signed-off-by: Jiwei Sun
---
tools/perf/builtin-record.c | 39
When transfer timeout, give -EAGAIN to the message's status, and it can
make the spi device driver choose repeated transimation or not. And if
transfer timeout, output some useful information for tracing the issue.
Signed-off-by: Jiwei Sun
---
drivers/spi/spi-pl022.c
times to write data ]
[ perf record: Captured and wrote 100.104 MB perf.data (2128267 samples) ]
Terminated
# ls -lh perf.data
-rw--- 1 root root 101M Mar 11 14:48 perf.data
Signed-off-by: Jiwei Sun
---
v3 changes:
- add a test result
- add the new option to tools/perf/Document
Hi Jirka,
On 02/21/2019 05:56 PM, Jiri Olsa wrote:
> On Thu, Feb 21, 2019 at 02:44:19PM +0800, Jiwei Sun wrote:
>> The patch adds a new option to limit the output file size, then based
>> on it, we can create a wrapper of the perf command that uses the option
>> to avoid exha
The patch adds a new option to limit the output file size, then based
on it, we can create a wrapper of the perf command that uses the option
to avoid exhausting the disk space by the unconscious user.
Signed-off-by: Jiwei Sun
---
v2 changes:
- make patch based on latest Arnaldo's perf
Hi Arnaldo,
On 02/22/2019 10:53 PM, Arnaldo Carvalho de Melo wrote:
> Em Fri, Feb 22, 2019 at 03:19:04PM +0800, Jiwei Sun escreveu:
>> The patch adds a new option to limit the output file size, then based
>> on it, we can create a wrapper of the perf command that uses the opt
037 msecs
The root cause is as following.
When the hardware clock's time is modified later than the periodic
alarm clock's expire time, the rtc_timer_do_work's loop may spend
a long time to process.
In order to avoid the case, we can adjust the next expire time to
equating to "now
>> is the same as C, if now A is rescheduled on CPU1, A's asid is not able
>>>> to renew according to 'if' clause, and the local TLB entry can't be
>>>> flushed too, A's address space will be the same as C.
>>>>
>>>> I
nd the local TLB entry can't be
flushed too, A's address space will be the same as C.
If asid_cache(cpu) overflows, all of user space task's asid on this CPU
are able to set a invalid value (such as 0), it will avoid the risk.
Signed-off-by: Jiwei Sun
---
arch/mips/include/asm/mmu
13 matches
Mail list logo
