Re: [Xen-devel] [RFC 01/16] xen/arm: Re-enable interrupt later in the trap path

2019-07-30 Thread Julien Grall
(+ Andre) On 7/30/19 6:34 PM, Andrii Anisov wrote: Hello Julien, It looks I missed answering this email. So do this now: On 29.11.18 00:00, Julien Grall wrote: On 28/11/2018 21:31, Andrii Anisov wrote: From: Julien Grall This makes function enter_hypervisor_head() being executed with irqs

Re: [Xen-devel] [RFC 01/16] xen/arm: Re-enable interrupt later in the trap path

2019-07-30 Thread Andrii Anisov
Hello Julien, It looks I missed answering this email. So do this now: On 29.11.18 00:00, Julien Grall wrote: On 28/11/2018 21:31, Andrii Anisov wrote: From: Julien Grall This makes function enter_hypervisor_head() being executed with irqs locked. This also give a fine side effect - it

Re: [Xen-devel] [RFC 01/16] xen/arm: Re-enable interrupt later in the trap path

2018-11-28 Thread Julien Grall
On 28/11/2018 21:31, Andrii Anisov wrote: > From: Julien Grall > > This makes function enter_hypervisor_head() being executed with > irqs locked. This also give a fine side effect - it assures that > LRs are cleared prior to any IRQs processing, which leads to a > better (faster) IRQs

[Xen-devel] [RFC 01/16] xen/arm: Re-enable interrupt later in the trap path

2018-11-28 Thread Andrii Anisov
From: Julien Grall This makes function enter_hypervisor_head() being executed with irqs locked. This also give a fine side effect - it assures that LRs are cleared prior to any IRQs processing, which leads to a better (faster) IRQs processing. Signed-off-by: Julien Grall [Andrii: add a