From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Masami Hiramatsu <mhiramat@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] objtool: drop redundant flags generation
Date: Mon, 6 Mar 2017 11:25:37 -0600 [thread overview]
Message-ID: <20170306172537.uox2f7ru3x72jzea@treble> (raw)
In-Reply-To: <1488819625-27395-1-git-send-email-der.herr@hofr.at>
On Mon, Mar 06, 2017 at 06:00:25PM +0100, Nicholas Mc Guire wrote:
> The generator was emitting quite a few duplicate flags which was making
> doublebitand.cocci nervous. This awk hack resolves the duplicate issue.
>
> Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
> ---
>
> The coccinelle complaints emitted was about 230 findings total:
> ./arch/x86/lib/inat-tables.c:214:10-20: duplicated argument to & or |
> ./arch/x86/lib/inat-tables.c:214:23-33: duplicated argument to & or |
> ./arch/x86/lib/inat-tables.c:218:10-20: duplicated argument to & or |
> ./arch/x86/lib/inat-tables.c:218:23-33: duplicated argument to & or |
> ....
> ./tools/objtool/arch/x86/insn/inat-tables.c:214:10-20: duplicated argument to & or |
> ./tools/objtool/arch/x86/insn/inat-tables.c:214:23-33: duplicated argument to & or |
> ./tools/objtool/arch/x86/insn/inat-tables.c:218:10-20: duplicated argument to & or |
> ./tools/objtool/arch/x86/insn/inat-tables.c:218:23-33: duplicated argument to & or |
> ...
> spatch --sp-file scripts/coccinelle/tests/doublebitand.cocci inat-tables.c -D report
> will give you the full list - all are caused by duplicates in the generated
> output by the add_flags function in the two instances of gen-insn-attr-x86.awk.
>
> Q: The two copies of gen-insn-attr-x86.awk are identical and its not actually clear
> why this duplication is needed ? Further the maintainers list emitted for the
> two files differ.
>
> Patch was checked by manual review of the diff between the initial file and the
> regenerated file after the below patch was applied.
> Second verification was by make tools/objtool and comparing the generated binaries
> in tools/objtool/arch/x86/decode.o with diff.
>
> Patch is against 4.11-rc1 (localversion-next is next-20170306)
>
> arch/x86/tools/gen-insn-attr-x86.awk | 12 ++++++++++--
> tools/objtool/arch/x86/insn/gen-insn-attr-x86.awk | 12 ++++++++++--
There's actually a third copy of the decoder in:
tools/perf/util/intel-pt-decoder/
Yes, the duplication is a pain, but it's part of an effort to keep
'tools/*' source independent from kernel code.
Maybe we can at least combine the objtool and perf versions someday.
--
Josh
next prev parent reply other threads:[~2017-03-06 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 17:00 Nicholas Mc Guire
2017-03-06 17:25 ` Josh Poimboeuf [this message]
2017-03-06 17:54 ` Nicholas Mc Guire
2017-03-06 21:40 ` Josh Poimboeuf
2017-03-07 8:13 ` Nicholas Mc Guire
2017-03-07 13:55 ` Masami Hiramatsu
2017-03-07 14:18 ` Nicholas Mc Guire
2017-03-07 8:16 ` Masami Hiramatsu
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=20170306172537.uox2f7ru3x72jzea@treble \
--to=jpoimboe@redhat.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=der.herr@hofr.at \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®