Em Wed, Mar 22, 2017 at 08:00:18AM +0900, Masami Hiramatsu escreveu:
> On Tue, 21 Mar 2017 11:10:49 -0300
> Arnaldo Carvalho de Melo wrote:
>
> > Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu:
> > > Thanks Masami for the review.
> > >
> > > On Tuesday 07
Em Wed, Mar 22, 2017 at 08:00:18AM +0900, Masami Hiramatsu escreveu:
> On Tue, 21 Mar 2017 11:10:49 -0300
> Arnaldo Carvalho de Melo wrote:
>
> > Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu:
> > > Thanks Masami for the review.
> > >
> > > On Tuesday 07 February 2017 08:41
On Tue, 21 Mar 2017 11:10:49 -0300
Arnaldo Carvalho de Melo wrote:
> Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu:
> > Thanks Masami for the review.
> >
> > On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote:
> > > On Thu, 2 Feb 2017 16:41:41
On Tue, 21 Mar 2017 11:10:49 -0300
Arnaldo Carvalho de Melo wrote:
> Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu:
> > Thanks Masami for the review.
> >
> > On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote:
> > > On Thu, 2 Feb 2017 16:41:41 +0530
> > > Ravi
On Thu, 2 Feb 2017 16:41:41 +0530
Ravi Bangoria wrote:
> SDT marker argument is in N@OP format. N is the size of argument and
> OP is the actual assembly operand. OP is arch dependent component and
> hence it's parsing logic also should be placed under
On Thu, 2 Feb 2017 16:41:41 +0530
Ravi Bangoria wrote:
> SDT marker argument is in N@OP format. N is the size of argument and
> OP is the actual assembly operand. OP is arch dependent component and
> hence it's parsing logic also should be placed under tools/perf/arch/.
>
> Signed-off-by: Ravi
Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu:
> Thanks Masami for the review.
>
> On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote:
> > On Thu, 2 Feb 2017 16:41:41 +0530
> > Ravi Bangoria wrote:
> >
> >> SDT marker argument is in
Em Tue, Feb 07, 2017 at 10:52:17AM +0530, Ravi Bangoria escreveu:
> Thanks Masami for the review.
>
> On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote:
> > On Thu, 2 Feb 2017 16:41:41 +0530
> > Ravi Bangoria wrote:
> >
> >> SDT marker argument is in N@OP format. N is the size of
Thanks Masami for the review.
On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote:
> On Thu, 2 Feb 2017 16:41:41 +0530
> Ravi Bangoria wrote:
>
>> SDT marker argument is in N@OP format. N is the size of argument and
>> OP is the actual assembly
Thanks Masami for the review.
On Tuesday 07 February 2017 08:41 AM, Masami Hiramatsu wrote:
> On Thu, 2 Feb 2017 16:41:41 +0530
> Ravi Bangoria wrote:
>
>> SDT marker argument is in N@OP format. N is the size of argument and
>> OP is the actual assembly operand. OP is arch dependent component
On Thu, 2 Feb 2017 16:41:41 +0530
Ravi Bangoria wrote:
> SDT marker argument is in N@OP format. N is the size of argument and
> OP is the actual assembly operand. OP is arch dependent component and
> hence it's parsing logic also should be placed under
On Thu, 2 Feb 2017 16:41:41 +0530
Ravi Bangoria wrote:
> SDT marker argument is in N@OP format. N is the size of argument and
> OP is the actual assembly operand. OP is arch dependent component and
> hence it's parsing logic also should be placed under tools/perf/arch/.
>
Ok, I have one
SDT marker argument is in N@OP format. N is the size of argument and
OP is the actual assembly operand. OP is arch dependent component and
hence it's parsing logic also should be placed under tools/perf/arch/.
Signed-off-by: Ravi Bangoria
---
SDT marker argument is in N@OP format. N is the size of argument and
OP is the actual assembly operand. OP is arch dependent component and
hence it's parsing logic also should be placed under tools/perf/arch/.
Signed-off-by: Ravi Bangoria
---
tools/perf/arch/x86/util/perf_regs.c | 93
14 matches
Mail list logo