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/tools/perf/builtin-record.c
>> index
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/tools/perf/builtin-record.c
> index 48600c90cc7e..30904d2a3407 100644
> --- a/tools/perf/builtin-record.c
> +++
On Mon, Oct 21, 2019 at 07:51:17PM +0800, Jiwei Sun wrote:
> Hello Arnaldo & Jirka,
>
> Do you have any other suggestions regarding the patch?
> Any suggestions are welcome. Thank you very much.
oops, overlooked this one, sry.. I'll check on it today
jirka
>
> Regards,
> Jiwei
>
> On
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 a wrapper
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.
In order to make the perf.data parsable, we just limit the sample data
size, since the
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.
In order to make the perf.data parsable, we just limit the sample data
size, since the
6 matches
Mail list logo
