Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Ley Foon Tan
On Thu, Jan 22, 2015 at 5:07 PM, Chung-Lin Tang wrote: > On 2015/1/22 下午 04:43, Ley Foon Tan wrote: >> On Thu, Jan 22, 2015 at 4:15 PM, Chung-Lin Tang >> wrote: >>> On 2015/1/22 03:54 PM, Ley Foon Tan wrote: On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang wrote: > The address of

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Chung-Lin Tang
On 2015/1/22 下午 04:43, Ley Foon Tan wrote: > On Thu, Jan 22, 2015 at 4:15 PM, Chung-Lin Tang > wrote: >> On 2015/1/22 03:54 PM, Ley Foon Tan wrote: >>> On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang >>> wrote: The address of __kuser_sigtramp is wrong by one word, due to padding

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Ley Foon Tan
On Thu, Jan 22, 2015 at 4:15 PM, Chung-Lin Tang wrote: > On 2015/1/22 03:54 PM, Ley Foon Tan wrote: >> On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang >> wrote: >>> The address of __kuser_sigtramp is wrong by one word, due to padding >>> __kuser_cmpxchg to fully 64 bytes. The version word at

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Chung-Lin Tang
On 2015/1/22 03:54 PM, Ley Foon Tan wrote: > On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang > wrote: >> The address of __kuser_sigtramp is wrong by one word, due to padding >> __kuser_cmpxchg to fully 64 bytes. The version word at the start of the >> page displaces __kuser_sigtramp to 0x1044,

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Chung-Lin Tang
On 2015/1/22 03:54 PM, Ley Foon Tan wrote: On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang chunglin.t...@gmail.com wrote: The address of __kuser_sigtramp is wrong by one word, due to padding __kuser_cmpxchg to fully 64 bytes. The version word at the start of the page displaces

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Ley Foon Tan
On Thu, Jan 22, 2015 at 4:15 PM, Chung-Lin Tang clt...@codesourcery.com wrote: On 2015/1/22 03:54 PM, Ley Foon Tan wrote: On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang chunglin.t...@gmail.com wrote: The address of __kuser_sigtramp is wrong by one word, due to padding __kuser_cmpxchg to

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Chung-Lin Tang
On 2015/1/22 下午 04:43, Ley Foon Tan wrote: On Thu, Jan 22, 2015 at 4:15 PM, Chung-Lin Tang clt...@codesourcery.com wrote: On 2015/1/22 03:54 PM, Ley Foon Tan wrote: On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang chunglin.t...@gmail.com wrote: The address of __kuser_sigtramp is wrong by

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-22 Thread Ley Foon Tan
On Thu, Jan 22, 2015 at 5:07 PM, Chung-Lin Tang clt...@codesourcery.com wrote: On 2015/1/22 下午 04:43, Ley Foon Tan wrote: On Thu, Jan 22, 2015 at 4:15 PM, Chung-Lin Tang clt...@codesourcery.com wrote: On 2015/1/22 03:54 PM, Ley Foon Tan wrote: On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-21 Thread Ley Foon Tan
On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang wrote: > The address of __kuser_sigtramp is wrong by one word, due to padding > __kuser_cmpxchg to fully 64 bytes. The version word at the start of the > page displaces __kuser_sigtramp to 0x1044, instead of the intended 0x1040. > > Fixed by

[PATCH] nios2: __kuser_sigtramp placement fix

2015-01-21 Thread Chung-Lin Tang
The address of __kuser_sigtramp is wrong by one word, due to padding __kuser_cmpxchg to fully 64 bytes. The version word at the start of the page displaces __kuser_sigtramp to 0x1044, instead of the intended 0x1040. Fixed by counting the 64-byte frame from the start of the page instead of

[PATCH] nios2: __kuser_sigtramp placement fix

2015-01-21 Thread Chung-Lin Tang
The address of __kuser_sigtramp is wrong by one word, due to padding __kuser_cmpxchg to fully 64 bytes. The version word at the start of the page displaces __kuser_sigtramp to 0x1044, instead of the intended 0x1040. Fixed by counting the 64-byte frame from the start of the page instead of

Re: [PATCH] nios2: __kuser_sigtramp placement fix

2015-01-21 Thread Ley Foon Tan
On Thu, Jan 22, 2015 at 3:14 PM, Chung-Lin Tang chunglin.t...@gmail.com wrote: The address of __kuser_sigtramp is wrong by one word, due to padding __kuser_cmpxchg to fully 64 bytes. The version word at the start of the page displaces __kuser_sigtramp to 0x1044, instead of the intended 0x1040.