[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: Andrii Anisov <andrii.anisov@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
From: Julien Grall <julien.grall@xxxxxxx>
Date: Fri, 26 Jul 2019 11:48:57 +0100
Cc: Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Andrii Anisov <andrii_anisov@xxxxxxxx>
Delivery-date: Fri, 26 Jul 2019 10:49:07 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Hi,

On 26/07/2019 11:37, Andrii Anisov wrote:

From: Julien Grall <julien.grall@xxxxxxx>

This makes function enter_hypervisor_head() being executed with
irqs locked.

This is the 3rd time you send this patch... and still no proper explanation whythis is done nor the impact on keeping the interrupts disabled longer thannecessary.

Resending the patch without things addressed is only going to make it worst. Ifyou have any doubt of what I am asking then ask.


Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

Follow-Ups:
- Re: [Xen-devel] [RFC 1/6] xen/arm: Re-enable interrupt later in the trap path
  - From: Andrii Anisov

References:
- [Xen-devel] [RFC 0/6] XEN scheduling hardening
  - From: Andrii Anisov
- [Xen-devel] [RFC 1/6] xen/arm: Re-enable interrupt later in the trap path
  - From: Andrii Anisov

Prev by Date: Re: [Xen-devel] [RFC 5/6] arm64: сall enter_hypervisor_head only when it is needed
Next by Date: [Xen-devel] [ovmf test] 139357: all pass - PUSHED
Previous by thread: [Xen-devel] [RFC 1/6] xen/arm: Re-enable interrupt later in the trap path
Next by thread: Re: [Xen-devel] [RFC 1/6] xen/arm: Re-enable interrupt later in the trap path
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.