From: Stephane Eranian <eranian@google.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Don Zickus <dzickus@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Lin Ming <ming.m.lin@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Vince Weaver <vweaver1@eecs.utk.edu>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC -tip] perf, x86: Add PERF_COUNT_HW_NMI_WATCHDOG event v2
Date: Thu, 23 Jun 2011 14:31:14 +0200 [thread overview]
Message-ID: <BANLkTimKpnbus2rStk7V4-2sbv5cUbz8NA@mail.gmail.com> (raw)
In-Reply-To: <20110623122648.GI10238@sun>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 5959 bytes --]
Yes.
On Thu, Jun 23, 2011 at 2:26 PM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> On Thu, Jun 23, 2011 at 04:07:32PM +0400, Cyrill Gorcunov wrote:
>> On Thu, Jun 23, 2011 at 02:03:50PM +0200, Stephane Eranian wrote:
>> ...
>> > >
>> > No, first level in watchdog.c, the other callback has to be implemented
>> > from x86_pmu as you had it.
>> >
> Something like below I suppose
>
> Â Â Â Â Cyrill
> ---
>  arch/x86/kernel/cpu/perf_event.c   |   7 +++++++
> Â arch/x86/kernel/cpu/perf_event_p4.c | Â 26 ++++++++++++++++++++++++++
>  kernel/watchdog.c          |   6 +++++-
> Â 3 files changed, 38 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.git/arch/x86/kernel/cpu/perf_event.c
> ===================================================================
> --- linux-2.6.git.orig/arch/x86/kernel/cpu/perf_event.c
> +++ linux-2.6.git/arch/x86/kernel/cpu/perf_event.c
> @@ -233,6 +233,7 @@ struct x86_pmu {
>     void       (*enable_all)(int added);
>     void       (*enable)(struct perf_event *);
>     void       (*disable)(struct perf_event *);
> +    void       (*hw_watchdog_set_attr)(struct perf_event_attr *attr);
>     int       (*hw_config)(struct perf_event *event);
>     int       (*schedule_events)(struct cpu_hw_events *cpuc, int n, int *assign);
>     unsigned     eventsel;
> @@ -315,6 +316,12 @@ static u64 __read_mostly hw_cache_extra_
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [PERF_COUNT_HW_CACHE_OP_MAX]
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [PERF_COUNT_HW_CACHE_RESULT_MAX];
>
> +void hw_nmi_watchdog_set_attr(struct perf_event_attr *wd_attr)
> +{
> + Â Â Â if (x86_pmu.hw_watchdog_set_attr)
> + Â Â Â Â Â Â Â x86_pmu.hw_watchdog_set_attr(wd_attr);
> +}
> +
> Â /*
> Â * Propagate event elapsed time into the generic event.
> Â * Can only be executed on the CPU where the event is active.
> Index: linux-2.6.git/arch/x86/kernel/cpu/perf_event_p4.c
> ===================================================================
> --- linux-2.6.git.orig/arch/x86/kernel/cpu/perf_event_p4.c
> +++ linux-2.6.git/arch/x86/kernel/cpu/perf_event_p4.c
> @@ -705,6 +705,31 @@ static int p4_validate_raw_event(struct
> Â Â Â Â return 0;
> Â }
>
> +static void p4_hw_watchdog_set_attr(struct perf_event_attr *wd_attr)
> +{
> + Â Â Â /*
> + Â Â Â Â * Watchdog ticks are special on Netburst, we use
> + Â Â Â Â * that named "non-sleeping" ticks as recommended
> + Â Â Â Â * by Intel SDM Vol3b.
> + Â Â Â Â */
> +    WARN_ON_ONCE(wd_attr->type    != PERF_TYPE_HARDWARE ||
> +           wd_attr->config   != PERF_COUNT_HW_CPU_CYCLES);
> +
> +    wd_attr->type  = PERF_TYPE_RAW;
> + Â Â Â wd_attr->config =
> + Â Â Â Â Â Â Â p4_config_pack_escr(P4_ESCR_EVENT(P4_EVENT_EXECUTION_EVENT) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS0) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS1) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS2) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, NBOGUS3) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS0) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS1) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS2) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_ESCR_EMASK_BIT(P4_EVENT_EXECUTION_EVENT, BOGUS3)) Â Â Â Â Â Â |
> + Â Â Â Â Â Â Â p4_config_pack_cccr(P4_CCCR_THRESHOLD(15) | P4_CCCR_COMPLEMENT Â Â Â Â Â |
> + Â Â Â Â Â Â Â Â Â Â Â P4_CCCR_COMPARE);
> +}
> +
> Â static int p4_hw_config(struct perf_event *event)
> Â {
> Â Â Â Â int cpu = get_cpu();
> @@ -1179,6 +1204,7 @@ static __initconst const struct x86_pmu
>     .cntval_bits       = ARCH_P4_CNTRVAL_BITS,
>     .cntval_mask       = ARCH_P4_CNTRVAL_MASK,
>     .max_period       = (1ULL << (ARCH_P4_CNTRVAL_BITS - 1)) - 1,
> +    .hw_watchdog_set_attr  = p4_hw_watchdog_set_attr,
>     .hw_config        = p4_hw_config,
>     .schedule_events     = p4_pmu_schedule_events,
> Â Â Â Â /*
> Index: linux-2.6.git/kernel/watchdog.c
> ===================================================================
> --- linux-2.6.git.orig/kernel/watchdog.c
> +++ linux-2.6.git/kernel/watchdog.c
> @@ -200,6 +200,8 @@ static int is_softlockup(unsigned long t
> Â }
>
> Â #ifdef CONFIG_HARDLOCKUP_DETECTOR
> +void __weak hw_nmi_watchdog_set_attr(struct perf_event_attr *wd_attr) { }
> +
> Â static struct perf_event_attr wd_hw_attr = {
>     .type      = PERF_TYPE_HARDWARE,
>     .config     = PERF_COUNT_HW_CPU_CYCLES,
> @@ -368,9 +370,11 @@ static int watchdog_nmi_enable(int cpu)
> Â Â Â Â if (event != NULL)
> Â Â Â Â Â Â Â Â goto out_enable;
>
> - Â Â Â /* Try to register using hardware perf events */
> Â Â Â Â wd_attr = &wd_hw_attr;
> Â Â Â Â wd_attr->sample_period = hw_nmi_get_sample_period(watchdog_thresh);
> + Â Â Â hw_nmi_watchdog_set_attr(wd_attr);
> +
> + Â Â Â /* Try to register using hardware perf events */
> Â Â Â Â event = perf_event_create_kernel_counter(wd_attr, cpu, NULL, watchdog_overflow_callback);
> Â Â Â Â if (!IS_ERR(event)) {
> Â Â Â Â Â Â Â Â printk(KERN_INFO "NMI watchdog enabled, takes one hw-pmu counter.\n");
>
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2011-06-23 12:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 15:37 Cyrill Gorcunov
2011-06-21 15:23 ` Don Zickus
2011-06-21 15:40 ` Cyrill Gorcunov
2011-06-21 15:58 ` Peter Zijlstra
2011-06-21 16:13 ` Cyrill Gorcunov
2011-06-21 16:20 ` Stephane Eranian
2011-06-21 16:48 ` Cyrill Gorcunov
2011-06-21 17:02 ` Cyrill Gorcunov
2011-06-21 17:10 ` Stephane Eranian
2011-06-21 17:23 ` Cyrill Gorcunov
2011-06-21 17:26 ` Stephane Eranian
2011-06-21 17:54 ` Cyrill Gorcunov
2011-06-21 18:06 ` Stephane Eranian
2011-06-21 18:32 ` Cyrill Gorcunov
2011-06-22 8:27 ` Cyrill Gorcunov
2011-06-22 9:21 ` Cyrill Gorcunov
2011-06-23 6:48 ` Cyrill Gorcunov
2011-06-23 9:40 ` Stephane Eranian
2011-06-23 9:54 ` Cyrill Gorcunov
2011-06-23 11:07 ` Cyrill Gorcunov
2011-06-23 11:40 ` Don Zickus
2011-06-23 11:44 ` Stephane Eranian
2011-06-23 11:53 ` Cyrill Gorcunov
2011-06-23 12:03 ` Stephane Eranian
2011-06-23 12:07 ` Cyrill Gorcunov
2011-06-23 12:26 ` Cyrill Gorcunov
2011-06-23 12:31 ` Stephane Eranian [this message]
2011-06-23 12:34 ` Cyrill Gorcunov
2011-06-23 11:51 ` 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=BANLkTimKpnbus2rStk7V4-2sbv5cUbz8NA@mail.gmail.com \
--to=eranian@google.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=dzickus@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=vweaver1@eecs.utk.edu \
/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
all inboxes | Powered by JetHome®