On 27 March 2017 at 13:54, Ard Biesheuvel wrote:
> On 22 March 2017 at 13:18, Leif Lindholm wrote:
>> On Mon, Mar 20, 2017 at 08:53:01PM +, Ard Biesheuvel wrote:
>>> In order to be able to produce meaningful diagnostic output when taking
On 22 March 2017 at 13:18, Leif Lindholm wrote:
> On Mon, Mar 20, 2017 at 08:53:01PM +, Ard Biesheuvel wrote:
>> In order to be able to produce meaningful diagnostic output when taking
>> synchronous exceptions that have been caused by corruption of the stack
>>
On 22 March 2017 at 13:18, Leif Lindholm wrote:
> On Mon, Mar 20, 2017 at 08:53:01PM +, Ard Biesheuvel wrote:
>> In order to be able to produce meaningful diagnostic output when taking
>> synchronous exceptions that have been caused by corruption of the stack
>>
On Mon, Mar 20, 2017 at 08:53:01PM +, Ard Biesheuvel wrote:
> In order to be able to produce meaningful diagnostic output when taking
> synchronous exceptions that have been caused by corruption of the stack
> pointer, prepare the EL0 stack pointer and switch to it when handling the
> 'Sync
In order to be able to produce meaningful diagnostic output when taking
synchronous exceptions that have been caused by corruption of the stack
pointer, prepare the EL0 stack pointer and switch to it when handling the
'Sync exception using SPx' exception class. Other exception classes (of
which we
5 matches
Mail list logo