Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: c16ed30bd64efc9d7a30745c333de9adc80b4a13
https://github.com/siemens/jailhouse/commit/c16ed30bd64efc9d7a30745c333de9adc80b4a13
Author: Jan Kiszka <[email protected]>
Date: 2019-12-23 (Mon, 23 Dec 2019)
Changed paths:
M hypervisor/arch/arm64/include/asm/spinlock.h
Log Message:
-----------
arm64: Document why spin_lock/unlock have memory barrier semantics
This makes it clearer why we have no explicit memory barrier in the
spin_lock/unlock implementation, in contrast to the ARMv7 version.
Based on research by Peng Fan.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 940e194f3be655cc56929c70b3f7fa61cc89abed
https://github.com/siemens/jailhouse/commit/940e194f3be655cc56929c70b3f7fa61cc89abed
Author: Jan Kiszka <[email protected]>
Date: 2019-12-23 (Mon, 23 Dec 2019)
Changed paths:
M hypervisor/arch/arm-common/irqchip.c
Log Message:
-----------
arm-common: Fix barrier usage in irqchip_set_pending / irqchip_inject_pending
We were missing memory barriers before updating the lockless ring buffer
of pending interrupts, both on producer and consumer side. At the same
time, we can remove a barrier that is already provided implicitly by
spin_unlock on ARM.
Reported-by: Peng Fan <[email protected]>
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 0db943d9a2541f6a4539bd12377c778b1b6024d1
https://github.com/siemens/jailhouse/commit/0db943d9a2541f6a4539bd12377c778b1b6024d1
Author: Jan Kiszka <[email protected]>
Date: 2019-12-23 (Mon, 23 Dec 2019)
Changed paths:
M hypervisor/arch/arm/include/asm/processor.h
M hypervisor/arch/arm64/include/asm/processor.h
Log Message:
-----------
arm/arm64: Populate memory_load_barrier
This abstraction is currently used for mmio region updates. There is no
reason why it could be left empty on ARM. Linux does not do that as
well.
What Linux also does is to map a write barrier on ishst. However,
Jailhouse has no abstraction for write-only barriers, thus cannot use
this mapping for its generic memory_barrier.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: f07ebffc91fdc37ba7760eac353338c759f563e4
https://github.com/siemens/jailhouse/commit/f07ebffc91fdc37ba7760eac353338c759f563e4
Author: Jan Kiszka <[email protected]>
Date: 2019-12-23 (Mon, 23 Dec 2019)
Changed paths:
M hypervisor/arch/arm-common/include/asm/traps.h
R hypervisor/arch/arm/include/arch/asm/traps.h
A hypervisor/arch/arm/include/asm/traps.h
R hypervisor/arch/arm64/include/arch/asm/traps.h
A hypervisor/arch/arm64/include/asm/traps.h
Log Message:
-----------
arm/arm64: Refactor traps.h inclusion
Rather than placing the arch-specific traps.h under at unusual place,
make use of includ_next to pull the common header from the prioritized
arch-specific one.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: 0b095585b1c3511c1fab42b9c7bf4e018f8faeee
https://github.com/siemens/jailhouse/commit/0b095585b1c3511c1fab42b9c7bf4e018f8faeee
Author: Jan Kiszka <[email protected]>
Date: 2019-12-23 (Mon, 23 Dec 2019)
Changed paths:
M hypervisor/arch/arm-common/include/asm/gic.h
M hypervisor/arch/arm-common/include/asm/iommu.h
Log Message:
-----------
arm-common: Fix some stand-alone inclusion issues
Pull required headers to comply with stand-alone inclusion rule.
header_check is about to test the common headers and detected these
issues.
Signed-off-by: Jan Kiszka <[email protected]>
Commit: b5ef548cec668376ca65492dbd2dc03d9e8cc489
https://github.com/siemens/jailhouse/commit/b5ef548cec668376ca65492dbd2dc03d9e8cc489
Author: Jan Kiszka <[email protected]>
Date: 2019-12-23 (Mon, 23 Dec 2019)
Changed paths:
M scripts/header_check
Log Message:
-----------
scripts: Let header_check cover arm-common includes as well
We had a blind spot here. Just make sure we do not test common traps.h
because that one is only supposed to be included via its arch-specific
companion.
Signed-off-by: Jan Kiszka <[email protected]>
Compare:
https://github.com/siemens/jailhouse/compare/cd140c5a6d85...b5ef548cec66
--
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/cd140c-b5ef54%40github.com.
