Argh, fix your mailer. That is unreadable.
/me reflows...
Sorry about that. Now I reconfigure the mail editor by applying "Preformat" and
"Fixed Width" settings in thunderbird client. Wish it to be better.
See, that's so much better..
Oh, so you _ARE_ adding a kernel feature? I
Argh, fix your mailer. That is unreadable.
/me reflows...
Sorry about that. Now I reconfigure the mail editor by applying "Preformat" and
"Fixed Width" settings in thunderbird client. Wish it to be better.
See, that's so much better..
Oh, so you _ARE_ adding a kernel feature? I
On Thu, Apr 06, 2017 at 10:43:19PM +0800, Jin, Yao wrote:
>
>
> On 4/6/2017 5:25 PM, Peter Zijlstra wrote:
> > On Thu, Apr 06, 2017 at 04:21:06PM +0800, Jin, Yao wrote:
> > > Hi, otherwise we have to maintain 2 branch type copies between kernel and
> > > user-space.
> > >
> > > For example,
On Thu, Apr 06, 2017 at 10:43:19PM +0800, Jin, Yao wrote:
>
>
> On 4/6/2017 5:25 PM, Peter Zijlstra wrote:
> > On Thu, Apr 06, 2017 at 04:21:06PM +0800, Jin, Yao wrote:
> > > Hi, otherwise we have to maintain 2 branch type copies between kernel and
> > > user-space.
> > >
> > > For example,
On 4/6/2017 5:25 PM, Peter Zijlstra wrote:
On Thu, Apr 06, 2017 at 04:21:06PM +0800, Jin, Yao wrote:
Hi, otherwise we have to maintain 2 branch type copies between kernel and
user-space.
For example, currently X86_BR_* are defined in lbr.c. To display the branch
type in user-space, the
On 4/6/2017 5:25 PM, Peter Zijlstra wrote:
On Thu, Apr 06, 2017 at 04:21:06PM +0800, Jin, Yao wrote:
Hi, otherwise we have to maintain 2 branch type copies between kernel and
user-space.
For example, currently X86_BR_* are defined in lbr.c. To display the branch
type in user-space, the
On Thu, Apr 06, 2017 at 04:21:06PM +0800, Jin, Yao wrote:
> Hi, otherwise we have to maintain 2 branch type copies between kernel and
> user-space.
>
> For example, currently X86_BR_* are defined in lbr.c. To display the branch
> type in user-space, the user-space has to maintain the same copy
On Thu, Apr 06, 2017 at 04:21:06PM +0800, Jin, Yao wrote:
> Hi, otherwise we have to maintain 2 branch type copies between kernel and
> user-space.
>
> For example, currently X86_BR_* are defined in lbr.c. To display the branch
> type in user-space, the user-space has to maintain the same copy
On 4/6/2017 2:58 PM, Peter Zijlstra wrote:
On Tue, Apr 04, 2017 at 11:18:05AM -0300, Arnaldo Carvalho de Melo wrote:
Adding the perf kernel maintainers to the CC list.
Thanks.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
It is often useful to know the branch types while
On 4/6/2017 2:58 PM, Peter Zijlstra wrote:
On Tue, Apr 04, 2017 at 11:18:05AM -0300, Arnaldo Carvalho de Melo wrote:
Adding the perf kernel maintainers to the CC list.
Thanks.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
It is often useful to know the branch types while
On Tue, Apr 04, 2017 at 11:18:05AM -0300, Arnaldo Carvalho de Melo wrote:
> Adding the perf kernel maintainers to the CC list.
Thanks.
> Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
> > It is often useful to know the branch types while analyzing branch
> > data. For example, a
On Tue, Apr 04, 2017 at 11:18:05AM -0300, Arnaldo Carvalho de Melo wrote:
> Adding the perf kernel maintainers to the CC list.
Thanks.
> Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
> > It is often useful to know the branch types while analyzing branch
> > data. For example, a
On 4/5/2017 12:09 AM, Arnaldo Carvalho de Melo wrote:
Em Tue, Apr 04, 2017 at 11:52:53PM +0800, Jin, Yao escreveu:
On 4/4/2017 10:18 PM, Arnaldo Carvalho de Melo wrote:
Adding the perf kernel maintainers to the CC list.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
It is
On 4/5/2017 12:09 AM, Arnaldo Carvalho de Melo wrote:
Em Tue, Apr 04, 2017 at 11:52:53PM +0800, Jin, Yao escreveu:
On 4/4/2017 10:18 PM, Arnaldo Carvalho de Melo wrote:
Adding the perf kernel maintainers to the CC list.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
It is
Em Tue, Apr 04, 2017 at 11:52:53PM +0800, Jin, Yao escreveu:
>
>
> On 4/4/2017 10:18 PM, Arnaldo Carvalho de Melo wrote:
> > Adding the perf kernel maintainers to the CC list.
> >
> > Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
> > > It is often useful to know the branch types
Em Tue, Apr 04, 2017 at 11:52:53PM +0800, Jin, Yao escreveu:
>
>
> On 4/4/2017 10:18 PM, Arnaldo Carvalho de Melo wrote:
> > Adding the perf kernel maintainers to the CC list.
> >
> > Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
> > > It is often useful to know the branch types
On 4/4/2017 10:18 PM, Arnaldo Carvalho de Melo wrote:
Adding the perf kernel maintainers to the CC list.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
It is often useful to know the branch types while analyzing branch
data. For example, a call is very different from a
On 4/4/2017 10:18 PM, Arnaldo Carvalho de Melo wrote:
Adding the perf kernel maintainers to the CC list.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
It is often useful to know the branch types while analyzing branch
data. For example, a call is very different from a
Adding the perf kernel maintainers to the CC list.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
> It is often useful to know the branch types while analyzing branch
> data. For example, a call is very different from a conditional branch.
>
> Currently we have to look it up in
Adding the perf kernel maintainers to the CC list.
Em Fri, Mar 31, 2017 at 11:18:38PM +0800, Jin Yao escreveu:
> It is often useful to know the branch types while analyzing branch
> data. For example, a call is very different from a conditional branch.
>
> Currently we have to look it up in
It is often useful to know the branch types while analyzing branch
data. For example, a call is very different from a conditional branch.
Currently we have to look it up in binary while the binary may later
not be available and even the binary is available but user has to take
some time. It is
It is often useful to know the branch types while analyzing branch
data. For example, a call is very different from a conditional branch.
Currently we have to look it up in binary while the binary may later
not be available and even the binary is available but user has to take
some time. It is
22 matches
Mail list logo
