From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@amacapital.net>, X86 ML <x86@kernel.org>
Subject: Re: [PATCH V2 0/4] x86/insn: perf tools: Add AVX-512 support to the instruction decoder
Date: Thu, 21 Jul 2016 09:39:07 -0300 [thread overview]
Message-ID: <20160721123907.GG18962@kernel.org> (raw)
In-Reply-To: <5790AF8A.1000006@intel.com>
Em Thu, Jul 21, 2016 at 02:18:34PM +0300, Adrian Hunter escreveu:
> On 20/07/16 21:11, Masami Hiramatsu wrote:
> > On Wed, 20 Jul 2016 11:30:33 +0300
> > Adrian Hunter <adrian.hunter@intel.com> wrote:
> >> Here are patches to add support for Intel's AVX-512 instructions to the
> >> instruction decoder. Also there is a patch to fix vcvtph2ps.
> >>
> >> AVX-512 instructions are documented in Intel Architecture Instruction Set
> >> Extensions Programming Reference (February 2016).
> >>
> >> These patches do not conflict with Dan's removal of pcommit.
> >>
> >> Changes in V2:
> >>
> >> Split patches: separate out perf tools and new instructions test.
> >> Amend decription of 'evo' annotation in x86-opcode-map.txt
> >
> > Thanks for updating!
> >
> > Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
> >
> > for the series :)
> >
> > Thank you,
>
> Thanks to Masami's quick ack's, I think it would be reasonable to queue
> these patches for v4.8 unless anyone objects.
>
> Arnaldo, if you are willing, please consider queuing these.
Yeah, I already have it, acked by Masami and Ingo,
Just pushed it in my perf/core branch.
Thanks,
- Arnaldo
prev parent reply other threads:[~2016-07-21 12:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:30 [PATCH V2 0/4] x86/insn: perf tools: Add AVX-512 support to the instruction decoder Adrian Hunter
2016-07-20 8:30 ` [PATCH V2 1/4] x86/insn: perf tools: Fix vcvtph2ps instruction decoding Adrian Hunter
2016-07-25 18:08 ` [tip:perf/core] " tip-bot for Adrian Hunter
2016-07-20 8:30 ` [PATCH V2 2/4] x86/insn: Add AVX-512 support to the instruction decoder Adrian Hunter
2016-07-25 18:08 ` [tip:perf/core] " tip-bot for Adrian Hunter
2025-11-30 16:05 ` [PATCH V2 2/4] " Borislav Petkov
2025-12-01 11:25 ` Borislav Petkov
2025-12-01 18:15 ` Adrian Hunter
2025-12-01 19:01 ` Borislav Petkov
2025-12-02 6:26 ` Adrian Hunter
2025-12-02 10:47 ` Borislav Petkov
2016-07-20 8:30 ` [PATCH V2 3/4] perf tools: Add AVX-512 support to the instruction decoder used by Intel PT Adrian Hunter
2016-07-25 18:09 ` [tip:perf/core] " tip-bot for Adrian Hunter
2016-07-20 8:30 ` [PATCH V2 4/4] perf tools: Add AVX-512 instructions to the new instructions test Adrian Hunter
2016-07-25 18:09 ` [tip:perf/core] " tip-bot for Adrian Hunter
2016-07-20 18:11 ` [PATCH V2 0/4] x86/insn: perf tools: Add AVX-512 support to the instruction decoder Masami Hiramatsu
2016-07-21 11:18 ` Adrian Hunter
2016-07-21 12:39 ` Arnaldo Carvalho de Melo [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=20160721123907.GG18962@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--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