All of lore.kernel.org
 help / color / mirror / Atom feed
From: xiakaixu <xiakaixu@huawei.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	paulus@samba.org, Ingo Molnar <mingo@kernel.org>,
	a.p.zijlstra@chello.nl,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Borislav Petkov <bp@alien8.de>,
	Namhyung Kim <namhyung@kernel.org>,
	Huxinwei <huxinwei@huawei.com>,
	peifeiyue@huawei.com
Subject: Re: Does perf support different length of user-space hw_breakpoint?
Date: Wed, 14 May 2014 10:55:09 +0800	[thread overview]
Message-ID: <5372DB0D.5070206@huawei.com> (raw)
In-Reply-To: <20140513150613.GC13828@localhost.localdomain>

于 2014/5/13 23:06, Frederic Weisbecker 写道:
> On Tue, May 13, 2014 at 02:00:46PM +0200, Jiri Olsa wrote:
>> On Mon, May 12, 2014 at 03:52:54PM +0800, xiakaixu wrote:
>>> Hi guys,
>>>
>>> Does perf support different length of user-space hw_breakpoint,
>>> such as  HW_BREAKPOINT_LEN_1/HW_BREAKPOINT_LEN_2/HW_BREAKPOINT_LEN_4/
>>> HW_BREAKPOINT_LEN_8?
>>>
>>> Seems perf only support HW_BREAKPOINT_LEN_4/sizeof(long)
>>> by default from the source code and simple test.
>>
>> right..
>>
>>         /*
>>          * We should find a nice way to override the access length
>>          * Provide some defaults for now
>>          */
>>         if (attr.bp_type == HW_BREAKPOINT_X)
>>                 attr.bp_len = sizeof(long);
>>         else
>>                 attr.bp_len = HW_BREAKPOINT_LEN_4;
>>
>>>
>>> May I have your opinions if I want to trace different bytes of
>>> hw_breakpoint addr?
>>
>> I guess that depends on what you want to do ;-)
> 
> Ah, I have a patchset from Jacob Shin and Suravee Suthikulpanit that does
> that. Also it has been hanging around for too long by my fault. I'm posting
> it now.

Thanks for your reply!
Hopefully I can get it ASAP.
> .
> 

WARNING: multiple messages have this Message-ID (diff)
From: xiakaixu <xiakaixu@huawei.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-perf-users@vger.kernel.org>, <paulus@samba.org>,
	Ingo Molnar <mingo@kernel.org>, <a.p.zijlstra@chello.nl>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Borislav Petkov <bp@alien8.de>,
	Namhyung Kim <namhyung@kernel.org>,
	Huxinwei <huxinwei@huawei.com>, <peifeiyue@huawei.com>
Subject: Re: Does perf support different length of user-space hw_breakpoint?
Date: Wed, 14 May 2014 10:55:09 +0800	[thread overview]
Message-ID: <5372DB0D.5070206@huawei.com> (raw)
In-Reply-To: <20140513150613.GC13828@localhost.localdomain>

于 2014/5/13 23:06, Frederic Weisbecker 写道:
> On Tue, May 13, 2014 at 02:00:46PM +0200, Jiri Olsa wrote:
>> On Mon, May 12, 2014 at 03:52:54PM +0800, xiakaixu wrote:
>>> Hi guys,
>>>
>>> Does perf support different length of user-space hw_breakpoint,
>>> such as  HW_BREAKPOINT_LEN_1/HW_BREAKPOINT_LEN_2/HW_BREAKPOINT_LEN_4/
>>> HW_BREAKPOINT_LEN_8?
>>>
>>> Seems perf only support HW_BREAKPOINT_LEN_4/sizeof(long)
>>> by default from the source code and simple test.
>>
>> right..
>>
>>         /*
>>          * We should find a nice way to override the access length
>>          * Provide some defaults for now
>>          */
>>         if (attr.bp_type == HW_BREAKPOINT_X)
>>                 attr.bp_len = sizeof(long);
>>         else
>>                 attr.bp_len = HW_BREAKPOINT_LEN_4;
>>
>>>
>>> May I have your opinions if I want to trace different bytes of
>>> hw_breakpoint addr?
>>
>> I guess that depends on what you want to do ;-)
> 
> Ah, I have a patchset from Jacob Shin and Suravee Suthikulpanit that does
> that. Also it has been hanging around for too long by my fault. I'm posting
> it now.

Thanks for your reply!
Hopefully I can get it ASAP.
> .
> 



  reply	other threads:[~2014-05-14  2:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  7:52 Does perf support different length of user-space hw_breakpoint? xiakaixu
2014-05-12  7:52 ` xiakaixu
2014-05-12  8:05 ` Peter Zijlstra
     [not found]   ` <CAGjdHukwC3cu3YOSSteXsC4_52m-YTdAAYCfXV+q5A2pnW+CKQ@mail.gmail.com>
2014-05-12  8:48     ` Peter Zijlstra
2014-05-12  9:00       ` xiakaixu
2014-05-12  9:00         ` xiakaixu
2014-05-13 11:38         ` xiakaixu
2014-05-13 11:38           ` xiakaixu
2014-05-13 12:00 ` Jiri Olsa
2014-05-13 15:06   ` Frederic Weisbecker
2014-05-14  2:55     ` xiakaixu [this message]
2014-05-14  2:55       ` xiakaixu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5372DB0D.5070206@huawei.com \
    --to=xiakaixu@huawei.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=bp@alien8.de \
    --cc=fweisbec@gmail.com \
    --cc=huxinwei@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    --cc=peifeiyue@huawei.com \
    --cc=suravee.suthikulpanit@amd.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.