Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: f91c57158100fa0b4586a3271dc2c27570d56be7
https://github.com/siemens/jailhouse/commit/f91c57158100fa0b4586a3271dc2c27570d56be7
Author: Jan Kiszka <[email protected]>
Date: 2020-03-06 (Fri, 06 Mar 2020)
Changed paths:
M hypervisor/arch/arm-common/control.c
M hypervisor/arch/arm-common/include/asm/control.h
M hypervisor/arch/arm-common/psci.c
M hypervisor/arch/x86/include/asm/control.h
M hypervisor/include/jailhouse/control.h
Log Message:
-----------
arm-common: Get rid of arm_cpu_kick
Implement arch_send_event directly and switch psci to this. Makes things
more straightforward - and provides the chance to properly document
arch_send_event.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 19cf7a61caaa793bb533d38b531519e703cccf49
https://github.com/siemens/jailhouse/commit/19cf7a61caaa793bb533d38b531519e703cccf49
Author: Jan Kiszka <[email protected]>
Date: 2020-03-06 (Fri, 06 Mar 2020)
Changed paths:
M hypervisor/arch/arm-common/psci.c
M hypervisor/control.c
M hypervisor/include/jailhouse/control.h
Log Message:
-----------
core, arm-common: Clarify role of spin_unlock before event submission
On ARM, the spin_unlock is sufficient to provide a memory barrier before
calling arch_send_event. On other archs, the implementation of
arch_send_event has to take care of this. Clarify this at the respective
call sites and the function documentation.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: d2becb4a22a7dc85cb237014796862a50f4cfc6d
https://github.com/siemens/jailhouse/commit/d2becb4a22a7dc85cb237014796862a50f4cfc6d
Author: Jan Kiszka <[email protected]>
Date: 2020-03-06 (Fri, 06 Mar 2020)
Changed paths:
M hypervisor/arch/arm-common/include/asm/irqchip.h
M hypervisor/arch/arm-common/irqchip.c
M hypervisor/arch/arm-common/ivshmem.c
Log Message:
-----------
arm-common: Factor out irqchip_trigger_external_irq
This replaces the non-intuitive special case of
irqchip_set_pending(NULL, ...) with an explicit one.
The only case where irqchip_set_pending() was called like this was
arch_ivshmem_trigger_interrupt(). All others already passed in a
cpu_public pointer guaranteed to be non-NULL.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 368ff6b2acb3f24ec5903db328d73f2c9d986601
https://github.com/siemens/jailhouse/commit/368ff6b2acb3f24ec5903db328d73f2c9d986601
Author: Jan Kiszka <[email protected]>
Date: 2020-03-06 (Fri, 06 Mar 2020)
Changed paths:
M Documentation/ivshmem-v2-specification.md
Log Message:
-----------
Documentation: ivshmem: Require that doorbell writes act as memory barriers
This avoids that the guest has to be aware of how the doorbell interrupt
is internally sent to the target CPU because to add the corresponding
memory barrier explicitly. The implementation in Jailhouse already
fulfills this new requirement.
Signed-off-by: Jan Kiszka <[email protected]>
Compare:
https://github.com/siemens/jailhouse/compare/266ebe6decbf...368ff6b2acb3
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/siemens/jailhouse/push/refs/heads/next/266ebe-368ff6%40github.com.
