From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH 0/2] perf/x86/intel/bts: Small fixes
Date: Tue, 10 Dec 2019 18:40:47 +0100 [thread overview]
Message-ID: <20191210174047.GQ2844@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191205142853.28894-1-alexander.shishkin@linux.intel.com>
On Thu, Dec 05, 2019 at 05:28:51PM +0300, Alexander Shishkin wrote:
> Hi Peter and Ingo,
>
> Here are two small fixes that resulted from running perf_fuzzer on a !KPTI
> kernel. One is a misguided and unannotated warning and another is a sketchy
> use of page_private(). The choice between deleting the BTS driver and
> fixing it is not obvious, though. It may theoretically still have users.
>
> Alexander Shishkin (2):
> perf/x86/intel/bts: Remove a silly warning
> perf/x86/intel/bts: Fix the use of page_private()
I'll squash the pair, that makes more sense to me.
next prev parent reply other threads:[~2019-12-10 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 14:28 [PATCH 0/2] perf/x86/intel/bts: Small fixes Alexander Shishkin
2019-12-05 14:28 ` [PATCH 1/2] perf/x86/intel/bts: Remove a silly warning Alexander Shishkin
2019-12-10 15:29 ` Peter Zijlstra
2019-12-17 12:39 ` [tip: perf/urgent] perf/x86/intel/bts: Fix the use of page_private() tip-bot2 for Alexander Shishkin
2019-12-05 14:28 ` [PATCH 2/2] " Alexander Shishkin
2019-12-10 15:35 ` Peter Zijlstra
2019-12-11 0:23 ` Peter Zijlstra
2019-12-11 6:26 ` Alexander Shishkin
2019-12-10 17:40 ` Peter Zijlstra [this message]
2019-12-11 11:33 ` [PATCH 0/2] perf/x86/intel/bts: Small fixes Alexander Shishkin
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=20191210174047.GQ2844@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.