On 3/17/25 4:46 PM, Jan Beulich wrote:
On 11.03.2025 17:19, Oleksii Kurochko wrote:
--- a/xen/arch/riscv/setup.c
+++ b/xen/arch/riscv/setup.c
@@ -16,6 +16,7 @@
#include
#include
#include
+#include
#include
#include
#include
@@ -128,6 +129,8 @@ void __init noreturn start_xen(u
On 11.03.2025 17:19, Oleksii Kurochko wrote:
> --- a/xen/arch/riscv/setup.c
> +++ b/xen/arch/riscv/setup.c
> @@ -16,6 +16,7 @@
> #include
> #include
> #include
> +#include
> #include
> #include
> #include
> @@ -128,6 +129,8 @@ void __init noreturn start_xen(unsigned long bootcpu_id,
>
Currently, only the device tree method is available to locate and perform
pre-initialization steps for the interrupt controller. When `acpi_disabled`
is true, the system will scan for a node with the "interrupt-controller"
property and then call `device_init()` to validate if it is an expected
inte