x86/PV: also check kernel endianness when building Dom0

While big endian x86 images are pretty unlikely to appear, merely
logging endianness isn't of much use.

Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
This commit is contained in:
Jan Beulich committed 2020-08-24 15:38:48 +02:00
1 parent c297c94533
commit 347384331e
1 file changed
+8 -4
+8 -4
View File
@@ -288,7 +288,8 @@ int __init dom0_construct_pv(struct domain *d,
module_t *initrd,
char *cmdline)
{
int i, rc, compatible, order, machine;
int i, rc, order, machine;
bool compatible;
struct cpu_user_regs *regs;
unsigned long pfn, mfn;
unsigned long nr_pages;
@@ -358,7 +359,7 @@ int __init dom0_construct_pv(struct domain *d,
/* compatibility check */
printk(" Xen kernel: 64-bit, lsb%s\n",
IS_ENABLED(CONFIG_PV32) ? ", compat32" : "");
compatible = 0;
compatible = false;
machine = elf_uval(&elf, elf.ehdr, e_machine);
#ifdef CONFIG_PV32
@@ -374,13 +375,16 @@ int __init dom0_construct_pv(struct domain *d,
return rc;
}
compatible = 1;
compatible = true;
}
}
#endif
if ( elf_64bit(&elf) && machine == EM_X86_64 )
compatible = 1;
compatible = true;
if ( elf_msb(&elf) )
compatible = false;
printk(" Dom0 kernel: %s-bit%s, %s, paddr %#" PRIx64 " -> %#" PRIx64 "\n",
elf_64bit(&elf) ? "64" : elf_32bit(&elf) ? "32" : "??",
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.