From: Masami Hiramatsu <mhiramat@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: x86@kernel.org, Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
H Peter Anvin <hpa@zytor.com>, Andi Kleen <ak@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Yu-cheng Yu <yu-cheng.yu@intel.com>
Subject: Re: [PATCH 0/2] x86/insn: Add some more Intel instructions to the opcode map
Date: Mon, 25 Nov 2019 23:29:56 +0900 [thread overview]
Message-ID: <20191125232956.455b5773c5cbdbfa94d0fc81@kernel.org> (raw)
In-Reply-To: <20191125125044.31879-1-adrian.hunter@intel.com>
Hi Adrian,
On Mon, 25 Nov 2019 14:50:42 +0200
Adrian Hunter <adrian.hunter@intel.com> wrote:
> Hi
>
> Here is a patch to update the x86 opcode map, and a patch to update the
> perf tools' "new instructions" test accordingly.
>
> There are still CET instructions to add, which Yu-cheng is doing.
Both looks good (and great!) to me :)
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thank you!
>
>
> Adrian Hunter (2):
> x86/insn: perf tools: Add some more instructions to the new instructions test
> x86/insn: Add some more Intel instructions to the opcode map
>
> arch/x86/lib/x86-opcode-map.txt | 44 +-
> tools/arch/x86/lib/x86-opcode-map.txt | 44 +-
> tools/perf/arch/x86/tests/insn-x86-dat-32.c | 366 +++++++++++++++
> tools/perf/arch/x86/tests/insn-x86-dat-64.c | 484 ++++++++++++++++++++
> tools/perf/arch/x86/tests/insn-x86-dat-src.c | 655 +++++++++++++++++++++++++++
> 5 files changed, 1569 insertions(+), 24 deletions(-)
>
>
> Regards
> Adrian
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2019-11-25 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 12:50 [PATCH 0/2] x86/insn: Add some more Intel instructions to the opcode map Adrian Hunter
2019-11-25 12:50 ` [PATCH 1/2] x86/insn: perf tools: Add some more instructions to the new instructions test Adrian Hunter
2019-11-29 6:02 ` [tip: perf/urgent] " tip-bot2 for Adrian Hunter
2019-11-25 12:50 ` [PATCH 2/2] x86/insn: Add some more Intel instructions to the opcode map Adrian Hunter
2019-11-29 6:02 ` [tip: perf/urgent] " tip-bot2 for Adrian Hunter
2019-11-25 13:46 ` [PATCH 0/2] " Arnaldo Carvalho de Melo
2019-11-25 14:29 ` Masami Hiramatsu [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=20191125232956.455b5773c5cbdbfa94d0fc81@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/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