diff mbox series

libelf: make L1_MFN_VALID note known

Message ID f444ccc1-51be-e526-e8e2-7759a68a743d@suse.com (mailing list archive)
State New, archived
Headers show
Series libelf: make L1_MFN_VALID note known | expand

Commit Message

Jan Beulich May 17, 2023, 2:19 p.m. UTC 
We still don't use it (in the tool stack), and its values (plural) also
aren't fetched correctly, but it is odd to continue to see the
hypervisor log "ELF: note: unknown (0xd)" when loading a Linux Dom0.

Signed-off-by: Jan Beulich <jbeulich@suse.com>

Comments

Julien Grall June 24, 2023, 1:57 p.m. UTC | #1 
Hi Jan,

On 17/05/2023 15:19, Jan Beulich wrote:
> We still don't use it (in the tool stack), and its values (plural) also
> aren't fetched correctly, but it is odd to continue to see the
> hypervisor log "ELF: note: unknown (0xd)" when loading a Linux Dom0.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Julien Grall <jgrall@amazon.com>

Cheers,
diff mbox series

Patch

--- a/xen/common/libelf/libelf-dominfo.c
+++ b/xen/common/libelf/libelf-dominfo.c
@@ -117,6 +117,7 @@  elf_errorstatus elf_xen_parse_note(struc
         [XEN_ELFNOTE_FEATURES] = { "FEATURES", 1},
         [XEN_ELFNOTE_SUPPORTED_FEATURES] = { "SUPPORTED_FEATURES", 0},
         [XEN_ELFNOTE_BSD_SYMTAB] = { "BSD_SYMTAB", 1},
+        [XEN_ELFNOTE_L1_MFN_VALID] = { "L1_MFN_VALID", false },
         [XEN_ELFNOTE_SUSPEND_CANCEL] = { "SUSPEND_CANCEL", 0 },
         [XEN_ELFNOTE_MOD_START_PFN] = { "MOD_START_PFN", 0 },
         [XEN_ELFNOTE_PHYS32_ENTRY] = { "PHYS32_ENTRY", 0 },