From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Don Zickus <dzickus@redhat.com>,
Stephane Eranian <eranian@google.com>,
Lin Ming <ming.m.lin@intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip, final] perf, x86: Add hw_watchdog_set_attr() in a sake of nmi-watchdog on P4
Date: Tue, 5 Jul 2011 14:34:03 +0400 [thread overview]
Message-ID: <20110705103403.GN17941@sun> (raw)
In-Reply-To: <20110705102017.GA12458@elte.hu>
On Tue, Jul 05, 2011 at 12:20:17PM +0200, Ingo Molnar wrote:
>
> * Cyrill Gorcunov <gorcunov@gmail.com> wrote:
...
>
> So why don't we simply set this for all PERF_COUNT_HW_CPU_CYCLES
> events in the P4 PMU driver? That would remove half of the patch
> AFAICS.
>
> Thanks,
>
> Ingo
Unfortunately it doesn't solve the main issue -- nmi-watchdog events
and cpu clock events should be a separate events with non-intersected
ESCRs, otherwise nmi-watchdog and cpu-cycles can't operate simultaneously
like other PMUs does.
non-sleeping ticks use
[P4_EVENT_EXECUTION_EVENT] = {
.escr_msr = { MSR_P4_CRU_ESCR2, MSR_P4_CRU_ESCR3 },
.cntr = { {12, 13, 16}, {14, 15, 17}
},
while cpu-cycles
[P4_EVENT_GLOBAL_POWER_EVENTS] = {
.escr_msr = { MSR_P4_FSB_ESCR0, MSR_P4_FSB_ESCR1 },
.cntr = { {0, -1, -1}, {2, -1, -1} },
},
Note non-intersection of { MSR_P4_CRU_ESCR2, MSR_P4_CRU_ESCR3 } and
{ MSR_P4_FSB_ESCR0, MSR_P4_FSB_ESCR1 } here (together with counters
itselves pointed by .cntr).
Cyrill
next prev parent reply other threads:[~2011-07-05 10:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 10:03 [PATCH -tip, final] perf, x86: Add hw_watchdog_set_attr() in a sake of nmi-watchdog on P4 Cyrill Gorcunov
2011-07-05 10:20 ` Ingo Molnar
2011-07-05 10:34 ` Cyrill Gorcunov [this message]
2011-07-05 10:59 ` Ingo Molnar
2011-07-05 11:05 ` Cyrill Gorcunov
2011-07-05 11:20 ` Ingo Molnar
2011-07-05 11:36 ` Cyrill Gorcunov
2011-07-05 11:44 ` Ingo Molnar
2011-07-05 11:49 ` Cyrill Gorcunov
2011-07-05 12:14 ` Cyrill Gorcunov
2011-07-05 13:10 ` Ingo Molnar
2011-07-05 13:17 ` Peter Zijlstra
2011-07-05 13:31 ` Ingo Molnar
2011-07-05 14:19 ` Cyrill Gorcunov
2011-07-08 12:44 ` Ingo Molnar
2011-07-05 14:20 ` Peter Zijlstra
2011-07-05 14:40 ` Peter Zijlstra
2011-07-05 14:56 ` Ingo Molnar
2011-07-05 15:25 ` Cyrill Gorcunov
2011-07-06 7:01 ` Cyrill Gorcunov
2011-07-08 12:49 ` Ingo Molnar
2011-07-08 13:01 ` Cyrill Gorcunov
2011-07-08 13:09 ` Ingo Molnar
2011-07-08 13:12 ` Cyrill Gorcunov
2011-07-05 13:26 ` Cyrill Gorcunov
2011-07-05 12:24 ` Don Zickus
2011-07-05 12:26 ` Cyrill Gorcunov
2011-07-05 12:44 ` Don Zickus
2011-07-05 12:56 ` Cyrill Gorcunov
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=20110705103403.GN17941@sun \
--to=gorcunov@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=dzickus@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
/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