Change Details

The structure hypervisor_info and associated source, introduced in cfa0b7b82fbdda56d7160569def5c6133eb045aa, is needed on all Xen architectures and should not be in the x86 area. As ARM (likely RISC-V) only has the PVv2/PVH version, leave the PVv1 version as x86-only. While the mechanism for setting xen_domain_type/HYPERVISOR_shared_info may differ, the presence of the variables will not. All architectures need these.

The xen_domain_type and HYPERVISOR_shared_info variables are shared by all Xen architectures, so they should be in common rather than reimplemented by each architecture. Likewise with the setup of HYPERVISOR_shared_info. The implementation of xen_handle_shared_info() was inspired by one from elsewhere which also meets the need for Xen/ARM.

The structure hypervisor_infoxen_domain_type and associated source, introduced in cfa0b7b82fbdda56d7160569def5c6133eb045aaHYPERVISOR_shared_info variables are shared by all Xen architectures, is needed on all Xen architectures and should not be in the x86 area. As ARM (likely RISC-V) only has the PVv2/PVH version, leave the PVv1 version as x86-onlyso they should be in common rather than reimplemented by each architecture. While the mechanism for setting xen_domain_type/HYPERVISOR_shared_info may differ, the presence of the variables will not. All architectures need theseLikewise with the setup of HYPERVISOR_shared_info. The implementation of xen_handle_shared_info() was inspired by one from elsewhere which also meets the need for Xen/ARM.