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 V2 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support
Date: Mon, 20 Nov 2017 15:10:07 +0100 [thread overview]
Message-ID: <20171120141007.GB23281@krava> (raw)
In-Reply-To: <1510970046-25387-3-git-send-email-megha.dey@linux.intel.com>
On Fri, Nov 17, 2017 at 05:54:05PM -0800, Megha Dey wrote:
SNIP
> +/* Branch Monitoring default and mask values */
> +#define BM_MAX_WINDOW_SIZE 0x3ff
> +#define BM_MAX_THRESHOLD 0x7f
> +#define BM_MAX_EVENTS 6
> +#define BM_WINDOW_SIZE_SHIFT 8
> +#define BM_THRESHOLD_SHIFT 8
> +#define BM_EVENT_TYPE_SHIFT 1
> +#define BM_GUEST_DISABLE_SHIFT 3
> +#define BM_LBR_FREEZE_SHIFT 2
> +#define BM_WINDOW_CNT_SEL_SHIFT 24
> +#define BM_CNT_AND_MODE_SHIFT 26
> +#define BM_MISPRED_EVT_CNT_SHIFT 15
> +#define BM_ENABLE 0x3
> +#define BM_CNTR_ENABLE 1
> +
> +static unsigned int bm_window_size = BM_MAX_WINDOW_SIZE;
> +static unsigned int bm_guest_disable;
> +static unsigned int bm_lbr_freeze;
> +static unsigned int bm_window_cnt_sel;
> +static unsigned int bm_cnt_and_mode;
> +
> +static unsigned int bm_threshold = BM_MAX_THRESHOLD;
> +static unsigned int bm_mispred_evt_cnt;
> +
> +/* Branch monitoring counter owners */
> +static struct perf_event **bm_counter_owner;
that's still global.. 2 counters per system
jirka
next prev parent reply other threads:[~2017-11-20 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 1:54 [PATCH V2 0/3] perf/x86/intel: Add Branch Monitoring support Megha Dey
2017-11-18 1:54 ` [PATCH V2 1/3] x86/cpu/intel: Add Cannonlake to Intel family Megha Dey
2017-11-18 1:54 ` [PATCH V2 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support Megha Dey
2017-11-20 11:57 ` Peter Zijlstra
2017-12-12 21:10 ` Megha Dey
2017-12-12 22:32 ` Peter Zijlstra
2017-12-12 23:08 ` Megha Dey
2017-12-13 7:21 ` Peter Zijlstra
2017-12-20 21:23 ` Megha Dey
2018-04-04 21:33 ` Megha Dey
2017-11-20 14:10 ` Jiri Olsa [this message]
2017-12-12 21:03 ` Megha Dey
2017-11-18 1:54 ` [PATCH V2 3/3] x86, bm: Add documentation on Intel Branch Monitoring Megha Dey
2017-11-20 14:07 ` Jiri Olsa
2017-12-12 21:05 ` 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=20171120141007.GB23281@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox