linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Lieven Hey <lieven.hey@kdab.com>
Cc: linux-perf-users@vger.kernel.org, Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH v2] perf jit: Include program header in elf files
Date: Tue, 20 Sep 2022 21:10:28 +0100	[thread overview]
Message-ID: <YyoeNGZ8wK8pFUjr@kernel.org> (raw)
In-Reply-To: <20220915092910.711036-1-lieven.hey@kdab.com>

Em Thu, Sep 15, 2022 at 11:29:10AM +0200, Lieven Hey escreveu:
> The missing header makes it hard for programs like elfutils to open
> these files.
> 
> Fixes: 2d86612aacb7805f ("perf symbol: Correct address for bss symbols")
> Signed-off-by: Lieven Hey <lieven.hey@kdab.com>
> Reviewed-by: Leo Yan <leo.yan@linaro.org>
> Tested-by: Leo Yan <leo.yan@linaro.org>

Thanks, applied.

- Arnaldo

> ---
>  tools/perf/util/genelf.c | 14 ++++++++++++++
>  tools/perf/util/genelf.h |  4 ++++
>  2 files changed, 18 insertions(+)
> 
> diff --git a/tools/perf/util/genelf.c b/tools/perf/util/genelf.c
> index 953338b9e887..02cd9f75e3d2 100644
> --- a/tools/perf/util/genelf.c
> +++ b/tools/perf/util/genelf.c
> @@ -251,6 +251,7 @@ jit_write_elf(int fd, uint64_t load_addr, const char *sym,
>  	Elf_Data *d;
>  	Elf_Scn *scn;
>  	Elf_Ehdr *ehdr;
> +	Elf_Phdr *phdr;
>  	Elf_Shdr *shdr;
>  	uint64_t eh_frame_base_offset;
>  	char *strsym = NULL;
> @@ -285,6 +286,19 @@ jit_write_elf(int fd, uint64_t load_addr, const char *sym,
>  	ehdr->e_version = EV_CURRENT;
>  	ehdr->e_shstrndx= unwinding ? 4 : 2; /* shdr index for section name */
>  
> +	/*
> +	 * setup program header
> +	 */
> +	phdr = elf_newphdr(e, 1);
> +	phdr[0].p_type = PT_LOAD;
> +	phdr[0].p_offset = 0;
> +	phdr[0].p_vaddr = 0;
> +	phdr[0].p_paddr = 0;
> +	phdr[0].p_filesz = csize;
> +	phdr[0].p_memsz = csize;
> +	phdr[0].p_flags = PF_X | PF_R;
> +	phdr[0].p_align = 8;
> +
>  	/*
>  	 * setup text section
>  	 */
> diff --git a/tools/perf/util/genelf.h b/tools/perf/util/genelf.h
> index ae138afe6c56..b5c909546e3f 100644
> --- a/tools/perf/util/genelf.h
> +++ b/tools/perf/util/genelf.h
> @@ -53,8 +53,10 @@ int jit_add_debug_info(Elf *e, uint64_t code_addr, void *debug, int nr_debug_ent
>  
>  #if GEN_ELF_CLASS == ELFCLASS64
>  #define elf_newehdr	elf64_newehdr
> +#define elf_newphdr	elf64_newphdr
>  #define elf_getshdr	elf64_getshdr
>  #define Elf_Ehdr	Elf64_Ehdr
> +#define Elf_Phdr	Elf64_Phdr
>  #define Elf_Shdr	Elf64_Shdr
>  #define Elf_Sym		Elf64_Sym
>  #define ELF_ST_TYPE(a)	ELF64_ST_TYPE(a)
> @@ -62,8 +64,10 @@ int jit_add_debug_info(Elf *e, uint64_t code_addr, void *debug, int nr_debug_ent
>  #define ELF_ST_VIS(a)	ELF64_ST_VISIBILITY(a)
>  #else
>  #define elf_newehdr	elf32_newehdr
> +#define elf_newphdr	elf32_newphdr
>  #define elf_getshdr	elf32_getshdr
>  #define Elf_Ehdr	Elf32_Ehdr
> +#define Elf_Phdr	Elf32_Phdr
>  #define Elf_Shdr	Elf32_Shdr
>  #define Elf_Sym		Elf32_Sym
>  #define ELF_ST_TYPE(a)	ELF32_ST_TYPE(a)
> -- 
> 2.37.3

-- 

- Arnaldo

      reply	other threads:[~2022-09-20 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  9:29 [PATCH v2] perf jit: Include program header in elf files Lieven Hey
2022-09-20 20:10 ` Arnaldo Carvalho de Melo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YyoeNGZ8wK8pFUjr@kernel.org \
    --to=acme@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=lieven.hey@kdab.com \
    --cc=linux-perf-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).