From: Adrian Hunter <adrian.hunter@intel.com>
To: Borislav Petkov <bp@alien8.de>, Peter Zijlstra <peterz@infradead.org>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, H Peter Anvin <hpa@zytor.com>,
chang.seok.bae@intel.com, Masami Hiramatsu <mhiramat@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH 0/6] x86/insn: Add instructions to instruction decoder
Date: Thu, 13 Jan 2022 08:52:58 +0200 [thread overview]
Message-ID: <678169e0-de12-6a61-d0df-cd898b9377a9@intel.com> (raw)
In-Reply-To: <YdNArxYU25LfrS52@kernel.org>
On 03/01/2022 20:30, Arnaldo Carvalho de Melo wrote:
> Em Mon, Jan 03, 2022 at 03:22:59PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Jan 03, 2022 at 05:40:00PM +0200, Adrian Hunter escreveu:
>>> On 03/01/2022 17:01, Arnaldo Carvalho de Melo wrote:
>>>> Em Mon, Jan 03, 2022 at 11:56:08AM -0300, Arnaldo Carvalho de Melo escreveu:
>>>> So since this needs rebasing, could you please split it into two
>>>> patchsets, one for tools/ and another for arch and send two batches?
>>>> This way I'll pick the tools/ one, the x86 maintainers the other bits.
>
>>>> Otherwise the x86 maintainers would have to test if the tools/ bits
>>>> works as expected, etc.
>
>>> It seems not to be happening for me. What tree/branch is it?
>
>> tmp.perf/core
>
>> https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/log/?h=tmp.perf/core
>
>> I merged torvalds/master today, but it should work as that file was last
>> changed looong ago:
>
>> ⬢[acme@toolbox perf]$ git log arch/x86/lib/x86-opcode-map.txt | head
>> commit 5790921bc18b1eb5c0c61371e31114fd4c4b0154
>> Author: Yu-cheng Yu <yu-cheng.yu@intel.com>
>> Date: Tue Feb 4 09:14:24 2020 -0800
>>
>> x86/insn: Add Control-flow Enforcement (CET) instructions to the opcode map
>>
>> Add the following CET instructions to the opcode map:
>>
>> INCSSP:
>> Increment Shadow Stack pointer (SSP).
>> ⬢[acme@toolbox perf]$
>>
>> Perhaps related to b4? I'll try updating it and retrying...
>
> Now it should work:
>
> ⬢[acme@toolbox perf]$ b4 am -ctsl --cc-trailers c7ac518e-82fb-eb51-7778-5e9b1aaed9a9@intel.com
> <SNIP>
> Cover: ./20211202_adrian_hunter_x86_insn_add_instructions_to_instruction_decoder.cover
> Link: https://lore.kernel.org/r/20211202095029.2165714-1-adrian.hunter@intel.com
> Base: applies clean to current tree
> git checkout -b 20211202_adrian_hunter_intel_com HEAD
> git am ./20211202_adrian_hunter_x86_insn_add_instructions_to_instruction_decoder.mbx
> ⬢[acme@toolbox perf]$
>
> Lets see...
>
> ⬢[acme@toolbox perf]$ git am ./20211202_adrian_hunter_x86_insn_add_instructions_to_instruction_decoder.mbx
> Applying: perf tests: Add AMX instructions to x86 instruction decoder test
> Applying: x86/insn: Add AMX instructions to x86 instruction decoder
> Applying: perf tests: Add misc instructions to x86 instruction decoder test
> Applying: x86/insn: Add misc instructions to x86 instruction decoder
> Applying: perf tests: Add AVX512-FP16 instructions to x86 instruction decoder test
> Applying: x86/insn: Add AVX512-FP16 instructions to x86 instruction decoder
> ⬢[acme@toolbox perf]$
>
> Yeah, it works, builds and the 'perf test instr' test case succeeds, so
> if Peter or Borislav so wishes please process this patchkit as-is:
>
> Acked-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Peter or Borislav, could these patches be considered as a late inclusion for v5.17?
next prev parent reply other threads:[~2022-01-13 6:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 9:50 Adrian Hunter
2021-12-02 9:50 ` [PATCH 1/6] perf tests: Add AMX instructions to x86 instruction decoder test Adrian Hunter
2022-01-23 19:44 ` [tip: x86/misc] perf/tests: " tip-bot2 for Adrian Hunter
2021-12-02 9:50 ` [PATCH 2/6] x86/insn: Add AMX instructions to x86 instruction decoder Adrian Hunter
2022-01-23 19:44 ` [tip: x86/misc] x86/insn: Add AMX instructions to the " tip-bot2 for Adrian Hunter
2021-12-02 9:50 ` [PATCH 3/6] perf tests: Add misc instructions to x86 instruction decoder test Adrian Hunter
2022-01-23 19:44 ` [tip: x86/misc] perf/tests: Add misc instructions to the " tip-bot2 for Adrian Hunter
2021-12-02 9:50 ` [PATCH 4/6] x86/insn: Add misc instructions to x86 instruction decoder Adrian Hunter
2022-01-23 19:44 ` [tip: x86/misc] " tip-bot2 for Adrian Hunter
2021-12-02 9:50 ` [PATCH 5/6] perf tests: Add AVX512-FP16 instructions to x86 instruction decoder test Adrian Hunter
2022-01-23 19:44 ` [tip: x86/misc] perf/tests: " tip-bot2 for Adrian Hunter
2021-12-02 9:50 ` [PATCH 6/6] x86/insn: Add AVX512-FP16 instructions to x86 instruction decoder Adrian Hunter
2022-01-23 19:44 ` [tip: x86/misc] x86/insn: Add AVX512-FP16 instructions to the " tip-bot2 for Adrian Hunter
2021-12-23 6:38 ` [PATCH 0/6] x86/insn: Add instructions to " Masami Hiramatsu
2022-01-03 8:13 ` Adrian Hunter
2022-01-03 14:56 ` Arnaldo Carvalho de Melo
2022-01-03 15:01 ` Arnaldo Carvalho de Melo
2022-01-03 15:40 ` Adrian Hunter
2022-01-03 18:22 ` Arnaldo Carvalho de Melo
2022-01-03 18:30 ` Arnaldo Carvalho de Melo
2022-01-13 6:52 ` Adrian Hunter [this message]
2022-01-13 10:16 ` Borislav Petkov
2022-01-13 10:33 ` Adrian Hunter
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=678169e0-de12-6a61-d0df-cd898b9377a9@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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®