OpenBSD cvs log

created 2020-07-31T12:08:20Z
begin 2020-07-17T07:58:46Z
end 2020-07-17T08:07:34Z
path src/sys
commits 2

date 2020-07-17T08:07:33Z
author patrick
files src/sys/arch/arm64/arm64/acpi_machdep.c log diff annotate
src/sys/arch/arm64/arm64/intr.c log diff annotate
src/sys/arch/arm64/dev/acpipci.c log diff annotate
src/sys/arch/arm64/dev/agintc.c log diff annotate
src/sys/arch/arm64/dev/ampintc.c log diff annotate
src/sys/arch/arm64/include/intr.h log diff annotate
message Re-work intr_barrier(9) on arm64 to remove layer violation. So far we
have stored the struct cpu_info * in the wrapper around the interrupt
handler cookie, but since we can have a few layers inbetween, this does
not seem very nice. Instead have each and every interrupt controller
provide a barrier function. This means that intr_barrier(9) will in the
end be executed by the interrupt controller that actually wired the pin
to a core. And that's the only place where the information is stored.

ok kettenis@

date 2020-07-17T08:07:34Z
author patrick
files src/sys/arch/armv7/include/intr.h log diff annotate
src/sys/dev/fdt/bcm2835_aux.c log diff annotate
src/sys/dev/fdt/imxgpc.c log diff annotate
src/sys/dev/fdt/imxgpio.c log diff annotate
src/sys/dev/fdt/mvgicp.c log diff annotate
src/sys/dev/fdt/mvicu.c log diff annotate
src/sys/dev/fdt/mvkpcie.c log diff annotate
src/sys/dev/fdt/rkgpio.c log diff annotate
message Re-work intr_barrier(9) on arm64 to remove layer violation. So far we
have stored the struct cpu_info * in the wrapper around the interrupt
handler cookie, but since we can have a few layers inbetween, this does
not seem very nice. Instead have each and every interrupt controller
provide a barrier function. This means that intr_barrier(9) will in the
end be executed by the interrupt controller that actually wired the pin
to a core. And that's the only place where the information is stored.

ok kettenis@