We currently have an asymmetric setup where CONFIG_VERBOSE_DEBUG controls
extra diagnostics for a PV dom0, and opt_dom0_verbose controls extra
diagnostics for a PVH dom0.
Default opt_dom0_verbose to CONFIG_VERBOSE_DEBUG and use opt_dom0_verbose
consistently.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
guests do no require any paging support by default.
* The `verbose` boolean is intended for diagnostics, and prints out extra
- information during the dom0 build. It defaults to false.
+ information during the dom0 build. It defaults to the compile time choice
+ of `CONFIG_VERBOSE_DEBUG`.
### dom0-iommu
= List of [ passthrough=<bool>, strict=<bool>, map-inclusive=<bool>,
bool __initdata opt_dom0_shadow;
#endif
bool __initdata opt_dom0_pvh = !IS_ENABLED(CONFIG_PV);
-bool __initdata opt_dom0_verbose;
+bool __initdata opt_dom0_verbose = IS_ENABLED(CONFIG_VERBOSE_DEBUG);
static int __init parse_dom0_param(const char *s)
{
if ( (rc = elf_init(&elf, image_start, image_len)) != 0 )
return rc;
-#ifdef CONFIG_VERBOSE_DEBUG
- elf_set_verbose(&elf);
-#endif
+
+ if ( opt_dom0_verbose )
+ elf_set_verbose(&elf);
+
elf_parse_binary(&elf);
if ( (rc = elf_xen_parse(&elf, &parms)) != 0 )
goto out;