On Tue, Dec 10, 2013 at 05:22:29PM +0100, Oleg Nesterov wrote:
> On 12/10, Frederic Weisbecker wrote:
> >
> > On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpa...@amd.com
> > wrote:
> > > @@ -525,14 +525,11 @@ int parse_events_add_breakpoint(struct list_head
> > > *list, int *idx,
> >
On 12/10, Frederic Weisbecker wrote:
>
> On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpa...@amd.com wrote:
> > @@ -525,14 +525,11 @@ int parse_events_add_breakpoint(struct list_head
> > *list, int *idx,
> > if (parse_breakpoint_type(type, ))
> > return -EINVAL;
> >
>
On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpa...@amd.com wrote:
> From: Jacob Shin
>
> Currently bp_len is given a default value of 4. Allow user to override it:
>
> $ perf stat -e mem:0x1000/8
> ^
> bp_len
>
> If no
On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpa...@amd.com wrote:
From: Jacob Shin jacob.w.s...@gmail.com
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
On 12/10, Frederic Weisbecker wrote:
On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpa...@amd.com wrote:
@@ -525,14 +525,11 @@ int parse_events_add_breakpoint(struct list_head
*list, int *idx,
if (parse_breakpoint_type(type, attr))
return -EINVAL;
- /*
On Tue, Dec 10, 2013 at 05:22:29PM +0100, Oleg Nesterov wrote:
On 12/10, Frederic Weisbecker wrote:
On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpa...@amd.com
wrote:
@@ -525,14 +525,11 @@ int parse_events_add_breakpoint(struct list_head
*list, int *idx,
if
From: Jacob Shin
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
If no value is given, it will default to 4 as it did before.
Signed-off-by: Jacob Shin
Signed-off-by:
From: Jacob Shin jacob.w.s...@gmail.com
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
If no value is given, it will default to 4 as it did before.
Signed-off-by: Jacob
On 04/27, H. Peter Anvin wrote:
>
> On 04/27/2013 09:58 AM, Oleg Nesterov wrote:
> >
> > Stupid question... So X86_FEATURE_BPEXT only works for r/w? I mean, it
> > doesn't allow to specify the mask for an execute breakpoint?
>
> x86 execute breakpoints in general are only a single byte, which has
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
If no value is given, it will default to 4 as it did before.
Signed-off-by: Jacob Shin
---
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
If no value is given, it will default to 4 as it did before.
Signed-off-by: Jacob Shin jacob.s...@amd.com
---
On 04/27, H. Peter Anvin wrote:
On 04/27/2013 09:58 AM, Oleg Nesterov wrote:
Stupid question... So X86_FEATURE_BPEXT only works for r/w? I mean, it
doesn't allow to specify the mask for an execute breakpoint?
x86 execute breakpoints in general are only a single byte, which has to
be the
On 04/27/2013 09:58 AM, Oleg Nesterov wrote:
>
> Stupid question... So X86_FEATURE_BPEXT only works for r/w? I mean, it
> doesn't allow to specify the mask for an execute breakpoint?
>
x86 execute breakpoints in general are only a single byte, which has to
be the first byte of the instruction.
On Sat, Apr 27, 2013 at 07:34:24PM +0200, Oleg Nesterov wrote:
> On 04/27, Oleg Nesterov wrote:
> >
> > On 04/26, Jacob Shin wrote:
> > >
> > > @@ -518,12 +518,10 @@ int parse_events_add_breakpoint(struct list_head
> > > **list, int *idx,
> > > if (parse_breakpoint_type(type, ))
> > >
On 04/27, Oleg Nesterov wrote:
>
> On 04/26, Jacob Shin wrote:
> >
> > @@ -518,12 +518,10 @@ int parse_events_add_breakpoint(struct list_head
> > **list, int *idx,
> > if (parse_breakpoint_type(type, ))
> > return -EINVAL;
> >
> > - /*
> > -* We should find a nice way to
On 04/26, Jacob Shin wrote:
>
> @@ -518,12 +518,10 @@ int parse_events_add_breakpoint(struct list_head
> **list, int *idx,
> if (parse_breakpoint_type(type, ))
> return -EINVAL;
>
> - /*
> - * We should find a nice way to override the access length
> - * Provide
On 04/26, Jacob Shin wrote:
@@ -518,12 +518,10 @@ int parse_events_add_breakpoint(struct list_head
**list, int *idx,
if (parse_breakpoint_type(type, attr))
return -EINVAL;
- /*
- * We should find a nice way to override the access length
- * Provide some
On 04/27, Oleg Nesterov wrote:
On 04/26, Jacob Shin wrote:
@@ -518,12 +518,10 @@ int parse_events_add_breakpoint(struct list_head
**list, int *idx,
if (parse_breakpoint_type(type, attr))
return -EINVAL;
- /*
-* We should find a nice way to override the
On Sat, Apr 27, 2013 at 07:34:24PM +0200, Oleg Nesterov wrote:
On 04/27, Oleg Nesterov wrote:
On 04/26, Jacob Shin wrote:
@@ -518,12 +518,10 @@ int parse_events_add_breakpoint(struct list_head
**list, int *idx,
if (parse_breakpoint_type(type, attr))
return -EINVAL;
On 04/27/2013 09:58 AM, Oleg Nesterov wrote:
Stupid question... So X86_FEATURE_BPEXT only works for r/w? I mean, it
doesn't allow to specify the mask for an execute breakpoint?
x86 execute breakpoints in general are only a single byte, which has to
be the first byte of the instruction.
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
If no value is given, it will default to 4 as it did before.
Signed-off-by: Jacob Shin
---
Currently bp_len is given a default value of 4. Allow user to override it:
$ perf stat -e mem:0x1000/8
^
bp_len
If no value is given, it will default to 4 as it did before.
Signed-off-by: Jacob Shin jacob.s...@amd.com
---
22 matches
Mail list logo
