On Mon, Jan 20, 2014 at 05:05:14PM +, Jean Pihet wrote:
> Hi Will,
>
> Here is an updated version of the change, which uses compat_sp at only
> one place.
> The drawback is that compat_user_mode is checked when calling
> compat_user_stack_pointer, which seems unnecessary. Unfortunately the
>
On Mon, Jan 20, 2014 at 05:05:14PM +, Jean Pihet wrote:
Hi Will,
Here is an updated version of the change, which uses compat_sp at only
one place.
The drawback is that compat_user_mode is checked when calling
compat_user_stack_pointer, which seems unnecessary. Unfortunately the
check
Hi Will,
Here is an updated version of the change, which uses compat_sp at only
one place.
The drawback is that compat_user_mode is checked when calling
compat_user_stack_pointer, which seems unnecessary. Unfortunately the
check is not optimized out by the complier as I could check with
objdump
Hi Will,
Here is an updated version of the change, which uses compat_sp at only
one place.
The drawback is that compat_user_mode is checked when calling
compat_user_stack_pointer, which seems unnecessary. Unfortunately the
check is not optimized out by the complier as I could check with
objdump
On Fri, Jan 17, 2014 at 09:00:09AM +, Jean Pihet wrote:
> On 16 January 2014 14:47, Jean Pihet wrote:
> >> So the simplest thing would be to make compat_user_stack_pointer expand to
> >> user_stack_pointer(current_pt_regs()) on arm64 and merge that in with your
> >> original patch fixing
Hi Will,
Some more thoughts below
On 16 January 2014 14:47, Jean Pihet wrote:
> Will,
>
> On 16 January 2014 13:57, Will Deacon wrote:
>> On Thu, Jan 16, 2014 at 12:26:53PM +, Jean Pihet wrote:
>>> On 16 January 2014 12:56, Will Deacon wrote:
>>> > In your previous series, compat
Hi Will,
Some more thoughts below
On 16 January 2014 14:47, Jean Pihet jean.pi...@linaro.org wrote:
Will,
On 16 January 2014 13:57, Will Deacon will.dea...@arm.com wrote:
On Thu, Jan 16, 2014 at 12:26:53PM +, Jean Pihet wrote:
On 16 January 2014 12:56, Will Deacon will.dea...@arm.com
On Fri, Jan 17, 2014 at 09:00:09AM +, Jean Pihet wrote:
On 16 January 2014 14:47, Jean Pihet jean.pi...@linaro.org wrote:
So the simplest thing would be to make compat_user_stack_pointer expand to
user_stack_pointer(current_pt_regs()) on arm64 and merge that in with your
original patch
Will,
On 16 January 2014 13:57, Will Deacon wrote:
> On Thu, Jan 16, 2014 at 12:26:53PM +, Jean Pihet wrote:
>> On 16 January 2014 12:56, Will Deacon wrote:
>> > In your previous series, compat backtracing is actually split out into a
>> > separate function (compat_user_backtrace), so it
On Thu, Jan 16, 2014 at 12:26:53PM +, Jean Pihet wrote:
> On 16 January 2014 12:56, Will Deacon wrote:
> > In your previous series, compat backtracing is actually split out into a
> > separate function (compat_user_backtrace), so it would be more consistent to
> > have a
On 16 January 2014 12:56, Will Deacon wrote:
> Hi Jean,
>
> On Thu, Jan 16, 2014 at 10:45:23AM +, Jean Pihet wrote:
>> Add support for unwinding using the dwarf information in compat
>> mode. Using the correct user stack pointer allows perf to record
>> the frames correctly in the native and
Hi Jean,
On Thu, Jan 16, 2014 at 10:45:23AM +, Jean Pihet wrote:
> Add support for unwinding using the dwarf information in compat
> mode. Using the correct user stack pointer allows perf to record
> the frames correctly in the native and compat modes.
>
> Note that although the dwarf frame
Add support for unwinding using the dwarf information in compat
mode. Using the correct user stack pointer allows perf to record
the frames correctly in the native and compat modes.
Note that although the dwarf frame unwinding works ok using
libunwind in native mode (on ARMv7 & ARMv8), some
Add support for unwinding using the dwarf information in compat
mode. Using the correct user stack pointer allows perf to record
the frames correctly in the native and compat modes.
Note that although the dwarf frame unwinding works ok using
libunwind in native mode (on ARMv7 ARMv8), some
Hi Jean,
On Thu, Jan 16, 2014 at 10:45:23AM +, Jean Pihet wrote:
Add support for unwinding using the dwarf information in compat
mode. Using the correct user stack pointer allows perf to record
the frames correctly in the native and compat modes.
Note that although the dwarf frame
On 16 January 2014 12:56, Will Deacon will.dea...@arm.com wrote:
Hi Jean,
On Thu, Jan 16, 2014 at 10:45:23AM +, Jean Pihet wrote:
Add support for unwinding using the dwarf information in compat
mode. Using the correct user stack pointer allows perf to record
the frames correctly in the
On Thu, Jan 16, 2014 at 12:26:53PM +, Jean Pihet wrote:
On 16 January 2014 12:56, Will Deacon will.dea...@arm.com wrote:
In your previous series, compat backtracing is actually split out into a
separate function (compat_user_backtrace), so it would be more consistent to
have a
Will,
On 16 January 2014 13:57, Will Deacon will.dea...@arm.com wrote:
On Thu, Jan 16, 2014 at 12:26:53PM +, Jean Pihet wrote:
On 16 January 2014 12:56, Will Deacon will.dea...@arm.com wrote:
In your previous series, compat backtracing is actually split out into a
separate function
18 matches
Mail list logo
