From: Peter Zijlstra <peterz@infradead.org>
To: "Rogozhkin, Dmitry V" <dmitry.v.rogozhkin@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC v2 2/3] drm/i915/pmu: serve global events and support perf stat
Date: Wed, 30 Aug 2017 22:03:40 +0200 [thread overview]
Message-ID: <20170830200340.GP6524@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <1504084943.18626.5.camel@intel.com>
On Wed, Aug 30, 2017 at 05:24:30PM +0000, Rogozhkin, Dmitry V wrote:
> Ok... but they could register for just cpu0. Besides, it looks like on
> Linux cpu0 can't go offline at all at least of x86 architecture. Peter,
> could you, please, clarify the reasoning to register designated readers
> of uncore PMU for few CPUs?
arch/x86/Kconfig:config BOOTPARAM_HOTPLUG_CPU0
means we cannot rely on CPU0 being present, even on x86.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-31 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 15:26 [RFC v2 0/3] Support perf stat with i915 PMU Dmitry Rogozhkin
2017-08-23 15:26 ` [RFC v2 1/3] drm/i915/pmu: reorder function to suite next patch Dmitry Rogozhkin
2017-08-23 15:26 ` [RFC v2 2/3] drm/i915/pmu: serve global events and support perf stat Dmitry Rogozhkin
2017-08-23 23:38 ` Rogozhkin, Dmitry V
2017-08-28 22:45 ` Rogozhkin, Dmitry V
2017-08-29 9:28 ` Peter Zijlstra
2017-08-30 17:24 ` Rogozhkin, Dmitry V
2017-08-30 20:03 ` Peter Zijlstra [this message]
2017-08-30 20:05 ` Peter Zijlstra
2017-08-23 15:26 ` [RFC v2 3/3] drm/i915/pmu: deny perf driver level sampling of i915 PMU Dmitry Rogozhkin
2017-08-23 23:43 ` Rogozhkin, Dmitry V
[not found] ` <3EDB40B547243546A1017B798F8C1AA8847FC002@ORSMSX114.amr.corp.intel.com>
[not found] ` <150368515309.27971.17522435118048475155@mail.alporthouse.com>
2017-08-25 19:01 ` Rogozhkin, Dmitry V
2017-08-31 7:41 ` Peter Zijlstra
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=20170830200340.GP6524@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dmitry.v.rogozhkin@intel.com \
--cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).