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 15:40:54 -0600 [thread overview]
Message-ID: <20170306214054.tobodci764xvbwr7@treble> (raw)
In-Reply-To: <20170306175401.GA26026@osadl.at>
On Mon, Mar 06, 2017 at 05:54:01PM +0000, Nicholas Mc Guire wrote:
> On Mon, Mar 06, 2017 at 11:25:37AM -0600, Josh Poimboeuf wrote:
> > > 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.
> >
> Bad - missed that one - did not build perf - the generator seems to
> be the same though only differing by a single blank line - so pulling
> those together should be a non-issue atleast with respect to the
> generator as the x86-opcode-map.txt are all the same ? ...or what
> fun am I missing ?
In theory, all three copies of the decoder should be identical. That
includes all the files: insn.[ch], inat.[ch], inat_types.h,
gen-insn-attr-x86.awk, x86-opcode-map.txt.
--
Josh
next prev parent reply other threads:[~2017-03-06 21:41 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
2017-03-06 17:54 ` Nicholas Mc Guire
2017-03-06 21:40 ` Josh Poimboeuf [this message]
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=20170306214054.tobodci764xvbwr7@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®