From: Sasha Levin <sashal@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: stable@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH 4.14 0/5] perf machine: Workaround missing maps for x86 PTI entry trampolines
Date: Fri, 23 Nov 2018 14:47:53 -0500 [thread overview]
Message-ID: <20181123194753.GK1917@sasha-vm> (raw)
In-Reply-To: <20181121135247.23304-1-adrian.hunter@intel.com>
On Wed, Nov 21, 2018 at 03:52:42PM +0200, Adrian Hunter wrote:
>Hi
>
>x86 PTI trampolines were backported to 4.14, refer
>commit: c631a16e5b84521ae80ab10d47cd6ccd2afc6817 ("x86/entry/64:
>Create a per-CPU SYSCALL entry trampoline")
>so the corresponding perf tools workaround also needs to be backported.
>Here are 5 patches for 4.14 stable backported from 4.18, to address that.
Queued for 4.14, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2018-11-24 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 13:52 [PATCH 4.14 0/5] perf machine: Workaround missing maps for x86 PTI entry trampolines Adrian Hunter
2018-11-21 13:52 ` [PATCH 4.14 1/5] perf machine: Add machine__is() to identify machine arch Adrian Hunter
2018-11-21 13:52 ` [PATCH 4.14 2/5] perf tools: Fix kernel_start for PTI on x86 Adrian Hunter
2018-11-21 13:52 ` [PATCH 4.14 3/5] perf machine: Add nr_cpus_avail() Adrian Hunter
2018-11-21 13:52 ` [PATCH 4.14 4/5] perf machine: Workaround missing maps for x86 PTI entry trampolines Adrian Hunter
2018-11-21 13:52 ` [PATCH 4.14 5/5] perf test code-reading: Fix perf_env setup for " Adrian Hunter
2018-11-23 19:47 ` Sasha Levin [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=20181123194753.GK1917@sasha-vm \
--to=sashal@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=luto@kernel.org \
--cc=stable@vger.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