From: Peter Zijlstra <peterz@infradead.org>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
kvm@vger.kernel.org, nathan@kernel.org, ndesaulniers@google.com,
morbo@google.com, justinstitt@google.com, llvm@lists.linux.dev
Subject: Re: [PATCH 01/11] objtool: Generic annotation infrastructure
Date: Fri, 8 Nov 2024 15:16:00 +0100 [thread overview]
Message-ID: <20241108141600.GB6497@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20231204093731.356358182@infradead.org>
On Mon, Dec 04, 2023 at 10:37:03AM +0100, Peter Zijlstra wrote:
> Avoid endless .discard.foo sections for each annotation, create a
> single .discard.annotate section that takes an annotation type along
> with the instruction.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> --- a/include/linux/objtool.h
> +++ b/include/linux/objtool.h
> @@ -57,6 +57,13 @@
> ".long 998b\n\t" \
> ".popsection\n\t"
>
> +#define ASM_ANNOTATE(x) \
> + "911:\n\t" \
> + ".pushsection .discard.annotate,\"M\",@progbits,8\n\t" \
> + ".long 911b - .\n\t" \
> + ".long " __stringify(x) "\n\t" \
> + ".popsection\n\t"
> +
> #else /* __ASSEMBLY__ */
>
> /*
> @@ -146,6 +153,14 @@
> .popsection
> .endm
>
> +.macro ANNOTATE type:req
> +.Lhere_\@:
> + .pushsection .discard.annotate,"M",@progbits,8
> + .long .Lhere_\@ - .
> + .long \type
> + .popsection
> +.endm
> +
> #endif /* __ASSEMBLY__ */
>
> #else /* !CONFIG_OBJTOOL */
> @@ -167,6 +182,8 @@
> .endm
> .macro REACHABLE
> .endm
> +.macro ANNOTATE
> +.endm
> #endif
>
> #endif /* CONFIG_OBJTOOL */
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@ -2308,6 +2308,41 @@ static int read_unwind_hints(struct objt
> return 0;
> }
>
> +static int read_annotate(struct objtool_file *file, void (*func)(int type, struct instruction *insn))
> +{
> + struct section *rsec, *sec;
> + struct instruction *insn;
> + struct reloc *reloc;
> + int type;
> +
> + rsec = find_section_by_name(file->elf, ".rela.discard.annotate");
> + if (!rsec)
> + return 0;
> +
> + sec = find_section_by_name(file->elf, ".discard.annotate");
> + if (!sec)
> + return 0;
> +
> + for_each_reloc(rsec, reloc) {
> + insn = find_insn(file, reloc->sym->sec,
> + reloc->sym->offset + reloc_addend(reloc));
> + if (!insn) {
> + WARN("bad .discard.annotate entry: %d", reloc_idx(reloc));
> + return -1;
> + }
> +
> + type = *(u32 *)(sec->data->d_buf + (reloc_idx(reloc) * sec->sh.sh_entsize) + 4);
> +
> + func(type, insn);
> + }
> +
> + return 0;
> +}
So... ld.lld hates this :-(
From an LLVM=-19 build we can see that:
$ readelf -WS tmp-build/arch/x86/kvm/vmx/vmenter.o | grep annotate
[13] .discard.annotate PROGBITS 0000000000000000 00028c 000018 08 M 0 0 1
$ readelf -WS tmp-build/arch/x86/kvm/kvm-intel.o | grep annotate
[ 3] .discard.annotate PROGBITS 0000000000000000 069fe0 0089d0 00 M 0 0 1
Which tells us that the translation unit itself has a sh_entsize of 8,
while the linked object has sh_entsize of 0.
This then completely messes up the indexing objtool does, which relies
on it being a sane number.
GCC/binutils very much does not do this, it retains the 8.
Dear clang folks, help?
next parent reply other threads:[~2024-11-08 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231204093702.989848513@infradead.org>
[not found] ` <20231204093731.356358182@infradead.org>
2024-11-08 14:16 ` Peter Zijlstra [this message]
2024-11-08 14:57 ` [PATCH 01/11] objtool: Generic annotation infrastructure Nathan Chancellor
2024-11-08 15:13 ` Peter Zijlstra
2024-11-08 19:03 ` Peter Zijlstra
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=20241108141600.GB6497@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=justinstitt@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@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