Dom0 (aka hardware domain on Arm) is always direct mapped. Rather than
using a global variable to store a const, directly open-code it or
replace the use with is_domain_direct_mapped(...) macros.
This will also help a follow-up patch to move all domain_build.c in
init.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
static unsigned int __initdata opt_dom0_max_vcpus;
integer_param("dom0_max_vcpus", opt_dom0_max_vcpus);
-int dom0_11_mapping = 1;
-
static u64 __initdata dom0_mem;
static int __init parse_dom0_mem(const char *s)
* TODO: Implement memory bank allocation when DOM0 is not direct
* mapped
*/
- BUG_ON(!dom0_11_mapping);
+ BUG_ON(!is_domain_direct_mapped(d));
printk("Allocating 1:1 mappings totalling %ldMB for dom0:\n",
/* Don't want format this as PRIpaddr (16 digit hex) */
#define is_64bit_domain(d) (0)
#endif
-extern int dom0_11_mapping;
-#define is_domain_direct_mapped(d) ((d) == hardware_domain && dom0_11_mapping)
+/* The hardware domain has always its memory direct mapped. */
+#define is_domain_direct_mapped(d) ((d) == hardware_domain)
struct vtimer {
struct vcpu *v;