From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
davidcc@google.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kan.liang@intel.com, Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Anvin <hpa@zytor.com>, Borislav Petkov <bp@suse.de>,
Paul Turner <pjt@google.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Stephane Eranian <eranian@google.com>,
Ingo Molnar <mingo@kernel.org>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:perf/urgent] perf/x86: Set pmu->module in Intel PMU modules
Date: Thu, 5 Jan 2017 21:24:21 +0100 [thread overview]
Message-ID: <20170105202421.GA3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+55aFyrComaHiGVUkU3P2xx1hh_41xR5KNqKVPof75iU8+gNw@mail.gmail.com>
On Thu, Jan 05, 2017 at 10:46:30AM -0800, Linus Torvalds wrote:
> On Thu, Jan 5, 2017 at 7:52 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> >
> > The first time I saw this I thought about doing something like the
> > below, but never got around to testing if that works and subsequently
> > forgot about things again.
> >
> > Does this make sense and or work?
>
> I'd argue against it.
Fair enough; /me files it in the bit-bucket.
prev parent reply other threads:[~2017-01-05 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 1:17 [PATCH] perf/x86: set pmu->module in Intel PMU modules David Carrillo-Cisneros
2017-01-05 15:07 ` [tip:perf/urgent] perf/x86: Set " tip-bot for David Carrillo-Cisneros
2017-01-05 15:52 ` Peter Zijlstra
2017-01-05 18:46 ` Linus Torvalds
2017-01-05 20:24 ` Peter Zijlstra [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=20170105202421.GA3092@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=davidcc@google.com \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pjt@google.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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