From: Jiri Olsa <jolsa@redhat.com>
To: Megha Dey <megha.dey@linux.intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, andriy.shevchenko@linux.intel.com,
kstewart@linuxfoundation.org, yu-cheng.yu@intel.com,
len.brown@intel.com, gregkh@linuxfoundation.org,
peterz@infradead.org, acme@kernel.org,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
vikas.shivappa@linux.intel.com, pombredanne@nexb.com,
me@kylehuey.com, bp@suse.de, grzegorz.andrejczuk@intel.com,
tony.luck@intel.com, corbet@lwn.net, ravi.v.shankar@intel.com,
megha.dey@intel.com
Subject: Re: [PATCH V0 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support
Date: Sat, 4 Nov 2017 14:24:59 +0100 [thread overview]
Message-ID: <20171104132459.GA8454@krava> (raw)
In-Reply-To: <1509732006-5917-3-git-send-email-megha.dey@linux.intel.com>
On Fri, Nov 03, 2017 at 11:00:05AM -0700, Megha Dey wrote:
SNIP
> +
> +static int intel_bm_event_nmi_handler(unsigned int cmd, struct pt_regs *regs)
> +{
> + struct perf_event *event;
> + union bm_detect_status stat;
> + struct perf_sample_data data;
> + int i;
> + unsigned long x;
> +
> + rdmsrl(BR_DETECT_STATUS_MSR, stat.raw);
> +
> + if (stat.event) {
> + wrmsrl(BR_DETECT_STATUS_MSR, 0);
> + apic_write(APIC_LVTPC, APIC_DM_NMI);
> + /*
> + * Issue wake-up to corrresponding polling event
> + */
> + x = stat.ctrl_hit;
> + for_each_set_bit(i, &x, bm_num_counters) {
> + event = bm_counter_owner[i];
> + perf_sample_data_init(&data, 0, event->hw.last_period);
> + perf_event_overflow(event, &data, regs);
hum, it's non sampling events only right? then you don't need
any of the perf_sample_data stuff.. the perf_event_overflow call
is basicaly nop
> + local64_inc(&event->count);
> + atomic_set(&event->hw.bm_poll, POLLIN);
> + event->pending_wakeup = 1;
> + irq_work_queue(&event->pending);
also this is for sampling events only
seems like you only want to increment the event->count in here
thanks,
jirka
> + }
> + return NMI_HANDLED;
> + }
> + return NMI_DONE;
> +}
SNIP
next prev parent reply other threads:[~2017-11-04 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 18:00 [PATCH V0 0/3] perf/x86/intel: Add Branch Monitoring support Megha Dey
2017-11-03 18:00 ` [PATCH V0 1/3] x86/cpu/intel: Add Cannonlake to Intel family Megha Dey
2017-11-03 18:00 ` [PATCH V0 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support Megha Dey
2017-11-04 13:24 ` Jiri Olsa [this message]
2017-11-11 0:42 ` Dey, Megha
2017-11-04 13:25 ` Jiri Olsa
2017-11-11 0:44 ` Dey, Megha
2017-11-04 13:25 ` Jiri Olsa
2017-11-04 13:25 ` Jiri Olsa
2017-11-11 0:50 ` Dey, Megha
2017-11-04 13:26 ` Jiri Olsa
2017-11-11 0:53 ` Dey, Megha
2017-11-04 13:26 ` Jiri Olsa
[not found] ` <20171106114943.mg6pwpqe6eqlx7w2@ukko.fi.intel.com>
2017-11-10 23:36 ` Megha Dey
2017-11-03 18:00 ` [PATCH V0 3/3] x86, bm: Add documentation on Intel Branch Monitoring Megha Dey
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=20171104132459.GA8454@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=grzegorz.andrejczuk@intel.com \
--cc=hpa@zytor.com \
--cc=kstewart@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kylehuey.com \
--cc=megha.dey@intel.com \
--cc=megha.dey@linux.intel.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.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.