Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-24 Thread Baicar, Tyler
On 1/23/2017 3:01 AM, James Morse wrote: Hi Tyler, On 20/01/17 20:35, Baicar, Tyler wrote: On 1/19/2017 10:55 AM, James Morse wrote: On 18/01/17 23:26, Baicar, Tyler wrote: On 1/17/2017 3:31 AM, James Morse wrote: On 12/01/17 18:15, Tyler Baicar wrote: +info.si_addr = (void __user

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-24 Thread Baicar, Tyler
On 1/23/2017 3:01 AM, James Morse wrote: Hi Tyler, On 20/01/17 20:35, Baicar, Tyler wrote: On 1/19/2017 10:55 AM, James Morse wrote: On 18/01/17 23:26, Baicar, Tyler wrote: On 1/17/2017 3:31 AM, James Morse wrote: On 12/01/17 18:15, Tyler Baicar wrote: +info.si_addr = (void __user

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-23 Thread James Morse
Hi Tyler, On 20/01/17 20:35, Baicar, Tyler wrote: > On 1/19/2017 10:55 AM, James Morse wrote: >> On 18/01/17 23:26, Baicar, Tyler wrote: >>> On 1/17/2017 3:31 AM, James Morse wrote: On 12/01/17 18:15, Tyler Baicar wrote: > +info.si_addr = (void __user *)addr; addr here was read

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-23 Thread James Morse
Hi Tyler, On 20/01/17 20:35, Baicar, Tyler wrote: > On 1/19/2017 10:55 AM, James Morse wrote: >> On 18/01/17 23:26, Baicar, Tyler wrote: >>> On 1/17/2017 3:31 AM, James Morse wrote: On 12/01/17 18:15, Tyler Baicar wrote: > +info.si_addr = (void __user *)addr; addr here was read

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-20 Thread Baicar, Tyler
On 1/19/2017 10:55 AM, James Morse wrote: Hi Tyler, On 18/01/17 23:26, Baicar, Tyler wrote: On 1/17/2017 3:31 AM, James Morse wrote: On 12/01/17 18:15, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-20 Thread Baicar, Tyler
On 1/19/2017 10:55 AM, James Morse wrote: Hi Tyler, On 18/01/17 23:26, Baicar, Tyler wrote: On 1/17/2017 3:31 AM, James Morse wrote: On 12/01/17 18:15, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-19 Thread James Morse
Hi Tyler, On 18/01/17 23:26, Baicar, Tyler wrote: > On 1/17/2017 3:31 AM, James Morse wrote: >> On 12/01/17 18:15, Tyler Baicar wrote: >>> SEA exceptions are often caused by an uncorrected hardware >>> error, and are handled when data abort and instruction abort >>> exception classes have

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-19 Thread James Morse
Hi Tyler, On 18/01/17 23:26, Baicar, Tyler wrote: > On 1/17/2017 3:31 AM, James Morse wrote: >> On 12/01/17 18:15, Tyler Baicar wrote: >>> SEA exceptions are often caused by an uncorrected hardware >>> error, and are handled when data abort and instruction abort >>> exception classes have

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-18 Thread Baicar, Tyler
Hello James, On 1/17/2017 3:31 AM, James Morse wrote: Hi Tyler, On 12/01/17 18:15, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault Status Code.

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-18 Thread Baicar, Tyler
Hello James, On 1/17/2017 3:31 AM, James Morse wrote: Hi Tyler, On 12/01/17 18:15, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault Status Code.

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-18 Thread Baicar, Tyler
On 1/17/2017 3:27 AM, Will Deacon wrote: On Mon, Jan 16, 2017 at 01:09:22PM -0700, Baicar, Tyler wrote: On 1/16/2017 4:53 AM, Will Deacon wrote: On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-18 Thread Baicar, Tyler
On 1/17/2017 3:27 AM, Will Deacon wrote: On Mon, Jan 16, 2017 at 01:09:22PM -0700, Baicar, Tyler wrote: On 1/16/2017 4:53 AM, Will Deacon wrote: On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-18 Thread Baicar, Tyler
On 1/17/2017 3:23 AM, James Morse wrote: Hi Tyler, On 16/01/17 11:53, Will Deacon wrote: On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-18 Thread Baicar, Tyler
On 1/17/2017 3:23 AM, James Morse wrote: Hi Tyler, On 16/01/17 11:53, Will Deacon wrote: On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-17 Thread James Morse
Hi Tyler, On 12/01/17 18:15, Tyler Baicar wrote: > SEA exceptions are often caused by an uncorrected hardware > error, and are handled when data abort and instruction abort > exception classes have specific values for their Fault Status > Code. > When SEA occurs, before killing the process, go

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-17 Thread James Morse
Hi Tyler, On 12/01/17 18:15, Tyler Baicar wrote: > SEA exceptions are often caused by an uncorrected hardware > error, and are handled when data abort and instruction abort > exception classes have specific values for their Fault Status > Code. > When SEA occurs, before killing the process, go

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-17 Thread Will Deacon
On Mon, Jan 16, 2017 at 01:09:22PM -0700, Baicar, Tyler wrote: > On 1/16/2017 4:53 AM, Will Deacon wrote: > >On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: > >>SEA exceptions are often caused by an uncorrected hardware > >>error, and are handled when data abort and instruction abort

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-17 Thread Will Deacon
On Mon, Jan 16, 2017 at 01:09:22PM -0700, Baicar, Tyler wrote: > On 1/16/2017 4:53 AM, Will Deacon wrote: > >On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: > >>SEA exceptions are often caused by an uncorrected hardware > >>error, and are handled when data abort and instruction abort

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-17 Thread James Morse
Hi Tyler, On 16/01/17 11:53, Will Deacon wrote: > On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: >> SEA exceptions are often caused by an uncorrected hardware >> error, and are handled when data abort and instruction abort >> exception classes have specific values for their Fault

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-17 Thread James Morse
Hi Tyler, On 16/01/17 11:53, Will Deacon wrote: > On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: >> SEA exceptions are often caused by an uncorrected hardware >> error, and are handled when data abort and instruction abort >> exception classes have specific values for their Fault

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-16 Thread Baicar, Tyler
Hello Will, On 1/16/2017 4:53 AM, Will Deacon wrote: On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-16 Thread Baicar, Tyler
Hello Will, On 1/16/2017 4:53 AM, Will Deacon wrote: On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-16 Thread Will Deacon
On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: > SEA exceptions are often caused by an uncorrected hardware > error, and are handled when data abort and instruction abort > exception classes have specific values for their Fault Status > Code. > When SEA occurs, before killing the

Re: [PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-16 Thread Will Deacon
On Thu, Jan 12, 2017 at 11:15:18AM -0700, Tyler Baicar wrote: > SEA exceptions are often caused by an uncorrected hardware > error, and are handled when data abort and instruction abort > exception classes have specific values for their Fault Status > Code. > When SEA occurs, before killing the

[PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-12 Thread Tyler Baicar
SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault Status Code. When SEA occurs, before killing the process, go through the handlers registered in the notification list.

[PATCH V7 04/10] arm64: exception: handle Synchronous External Abort

2017-01-12 Thread Tyler Baicar
SEA exceptions are often caused by an uncorrected hardware error, and are handled when data abort and instruction abort exception classes have specific values for their Fault Status Code. When SEA occurs, before killing the process, go through the handlers registered in the notification list.