mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Yu-cheng Yu <yu-cheng.yu@intel.com>, Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Andi Kleen <andi.kleen@intel.com>,
	Tony Luck <tony.luck@intel.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"Ravi V. Shankar" <ravi.v.shankar@intel.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/2] Introduce Control-flow Enforcement opcodes
Date: Tue, 3 Mar 2020 19:35:50 +0900	[thread overview]
Message-ID: <20200303193550.692bf2be0ee800c21bd05215@kernel.org> (raw)
In-Reply-To: <20200204171425.28073-1-yu-cheng.yu@intel.com>

Hi,

On Tue,  4 Feb 2020 09:14:23 -0800
Yu-cheng Yu <yu-cheng.yu@intel.com> wrote:

> Control-flow Enforcement (CET) introduces 10 new instructions [1].  Add
> them to the opcode map.  This series has been separated from the CET
> patches [2] for ease of review.
> 
> [1] Detailed information on CET can be found in "Intel 64 and IA-32
>     Architectures Software Developer's Manual":
> 
>     https://software.intel.com/en-us/download/intel-64-and-ia-32-
>     architectures-sdm-combined-volumes-1-2a-2b-2c-2d-3a-3b-3c-3d-and-4
> 
> [2] CET patches:
> 
>     https://lkml.kernel.org/r/20190813205225.12032-1-yu-cheng.yu@intel.com/
>     https://lkml.kernel.org/r/20190813205359.12196-1-yu-cheng.yu@intel.com/

Sorry, somewhat I've missed this series...

This looks good to me.

Acked-by: Masami Hiramatsu <mhiramat@kernel.org>

for this series.

Thank you,

> 
> Adrian Hunter (1):
>   x86/insn: perf tools: Add CET instructions to the new instructions
>     test
> 
> Yu-cheng Yu (1):
>   x86/insn: Add Control-flow Enforcement (CET) instructions to the
>     opcode map
> 
>  arch/x86/lib/x86-opcode-map.txt              |  17 +-
>  tools/arch/x86/lib/x86-opcode-map.txt        |  17 +-
>  tools/perf/arch/x86/tests/insn-x86-dat-32.c  | 112 +++++++++
>  tools/perf/arch/x86/tests/insn-x86-dat-64.c  | 196 +++++++++++++++
>  tools/perf/arch/x86/tests/insn-x86-dat-src.c | 236 +++++++++++++++++++
>  5 files changed, 566 insertions(+), 12 deletions(-)
> 
> -- 
> 2.21.0
> 


-- 
Masami Hiramatsu <mhiramat@kernel.org>

  parent reply	other threads:[~2020-03-03 10:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 17:14 Yu-cheng Yu
2020-02-04 17:14 ` [PATCH 1/2] x86/insn: Add Control-flow Enforcement (CET) instructions to the opcode map Yu-cheng Yu
2020-03-26 11:40   ` [tip: x86/misc] " tip-bot2 for Yu-cheng Yu
2020-04-04  8:41   ` [tip: perf/urgent] " tip-bot2 for Yu-cheng Yu
2020-02-04 17:14 ` [PATCH 2/2] x86/insn: perf tools: Add CET instructions to the new instructions test Yu-cheng Yu
2020-03-26 11:40   ` [tip: x86/misc] perf/tests: " tip-bot2 for Adrian Hunter
2020-04-04  8:41   ` [tip: perf/urgent] perf test x86: " tip-bot2 for Adrian Hunter
2020-03-03 10:35 ` Masami Hiramatsu [this message]
2020-03-26  5:11   ` [PATCH 0/2] Introduce Control-flow Enforcement opcodes Adrian Hunter
2020-03-26 14:26     ` Arnaldo Carvalho de Melo

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=20200303193550.692bf2be0ee800c21bd05215@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=andi.kleen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --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

Powered by JetHome