On 08.07.2025 20:07, Alejandro Vallejo wrote:
> --- a/xen/include/xen/bootfdt.h
> +++ b/xen/include/xen/bootfdt.h
> @@ -107,6 +107,10 @@ struct boot_domain {
> struct boot_module *initrd;
>
> const char *cmdline;
> +
> +#if __has_include(<asm/bootfdt.h>)
> + struct arch_boot_domain arch;
> +#endif
> };
I fear I still don't follow this. In patch 1 you made domU a common-but-not-
x86 field. Why can't domid, which is entirely generic, not similarly be a
common-but-only-x86-for-now field? What is put in arch-specific structures
should, in the common case at least, be truly (i.e. conceptually) be arch-
specific imo.
Jan
