[PATCH] score: Add CPU_Exception_frame
Sebastian Huber
sebastian.huber at embedded-brains.de
Mon Nov 26 08:12:42 UTC 2012
On 11/25/2012 10:07 PM, Gedare Bloom wrote:
> Is there a difference between CPU_Interrupt_frame and CPU_Exception_frame?
Yes, there is a difference. The CPU_Exception_frame should contain the
complete processor state. The CPU_Interrupt_frame should contain only the part
necessary for interrupt processing (usually a processor state register, the
return context and the volatile register set). Thus CPU_Interrupt_frame
contains a subset of CPU_Exception_frame.
>
> I think Interrupt_frame has been more commonly used; most of these
> architectures have a CPU_Interrupt_frame defined. Instead of
> defaulting CPU_Exception_frame to an empty struct, maybe we should
> typedef CPU_Exception_frame CPU_Interrupt_frame;
Yes, this is a good idea.
--
Sebastian Huber, embedded brains GmbH
Address : Obere Lagerstr. 30, D-82178 Puchheim, Germany
Phone : +49 89 18 90 80 79-6
Fax : +49 89 18 90 80 79-9
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel
mailing list