Re: [PATCH v9 11/26] efi: Let architectures decide the flags that should be saved/restored

2019-01-28 Thread Marc Zyngier
On Mon, 21 Jan 2019 15:33:30 +, Julien Thierry wrote: > > Currently, irqflags are saved before calling runtime services and > checked for mismatch on return. > > Provide a pair of overridable macros to save and restore (if needed) the > state that need to be preserved on return from a

Re: [PATCH v9 11/26] efi: Let architectures decide the flags that should be saved/restored

2019-01-23 Thread Julien Thierry
On 21/01/2019 15:42, Ard Biesheuvel wrote: > On Mon, 21 Jan 2019 at 16:34, Julien Thierry wrote: >> >> Currently, irqflags are saved before calling runtime services and >> checked for mismatch on return. >> >> Provide a pair of overridable macros to save and restore (if needed) the >> state

Re: [PATCH v9 11/26] efi: Let architectures decide the flags that should be saved/restored

2019-01-21 Thread Ard Biesheuvel
On Mon, 21 Jan 2019 at 16:34, Julien Thierry wrote: > > Currently, irqflags are saved before calling runtime services and > checked for mismatch on return. > > Provide a pair of overridable macros to save and restore (if needed) the > state that need to be preserved on return from a runtime

[PATCH v9 11/26] efi: Let architectures decide the flags that should be saved/restored

2019-01-21 Thread Julien Thierry
Currently, irqflags are saved before calling runtime services and checked for mismatch on return. Provide a pair of overridable macros to save and restore (if needed) the state that need to be preserved on return from a runtime service. This allows to check for flags that are not necesarly