- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
/*-
|
|
|
|
* Copyright (c) 2008 Joseph Koshy
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Intel Core, Core 2 and Atom PMCs.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <sys/cdefs.h>
|
|
|
|
__FBSDID("$FreeBSD$");
|
|
|
|
|
|
|
|
#include <sys/param.h>
|
2009-08-14 21:05:08 +00:00
|
|
|
#include <sys/bus.h>
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
#include <sys/pmc.h>
|
|
|
|
#include <sys/pmckern.h>
|
|
|
|
#include <sys/systm.h>
|
|
|
|
|
2009-08-14 21:05:08 +00:00
|
|
|
#include <machine/intr_machdep.h>
|
|
|
|
#include <machine/apicvar.h>
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
#include <machine/cpu.h>
|
|
|
|
#include <machine/cpufunc.h>
|
2011-12-12 13:12:55 +00:00
|
|
|
#include <machine/md_var.h>
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
#include <machine/specialreg.h>
|
|
|
|
|
|
|
|
#define CORE_CPUID_REQUEST 0xA
|
|
|
|
#define CORE_CPUID_REQUEST_SIZE 0x4
|
|
|
|
#define CORE_CPUID_EAX 0x0
|
|
|
|
#define CORE_CPUID_EBX 0x1
|
|
|
|
#define CORE_CPUID_ECX 0x2
|
|
|
|
#define CORE_CPUID_EDX 0x3
|
|
|
|
|
|
|
|
#define IAF_PMC_CAPS \
|
2012-05-02 16:23:36 +00:00
|
|
|
(PMC_CAP_READ | PMC_CAP_WRITE | PMC_CAP_INTERRUPT | \
|
|
|
|
PMC_CAP_USER | PMC_CAP_SYSTEM)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
#define IAF_RI_TO_MSR(RI) ((RI) + (1 << 30))
|
|
|
|
|
|
|
|
#define IAP_PMC_CAPS (PMC_CAP_INTERRUPT | PMC_CAP_USER | PMC_CAP_SYSTEM | \
|
|
|
|
PMC_CAP_EDGE | PMC_CAP_THRESHOLD | PMC_CAP_READ | PMC_CAP_WRITE | \
|
|
|
|
PMC_CAP_INVERT | PMC_CAP_QUALIFIER | PMC_CAP_PRECISE)
|
|
|
|
|
|
|
|
/*
|
|
|
|
* "Architectural" events defined by Intel. The values of these
|
|
|
|
* symbols correspond to positions in the bitmask returned by
|
|
|
|
* the CPUID.0AH instruction.
|
|
|
|
*/
|
|
|
|
enum core_arch_events {
|
|
|
|
CORE_AE_BRANCH_INSTRUCTION_RETIRED = 5,
|
|
|
|
CORE_AE_BRANCH_MISSES_RETIRED = 6,
|
|
|
|
CORE_AE_INSTRUCTION_RETIRED = 1,
|
|
|
|
CORE_AE_LLC_MISSES = 4,
|
|
|
|
CORE_AE_LLC_REFERENCE = 3,
|
|
|
|
CORE_AE_UNHALTED_REFERENCE_CYCLES = 2,
|
|
|
|
CORE_AE_UNHALTED_CORE_CYCLES = 0
|
|
|
|
};
|
|
|
|
|
|
|
|
static enum pmc_cputype core_cputype;
|
|
|
|
|
|
|
|
struct core_cpu {
|
|
|
|
volatile uint32_t pc_resync;
|
|
|
|
volatile uint32_t pc_iafctrl; /* Fixed function control. */
|
|
|
|
volatile uint64_t pc_globalctrl; /* Global control register. */
|
|
|
|
struct pmc_hw pc_corepmcs[];
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct core_cpu **core_pcpu;
|
|
|
|
|
|
|
|
static uint32_t core_architectural_events;
|
|
|
|
static uint64_t core_pmcmask;
|
|
|
|
|
|
|
|
static int core_iaf_ri; /* relative index of fixed counters */
|
|
|
|
static int core_iaf_width;
|
|
|
|
static int core_iaf_npmc;
|
|
|
|
|
|
|
|
static int core_iap_width;
|
|
|
|
static int core_iap_npmc;
|
|
|
|
|
|
|
|
static int
|
|
|
|
core_pcpu_noop(struct pmc_mdep *md, int cpu)
|
|
|
|
{
|
|
|
|
(void) md;
|
|
|
|
(void) cpu;
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
core_pcpu_init(struct pmc_mdep *md, int cpu)
|
|
|
|
{
|
|
|
|
struct pmc_cpu *pc;
|
|
|
|
struct core_cpu *cc;
|
|
|
|
struct pmc_hw *phw;
|
|
|
|
int core_ri, n, npmc;
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[iaf,%d] insane cpu number %d", __LINE__, cpu));
|
|
|
|
|
|
|
|
PMCDBG(MDP,INI,1,"core-init cpu=%d", cpu);
|
|
|
|
|
|
|
|
core_ri = md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAP].pcd_ri;
|
|
|
|
npmc = md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAP].pcd_num;
|
|
|
|
|
|
|
|
if (core_cputype != PMC_CPU_INTEL_CORE)
|
|
|
|
npmc += md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAF].pcd_num;
|
|
|
|
|
|
|
|
cc = malloc(sizeof(struct core_cpu) + npmc * sizeof(struct pmc_hw),
|
|
|
|
M_PMC, M_WAITOK | M_ZERO);
|
|
|
|
|
|
|
|
core_pcpu[cpu] = cc;
|
|
|
|
pc = pmc_pcpu[cpu];
|
|
|
|
|
|
|
|
KASSERT(pc != NULL && cc != NULL,
|
|
|
|
("[core,%d] NULL per-cpu structures cpu=%d", __LINE__, cpu));
|
|
|
|
|
|
|
|
for (n = 0, phw = cc->pc_corepmcs; n < npmc; n++, phw++) {
|
|
|
|
phw->phw_state = PMC_PHW_FLAG_IS_ENABLED |
|
|
|
|
PMC_PHW_CPU_TO_STATE(cpu) |
|
|
|
|
PMC_PHW_INDEX_TO_STATE(n + core_ri);
|
|
|
|
phw->phw_pmc = NULL;
|
|
|
|
pc->pc_hwpmcs[n + core_ri] = phw;
|
|
|
|
}
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
core_pcpu_fini(struct pmc_mdep *md, int cpu)
|
|
|
|
{
|
|
|
|
int core_ri, n, npmc;
|
|
|
|
struct pmc_cpu *pc;
|
|
|
|
struct core_cpu *cc;
|
2010-07-13 19:37:45 +00:00
|
|
|
uint64_t msr = 0;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] insane cpu number (%d)", __LINE__, cpu));
|
|
|
|
|
|
|
|
PMCDBG(MDP,INI,1,"core-pcpu-fini cpu=%d", cpu);
|
|
|
|
|
|
|
|
if ((cc = core_pcpu[cpu]) == NULL)
|
|
|
|
return (0);
|
|
|
|
|
|
|
|
core_pcpu[cpu] = NULL;
|
|
|
|
|
|
|
|
pc = pmc_pcpu[cpu];
|
|
|
|
|
|
|
|
KASSERT(pc != NULL, ("[core,%d] NULL per-cpu %d state", __LINE__,
|
|
|
|
cpu));
|
|
|
|
|
|
|
|
npmc = md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAP].pcd_num;
|
|
|
|
core_ri = md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAP].pcd_ri;
|
|
|
|
|
2010-07-13 19:37:45 +00:00
|
|
|
for (n = 0; n < npmc; n++) {
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IAP_EVSEL0 + n) & ~IAP_EVSEL_MASK;
|
|
|
|
wrmsr(IAP_EVSEL0 + n, msr);
|
2010-07-13 19:37:45 +00:00
|
|
|
}
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
if (core_cputype != PMC_CPU_INTEL_CORE) {
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IAF_CTRL) & ~IAF_CTRL_MASK;
|
|
|
|
wrmsr(IAF_CTRL, msr);
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
npmc += md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAF].pcd_num;
|
|
|
|
}
|
|
|
|
|
|
|
|
for (n = 0; n < npmc; n++)
|
|
|
|
pc->pc_hwpmcs[n + core_ri] = NULL;
|
|
|
|
|
|
|
|
free(cc, M_PMC);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Fixed function counters.
|
|
|
|
*/
|
|
|
|
|
|
|
|
static pmc_value_t
|
|
|
|
iaf_perfctr_value_to_reload_count(pmc_value_t v)
|
|
|
|
{
|
|
|
|
v &= (1ULL << core_iaf_width) - 1;
|
|
|
|
return (1ULL << core_iaf_width) - v;
|
|
|
|
}
|
|
|
|
|
|
|
|
static pmc_value_t
|
|
|
|
iaf_reload_count_to_perfctr_value(pmc_value_t rlc)
|
|
|
|
{
|
|
|
|
return (1ULL << core_iaf_width) - rlc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_allocate_pmc(int cpu, int ri, struct pmc *pm,
|
|
|
|
const struct pmc_op_pmcallocate *a)
|
|
|
|
{
|
|
|
|
enum pmc_event ev;
|
|
|
|
uint32_t caps, flags, validflags;
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU %d", __LINE__, cpu));
|
|
|
|
|
|
|
|
PMCDBG(MDP,ALL,1, "iaf-allocate ri=%d reqcaps=0x%x", ri, pm->pm_caps);
|
|
|
|
|
|
|
|
if (ri < 0 || ri > core_iaf_npmc)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
caps = a->pm_caps;
|
|
|
|
|
|
|
|
if (a->pm_class != PMC_CLASS_IAF ||
|
|
|
|
(caps & IAF_PMC_CAPS) != caps)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
ev = pm->pm_event;
|
|
|
|
if (ev < PMC_EV_IAF_FIRST || ev > PMC_EV_IAF_LAST)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
if (ev == PMC_EV_IAF_INSTR_RETIRED_ANY && ri != 0)
|
|
|
|
return (EINVAL);
|
|
|
|
if (ev == PMC_EV_IAF_CPU_CLK_UNHALTED_CORE && ri != 1)
|
|
|
|
return (EINVAL);
|
|
|
|
if (ev == PMC_EV_IAF_CPU_CLK_UNHALTED_REF && ri != 2)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
flags = a->pm_md.pm_iaf.pm_iaf_flags;
|
|
|
|
|
|
|
|
validflags = IAF_MASK;
|
|
|
|
|
|
|
|
if (core_cputype != PMC_CPU_INTEL_ATOM)
|
|
|
|
validflags &= ~IAF_ANY;
|
|
|
|
|
|
|
|
if ((flags & ~validflags) != 0)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
if (caps & PMC_CAP_INTERRUPT)
|
|
|
|
flags |= IAF_PMI;
|
|
|
|
if (caps & PMC_CAP_SYSTEM)
|
|
|
|
flags |= IAF_OS;
|
|
|
|
if (caps & PMC_CAP_USER)
|
|
|
|
flags |= IAF_USR;
|
|
|
|
if ((caps & (PMC_CAP_USER | PMC_CAP_SYSTEM)) == 0)
|
|
|
|
flags |= (IAF_OS | IAF_USR);
|
|
|
|
|
|
|
|
pm->pm_md.pm_iaf.pm_iaf_ctrl = (flags << (ri * 4));
|
|
|
|
|
|
|
|
PMCDBG(MDP,ALL,2, "iaf-allocate config=0x%jx",
|
|
|
|
(uintmax_t) pm->pm_md.pm_iaf.pm_iaf_ctrl);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_config_pmc(int cpu, int ri, struct pmc *pm)
|
|
|
|
{
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU %d", __LINE__, cpu));
|
|
|
|
|
|
|
|
KASSERT(ri >= 0 && ri < core_iaf_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
PMCDBG(MDP,CFG,1, "iaf-config cpu=%d ri=%d pm=%p", cpu, ri, pm);
|
|
|
|
|
|
|
|
KASSERT(core_pcpu[cpu] != NULL, ("[core,%d] null per-cpu %d", __LINE__,
|
|
|
|
cpu));
|
|
|
|
|
|
|
|
core_pcpu[cpu]->pc_corepmcs[ri + core_iaf_ri].phw_pmc = pm;
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_describe(int cpu, int ri, struct pmc_info *pi, struct pmc **ppmc)
|
|
|
|
{
|
|
|
|
int error;
|
|
|
|
struct pmc_hw *phw;
|
|
|
|
char iaf_name[PMC_NAME_MAX];
|
|
|
|
|
|
|
|
phw = &core_pcpu[cpu]->pc_corepmcs[ri + core_iaf_ri];
|
|
|
|
|
|
|
|
(void) snprintf(iaf_name, sizeof(iaf_name), "IAF-%d", ri);
|
|
|
|
if ((error = copystr(iaf_name, pi->pm_name, PMC_NAME_MAX,
|
|
|
|
NULL)) != 0)
|
|
|
|
return (error);
|
|
|
|
|
|
|
|
pi->pm_class = PMC_CLASS_IAF;
|
|
|
|
|
|
|
|
if (phw->phw_state & PMC_PHW_FLAG_IS_ENABLED) {
|
|
|
|
pi->pm_enabled = TRUE;
|
|
|
|
*ppmc = phw->phw_pmc;
|
|
|
|
} else {
|
|
|
|
pi->pm_enabled = FALSE;
|
|
|
|
*ppmc = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_get_config(int cpu, int ri, struct pmc **ppm)
|
|
|
|
{
|
|
|
|
*ppm = core_pcpu[cpu]->pc_corepmcs[ri + core_iaf_ri].phw_pmc;
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_get_msr(int ri, uint32_t *msr)
|
|
|
|
{
|
|
|
|
KASSERT(ri >= 0 && ri < core_iaf_npmc,
|
|
|
|
("[iaf,%d] ri %d out of range", __LINE__, ri));
|
|
|
|
|
|
|
|
*msr = IAF_RI_TO_MSR(ri);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_read_pmc(int cpu, int ri, pmc_value_t *v)
|
|
|
|
{
|
|
|
|
struct pmc *pm;
|
|
|
|
pmc_value_t tmp;
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal cpu value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iaf_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
pm = core_pcpu[cpu]->pc_corepmcs[ri + core_iaf_ri].phw_pmc;
|
|
|
|
|
|
|
|
KASSERT(pm,
|
|
|
|
("[core,%d] cpu %d ri %d(%d) pmc not configured", __LINE__, cpu,
|
|
|
|
ri, ri + core_iaf_ri));
|
|
|
|
|
|
|
|
tmp = rdpmc(IAF_RI_TO_MSR(ri));
|
|
|
|
|
|
|
|
if (PMC_IS_SAMPLING_MODE(PMC_TO_MODE(pm)))
|
|
|
|
*v = iaf_perfctr_value_to_reload_count(tmp);
|
|
|
|
else
|
|
|
|
*v = tmp;
|
|
|
|
|
|
|
|
PMCDBG(MDP,REA,1, "iaf-read cpu=%d ri=%d msr=0x%x -> v=%jx", cpu, ri,
|
|
|
|
IAF_RI_TO_MSR(ri), *v);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_release_pmc(int cpu, int ri, struct pmc *pmc)
|
|
|
|
{
|
|
|
|
PMCDBG(MDP,REL,1, "iaf-release cpu=%d ri=%d pm=%p", cpu, ri, pmc);
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iaf_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
KASSERT(core_pcpu[cpu]->pc_corepmcs[ri + core_iaf_ri].phw_pmc == NULL,
|
|
|
|
("[core,%d] PHW pmc non-NULL", __LINE__));
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_start_pmc(int cpu, int ri)
|
|
|
|
{
|
|
|
|
struct pmc *pm;
|
|
|
|
struct core_cpu *iafc;
|
2010-07-13 19:37:45 +00:00
|
|
|
uint64_t msr = 0;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iaf_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
PMCDBG(MDP,STA,1,"iaf-start cpu=%d ri=%d", cpu, ri);
|
|
|
|
|
|
|
|
iafc = core_pcpu[cpu];
|
|
|
|
pm = iafc->pc_corepmcs[ri + core_iaf_ri].phw_pmc;
|
|
|
|
|
|
|
|
iafc->pc_iafctrl |= pm->pm_md.pm_iaf.pm_iaf_ctrl;
|
|
|
|
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IAF_CTRL) & ~IAF_CTRL_MASK;
|
2010-07-13 19:37:45 +00:00
|
|
|
wrmsr(IAF_CTRL, msr | (iafc->pc_iafctrl & IAF_CTRL_MASK));
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
do {
|
|
|
|
iafc->pc_resync = 0;
|
|
|
|
iafc->pc_globalctrl |= (1ULL << (ri + IAF_OFFSET));
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IA_GLOBAL_CTRL) & ~IAF_GLOBAL_CTRL_MASK;
|
2010-07-13 19:37:45 +00:00
|
|
|
wrmsr(IA_GLOBAL_CTRL, msr | (iafc->pc_globalctrl &
|
|
|
|
IAF_GLOBAL_CTRL_MASK));
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
} while (iafc->pc_resync != 0);
|
|
|
|
|
|
|
|
PMCDBG(MDP,STA,1,"iafctrl=%x(%x) globalctrl=%jx(%jx)",
|
|
|
|
iafc->pc_iafctrl, (uint32_t) rdmsr(IAF_CTRL),
|
|
|
|
iafc->pc_globalctrl, rdmsr(IA_GLOBAL_CTRL));
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_stop_pmc(int cpu, int ri)
|
|
|
|
{
|
|
|
|
uint32_t fc;
|
|
|
|
struct core_cpu *iafc;
|
2010-07-13 19:37:45 +00:00
|
|
|
uint64_t msr = 0;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
PMCDBG(MDP,STO,1,"iaf-stop cpu=%d ri=%d", cpu, ri);
|
|
|
|
|
|
|
|
iafc = core_pcpu[cpu];
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iaf_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
fc = (IAF_MASK << (ri * 4));
|
|
|
|
|
|
|
|
if (core_cputype != PMC_CPU_INTEL_ATOM)
|
|
|
|
fc &= ~IAF_ANY;
|
|
|
|
|
|
|
|
iafc->pc_iafctrl &= ~fc;
|
|
|
|
|
|
|
|
PMCDBG(MDP,STO,1,"iaf-stop iafctrl=%x", iafc->pc_iafctrl);
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IAF_CTRL) & ~IAF_CTRL_MASK;
|
2010-07-13 19:37:45 +00:00
|
|
|
wrmsr(IAF_CTRL, msr | (iafc->pc_iafctrl & IAF_CTRL_MASK));
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
do {
|
|
|
|
iafc->pc_resync = 0;
|
|
|
|
iafc->pc_globalctrl &= ~(1ULL << (ri + IAF_OFFSET));
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IA_GLOBAL_CTRL) & ~IAF_GLOBAL_CTRL_MASK;
|
2010-07-13 19:37:45 +00:00
|
|
|
wrmsr(IA_GLOBAL_CTRL, msr | (iafc->pc_globalctrl &
|
|
|
|
IAF_GLOBAL_CTRL_MASK));
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
} while (iafc->pc_resync != 0);
|
|
|
|
|
|
|
|
PMCDBG(MDP,STO,1,"iafctrl=%x(%x) globalctrl=%jx(%jx)",
|
|
|
|
iafc->pc_iafctrl, (uint32_t) rdmsr(IAF_CTRL),
|
|
|
|
iafc->pc_globalctrl, rdmsr(IA_GLOBAL_CTRL));
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iaf_write_pmc(int cpu, int ri, pmc_value_t v)
|
|
|
|
{
|
|
|
|
struct core_cpu *cc;
|
|
|
|
struct pmc *pm;
|
2010-07-13 19:37:45 +00:00
|
|
|
uint64_t msr;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal cpu value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iaf_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
cc = core_pcpu[cpu];
|
|
|
|
pm = cc->pc_corepmcs[ri + core_iaf_ri].phw_pmc;
|
|
|
|
|
|
|
|
KASSERT(pm,
|
|
|
|
("[core,%d] cpu %d ri %d pmc not configured", __LINE__, cpu, ri));
|
|
|
|
|
|
|
|
if (PMC_IS_SAMPLING_MODE(PMC_TO_MODE(pm)))
|
|
|
|
v = iaf_reload_count_to_perfctr_value(v);
|
|
|
|
|
2010-07-29 17:52:23 +00:00
|
|
|
/* Turn off fixed counters */
|
|
|
|
msr = rdmsr(IAF_CTRL) & ~IAF_CTRL_MASK;
|
|
|
|
wrmsr(IAF_CTRL, msr);
|
|
|
|
|
2010-07-13 19:37:45 +00:00
|
|
|
wrmsr(IAF_CTR0 + ri, v & ((1ULL << core_iaf_width) - 1));
|
2010-07-29 17:52:23 +00:00
|
|
|
|
|
|
|
/* Turn on fixed counters */
|
|
|
|
msr = rdmsr(IAF_CTRL) & ~IAF_CTRL_MASK;
|
2010-07-13 19:37:45 +00:00
|
|
|
wrmsr(IAF_CTRL, msr | (cc->pc_iafctrl & IAF_CTRL_MASK));
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
PMCDBG(MDP,WRI,1, "iaf-write cpu=%d ri=%d msr=0x%x v=%jx iafctrl=%jx "
|
|
|
|
"pmc=%jx", cpu, ri, IAF_RI_TO_MSR(ri), v,
|
|
|
|
(uintmax_t) rdmsr(IAF_CTRL),
|
|
|
|
(uintmax_t) rdpmc(IAF_RI_TO_MSR(ri)));
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
iaf_initialize(struct pmc_mdep *md, int maxcpu, int npmc, int pmcwidth)
|
|
|
|
{
|
|
|
|
struct pmc_classdep *pcd;
|
|
|
|
|
|
|
|
KASSERT(md != NULL, ("[iaf,%d] md is NULL", __LINE__));
|
|
|
|
|
|
|
|
PMCDBG(MDP,INI,1, "%s", "iaf-initialize");
|
|
|
|
|
|
|
|
pcd = &md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAF];
|
|
|
|
|
|
|
|
pcd->pcd_caps = IAF_PMC_CAPS;
|
|
|
|
pcd->pcd_class = PMC_CLASS_IAF;
|
|
|
|
pcd->pcd_num = npmc;
|
|
|
|
pcd->pcd_ri = md->pmd_npmc;
|
|
|
|
pcd->pcd_width = pmcwidth;
|
|
|
|
|
|
|
|
pcd->pcd_allocate_pmc = iaf_allocate_pmc;
|
|
|
|
pcd->pcd_config_pmc = iaf_config_pmc;
|
|
|
|
pcd->pcd_describe = iaf_describe;
|
|
|
|
pcd->pcd_get_config = iaf_get_config;
|
|
|
|
pcd->pcd_get_msr = iaf_get_msr;
|
|
|
|
pcd->pcd_pcpu_fini = core_pcpu_noop;
|
|
|
|
pcd->pcd_pcpu_init = core_pcpu_noop;
|
|
|
|
pcd->pcd_read_pmc = iaf_read_pmc;
|
|
|
|
pcd->pcd_release_pmc = iaf_release_pmc;
|
|
|
|
pcd->pcd_start_pmc = iaf_start_pmc;
|
|
|
|
pcd->pcd_stop_pmc = iaf_stop_pmc;
|
|
|
|
pcd->pcd_write_pmc = iaf_write_pmc;
|
|
|
|
|
|
|
|
md->pmd_npmc += npmc;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Intel programmable PMCs.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Event descriptor tables.
|
|
|
|
*
|
|
|
|
* For each event id, we track:
|
|
|
|
*
|
|
|
|
* 1. The CPUs that the event is valid for.
|
|
|
|
*
|
|
|
|
* 2. If the event uses a fixed UMASK, the value of the umask field.
|
|
|
|
* If the event doesn't use a fixed UMASK, a mask of legal bits
|
|
|
|
* to check against.
|
|
|
|
*/
|
|
|
|
|
|
|
|
struct iap_event_descr {
|
|
|
|
enum pmc_event iap_ev;
|
|
|
|
unsigned char iap_evcode;
|
|
|
|
unsigned char iap_umask;
|
2012-09-06 13:54:01 +00:00
|
|
|
unsigned int iap_flags;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#define IAP_F_CC (1 << 0) /* CPU: Core */
|
2008-12-03 17:30:36 +00:00
|
|
|
#define IAP_F_CC2 (1 << 1) /* CPU: Core2 family */
|
|
|
|
#define IAP_F_CC2E (1 << 2) /* CPU: Core2 Extreme only */
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
#define IAP_F_CA (1 << 3) /* CPU: Atom */
|
2009-01-27 07:29:37 +00:00
|
|
|
#define IAP_F_I7 (1 << 4) /* CPU: Core i7 */
|
2010-04-02 13:23:49 +00:00
|
|
|
#define IAP_F_I7O (1 << 4) /* CPU: Core i7 (old) */
|
|
|
|
#define IAP_F_WM (1 << 5) /* CPU: Westmere */
|
2012-09-06 13:54:01 +00:00
|
|
|
#define IAP_F_SB (1 << 6) /* CPU: Sandy Bridge */
|
|
|
|
#define IAP_F_IB (1 << 7) /* CPU: Ivy Bridge */
|
2012-10-19 17:01:27 +00:00
|
|
|
#define IAP_F_SBX (1 << 8) /* CPU: Sandy Bridge Xeon */
|
2013-01-31 22:09:53 +00:00
|
|
|
#define IAP_F_IBX (1 << 9) /* CPU: Ivy Bridge */
|
|
|
|
#define IAP_F_FM (1 << 10) /* Fixed mask */
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
#define IAP_F_ALLCPUSCORE2 \
|
|
|
|
(IAP_F_CC | IAP_F_CC2 | IAP_F_CC2E | IAP_F_CA)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
/* Sub fields of UMASK that this event supports. */
|
|
|
|
#define IAP_M_CORE (1 << 0) /* Core specificity */
|
|
|
|
#define IAP_M_AGENT (1 << 1) /* Agent specificity */
|
|
|
|
#define IAP_M_PREFETCH (1 << 2) /* Prefetch */
|
|
|
|
#define IAP_M_MESI (1 << 3) /* MESI */
|
|
|
|
#define IAP_M_SNOOPRESPONSE (1 << 4) /* Snoop response */
|
|
|
|
#define IAP_M_SNOOPTYPE (1 << 5) /* Snoop type */
|
|
|
|
#define IAP_M_TRANSITION (1 << 6) /* Transition */
|
|
|
|
|
|
|
|
#define IAP_F_CORE (0x3 << 14) /* Core specificity */
|
|
|
|
#define IAP_F_AGENT (0x1 << 13) /* Agent specificity */
|
|
|
|
#define IAP_F_PREFETCH (0x3 << 12) /* Prefetch */
|
|
|
|
#define IAP_F_MESI (0xF << 8) /* MESI */
|
|
|
|
#define IAP_F_SNOOPRESPONSE (0xB << 8) /* Snoop response */
|
|
|
|
#define IAP_F_SNOOPTYPE (0x3 << 8) /* Snoop type */
|
|
|
|
#define IAP_F_TRANSITION (0x1 << 12) /* Transition */
|
|
|
|
|
|
|
|
#define IAP_PREFETCH_RESERVED (0x2 << 12)
|
|
|
|
#define IAP_CORE_THIS (0x1 << 14)
|
|
|
|
#define IAP_CORE_ALL (0x3 << 14)
|
|
|
|
#define IAP_F_CMASK 0xFF000000
|
|
|
|
|
|
|
|
static struct iap_event_descr iap_events[] = {
|
|
|
|
#undef IAPDESCR
|
|
|
|
#define IAPDESCR(N,EV,UM,FLAGS) { \
|
|
|
|
.iap_ev = PMC_EV_IAP_EVENT_##N, \
|
|
|
|
.iap_evcode = (EV), \
|
|
|
|
.iap_umask = (UM), \
|
|
|
|
.iap_flags = (FLAGS) \
|
|
|
|
}
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(02H_01H, 0x02, 0x01, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(02H_81H, 0x02, 0x81, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
|
|
|
IAPDESCR(03H_00H, 0x03, 0x00, IAP_F_FM | IAP_F_CC),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(03H_01H, 0x03, 0x01, IAP_F_FM | IAP_F_I7O | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(03H_02H, 0x03, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(03H_04H, 0x03, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 | IAP_F_I7O),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(03H_08H, 0x03, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2 | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
|
|
|
IAPDESCR(03H_10H, 0x03, 0x10, IAP_F_FM | IAP_F_CA | IAP_F_CC2 | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(03H_20H, 0x03, 0x20, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(04H_00H, 0x04, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(04H_01H, 0x04, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(04H_02H, 0x04, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(04H_07H, 0x04, 0x07, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(04H_08H, 0x04, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(05H_00H, 0x05, 0x00, IAP_F_FM | IAP_F_CC),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(05H_01H, 0x05, 0x01, IAP_F_FM | IAP_F_I7O | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(05H_02H, 0x05, 0x02, IAP_F_FM | IAP_F_I7O | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(05H_03H, 0x05, 0x03, IAP_F_FM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(06H_00H, 0x06, 0x00, IAP_F_FM | IAP_F_CC | IAP_F_CC2 |
|
|
|
|
IAP_F_CC2E | IAP_F_CA),
|
|
|
|
IAPDESCR(06H_01H, 0x06, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(06H_02H, 0x06, 0x02, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(06H_04H, 0x06, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(06H_08H, 0x06, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(06H_0FH, 0x06, 0x0F, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(07H_00H, 0x07, 0x00, IAP_F_FM | IAP_F_CC | IAP_F_CC2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(07H_01H, 0x07, 0x01, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(07H_02H, 0x07, 0x02, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(07H_03H, 0x07, 0x03, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(07H_06H, 0x07, 0x06, IAP_F_FM | IAP_F_CA),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(07H_08H, 0x07, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(08H_01H, 0x08, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(08H_02H, 0x08, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(08H_04H, 0x08, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_WM | IAP_F_SB | IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(08H_05H, 0x08, 0x05, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(08H_06H, 0x08, 0x06, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(08H_07H, 0x08, 0x07, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(08H_08H, 0x08, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(08H_09H, 0x08, 0x09, IAP_F_FM | IAP_F_CA),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(08H_10H, 0x08, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(08H_20H, 0x08, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-01-04 07:58:36 +00:00
|
|
|
IAPDESCR(08H_40H, 0x08, 0x40, IAP_F_FM | IAP_F_I7O),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(08H_80H, 0x08, 0x80, IAP_F_FM | IAP_F_I7),
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(08H_81H, 0x08, 0x81, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(08H_82H, 0x08, 0x82, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(08H_84H, 0x08, 0x84, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(09H_01H, 0x09, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 | IAP_F_I7O),
|
|
|
|
IAPDESCR(09H_02H, 0x09, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 | IAP_F_I7O),
|
|
|
|
IAPDESCR(09H_04H, 0x09, 0x04, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(09H_08H, 0x09, 0x08, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(0BH_01H, 0x0B, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(0BH_02H, 0x0B, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(0BH_10H, 0x0B, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(0CH_01H, 0x0C, 0x01, IAP_F_FM | IAP_F_CC2 | IAP_F_I7 |
|
|
|
|
IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(0CH_02H, 0x0C, 0x02, IAP_F_FM | IAP_F_CC2),
|
|
|
|
IAPDESCR(0CH_03H, 0x0C, 0x03, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(0DH_03H, 0x0D, 0x03, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(0DH_40H, 0x0D, 0x40, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(0EH_01H, 0x0E, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(0EH_02H, 0x0E, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(0EH_10H, 0x0E, 0x10, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(0EH_20H, 0x0E, 0x20, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(0EH_40H, 0x0E, 0x40, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(0FH_01H, 0x0F, 0x01, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(0FH_02H, 0x0F, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(0FH_08H, 0x0F, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(0FH_10H, 0x0F, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(0FH_20H, 0x0F, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(0FH_80H, 0x0F, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(10H_00H, 0x10, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(10H_01H, 0x10, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_I7 |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_WM | IAP_F_SB | IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(10H_02H, 0x10, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(10H_04H, 0x10, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(10H_08H, 0x10, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(10H_10H, 0x10, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
|
|
|
IAPDESCR(10H_20H, 0x10, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
|
|
|
IAPDESCR(10H_40H, 0x10, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
|
|
|
IAPDESCR(10H_80H, 0x10, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(10H_81H, 0x10, 0x81, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
|
|
|
IAPDESCR(11H_00H, 0x11, 0x00, IAP_F_FM | IAP_F_CC | IAP_F_CC2),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(11H_01H, 0x11, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
|
|
|
IAPDESCR(11H_02H, 0x11, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(11H_81H, 0x11, 0x81, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(12H_00H, 0x12, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(12H_01H, 0x12, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(12H_02H, 0x12, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(12H_04H, 0x12, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(12H_08H, 0x12, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(12H_10H, 0x12, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(12H_20H, 0x12, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(12H_40H, 0x12, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(12H_81H, 0x12, 0x81, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(13H_00H, 0x13, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(13H_01H, 0x13, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(13H_02H, 0x13, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(13H_04H, 0x13, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(13H_07H, 0x13, 0x07, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(13H_81H, 0x13, 0x81, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
|
|
|
IAPDESCR(14H_00H, 0x14, 0x00, IAP_F_FM | IAP_F_CC | IAP_F_CC2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(14H_01H, 0x14, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_I7 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(14H_02H, 0x14, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(17H_01H, 0x17, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(18H_00H, 0x18, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(18H_01H, 0x18, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(19H_00H, 0x19, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(19H_01H, 0x19, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(19H_02H, 0x19, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(1DH_01H, 0x1D, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(1DH_02H, 0x1D, 0x02, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(1DH_04H, 0x1D, 0x04, IAP_F_FM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(1EH_01H, 0x1E, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(20H_01H, 0x20, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(21H, 0x21, IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(22H, 0x22, IAP_M_CORE, IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(23H, 0x23, IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
|
|
|
|
|
|
|
IAPDESCR(24H, 0x24, IAP_M_CORE | IAP_M_PREFETCH, IAP_F_ALLCPUSCORE2),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_01H, 0x24, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(24H_02H, 0x24, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_03H, 0x24, 0x03, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_04H, 0x24, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_08H, 0x24, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_0CH, 0x24, 0x0C, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_10H, 0x24, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_20H, 0x24, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_30H, 0x24, 0x30, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_40H, 0x24, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_80H, 0x24, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(24H_C0H, 0x24, 0xC0, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(24H_AAH, 0x24, 0xAA, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(24H_FFH, 0x24, 0xFF, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(25H, 0x25, IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
|
|
|
|
|
|
|
IAPDESCR(26H, 0x26, IAP_M_CORE | IAP_M_PREFETCH, IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(26H_01H, 0x26, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_02H, 0x26, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_04H, 0x26, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_08H, 0x26, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_0FH, 0x26, 0x0F, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_10H, 0x26, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_20H, 0x26, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_40H, 0x26, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_80H, 0x26, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_F0H, 0x26, 0xF0, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(26H_FFH, 0x26, 0xFF, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(27H, 0x27, IAP_M_CORE | IAP_M_PREFETCH, IAP_F_ALLCPUSCORE2),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(27H_01H, 0x27, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(27H_02H, 0x27, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(27H_04H, 0x27, 0x04, IAP_F_FM | IAP_F_I7O | IAP_F_SB |
|
|
|
|
IAP_F_SBX),
|
|
|
|
IAPDESCR(27H_08H, 0x27, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(27H_0EH, 0x27, 0x0E, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(27H_0FH, 0x27, 0x0F, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(27H_10H, 0x27, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(27H_20H, 0x27, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(27H_40H, 0x27, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(27H_80H, 0x27, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(27H_E0H, 0x27, 0xE0, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(27H_F0H, 0x27, 0xF0, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(28H, 0x28, IAP_M_CORE | IAP_M_MESI, IAP_F_ALLCPUSCORE2),
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(28H_01H, 0x28, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(28H_02H, 0x28, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SBX),
|
|
|
|
IAPDESCR(28H_04H, 0x28, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(28H_08H, 0x28, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(28H_0FH, 0x28, 0x0F, IAP_F_FM | IAP_F_I7 | IAP_F_WM | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(29H, 0x29, IAP_M_CORE | IAP_M_MESI, IAP_F_CC),
|
|
|
|
IAPDESCR(29H, 0x29, IAP_M_CORE | IAP_M_MESI | IAP_M_PREFETCH,
|
|
|
|
IAP_F_CA | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(2AH, 0x2A, IAP_M_CORE | IAP_M_MESI, IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(2BH, 0x2B, IAP_M_CORE | IAP_M_MESI, IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(2EH, 0x2E, IAP_M_CORE | IAP_M_MESI | IAP_M_PREFETCH,
|
2010-04-02 13:23:49 +00:00
|
|
|
IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(2EH_01H, 0x2E, 0x01, IAP_F_FM | IAP_F_WM),
|
|
|
|
IAPDESCR(2EH_02H, 0x2E, 0x02, IAP_F_FM | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(2EH_41H, 0x2E, 0x41, IAP_F_FM | IAP_F_ALLCPUSCORE2 | IAP_F_I7 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(2EH_4FH, 0x2E, 0x4F, IAP_F_FM | IAP_F_ALLCPUSCORE2 | IAP_F_I7 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(30H, 0x30, IAP_M_CORE | IAP_M_MESI | IAP_M_PREFETCH,
|
2010-04-02 13:23:49 +00:00
|
|
|
IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(32H, 0x32, IAP_M_CORE | IAP_M_MESI | IAP_M_PREFETCH, IAP_F_CC),
|
|
|
|
IAPDESCR(32H, 0x32, IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(3AH, 0x3A, IAP_M_TRANSITION, IAP_F_CC),
|
|
|
|
IAPDESCR(3AH_00H, 0x3A, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(3BH_C0H, 0x3B, 0xC0, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(3CH_00H, 0x3C, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(3CH_01H, 0x3C, 0x01, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(3CH_02H, 0x3C, 0x02, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
|
|
|
|
IAPDESCR(3DH_01H, 0x3D, 0x01, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
IAPDESCR(40H, 0x40, IAP_M_MESI, IAP_F_CC | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(40H_01H, 0x40, 0x01, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(40H_02H, 0x40, 0x02, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(40H_04H, 0x40, 0x04, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(40H_08H, 0x40, 0x08, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(40H_0FH, 0x40, 0x0F, IAP_F_FM | IAP_F_I7),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(40H_21H, 0x40, 0x21, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
|
|
|
IAPDESCR(41H, 0x41, IAP_M_MESI, IAP_F_CC | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(41H_01H, 0x41, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(41H_02H, 0x41, 0x02, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(41H_04H, 0x41, 0x04, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(41H_08H, 0x41, 0x08, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(41H_0FH, 0x41, 0x0F, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(41H_22H, 0x41, 0x22, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(42H, 0x42, IAP_M_MESI, IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(42H_01H, 0x42, 0x01, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(42H_02H, 0x42, 0x02, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(42H_04H, 0x42, 0x04, IAP_F_FM | IAP_F_I7),
|
|
|
|
IAPDESCR(42H_08H, 0x42, 0x08, IAP_F_FM | IAP_F_I7),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(42H_10H, 0x42, 0x10, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(43H_01H, 0x43, 0x01, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
|
|
|
IAP_F_I7),
|
|
|
|
IAPDESCR(43H_02H, 0x43, 0x02, IAP_F_FM | IAP_F_CA |
|
|
|
|
IAP_F_CC2 | IAP_F_I7),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(44H_02H, 0x44, 0x02, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(45H_0FH, 0x45, 0x0F, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(46H_00H, 0x46, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(47H_00H, 0x47, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(48H_00H, 0x48, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(48H_01H, 0x48, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-01-04 07:58:36 +00:00
|
|
|
IAPDESCR(48H_02H, 0x48, 0x02, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(49H_00H, 0x49, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(49H_01H, 0x49, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(49H_02H, 0x49, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(49H_04H, 0x49, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(49H_10H, 0x49, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-01-04 07:58:36 +00:00
|
|
|
IAPDESCR(49H_20H, 0x49, 0x20, IAP_F_FM | IAP_F_I7),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(49H_40H, 0x49, 0x40, IAP_F_FM | IAP_F_I7O),
|
2012-01-04 07:58:36 +00:00
|
|
|
IAPDESCR(49H_80H, 0x49, 0x80, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(4BH_00H, 0x4B, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(4BH_01H, 0x4B, 0x01, IAP_F_FM | IAP_F_ALLCPUSCORE2 | IAP_F_I7O),
|
|
|
|
IAPDESCR(4BH_02H, 0x4B, 0x02, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(4BH_03H, 0x4B, 0x03, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(4BH_08H, 0x4B, 0x08, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(4CH_00H, 0x4C, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(4CH_01H, 0x4C, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(4CH_02H, 0x4C, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(4DH_01H, 0x4D, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(4EH_01H, 0x4E, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(4EH_02H, 0x4E, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(4EH_04H, 0x4E, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(4EH_10H, 0x4E, 0x10, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(4FH_00H, 0x4F, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(4FH_02H, 0x4F, 0x02, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(4FH_04H, 0x4F, 0x04, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(4FH_08H, 0x4F, 0x08, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(4FH_10H, 0x4F, 0x10, IAP_F_FM | IAP_F_WM),
|
|
|
|
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(51H_01H, 0x51, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(51H_02H, 0x51, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(51H_04H, 0x51, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(51H_08H, 0x51, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(52H_01H, 0x52, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(53H_01H, 0x53, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(58H_01H, 0x58, 0x01, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(58H_02H, 0x58, 0x02, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(58H_04H, 0x58, 0x04, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(58H_08H, 0x58, 0x08, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
2012-09-06 13:54:01 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(59H_20H, 0x59, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(59H_40H, 0x59, 0x40, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(59H_80H, 0x59, 0x80, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(5BH_0CH, 0x5B, 0x0C, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(5BH_0FH, 0x5B, 0x0F, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(5BH_40H, 0x5B, 0x40, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(5BH_4FH, 0x5B, 0x4F, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(5CH_01H, 0x5C, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(5CH_02H, 0x5C, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(5EH_01H, 0x5E, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-09-06 13:54:01 +00:00
|
|
|
|
|
|
|
IAPDESCR(5FH_01H, 0x5F, 0x01, IAP_F_FM | IAP_F_IB),
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(5FH_04H, 0x5F, 0x04, IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(60H, 0x60, IAP_M_AGENT | IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(60H_01H, 0x60, 0x01, IAP_F_FM | IAP_F_WM | IAP_F_I7O |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(60H_02H, 0x60, 0x02, IAP_F_FM | IAP_F_WM | IAP_F_I7O | IAP_F_IB |
|
|
|
|
IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(60H_04H, 0x60, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_I7O |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(60H_08H, 0x60, 0x08, IAP_F_FM | IAP_F_WM | IAP_F_I7O |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(61H, 0x61, IAP_M_AGENT, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(61H_00H, 0x61, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(62H, 0x62, IAP_M_AGENT, IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(62H_00H, 0x62, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(63H, 0x63, IAP_M_AGENT | IAP_M_CORE,
|
|
|
|
IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(63H, 0x63, IAP_M_CORE, IAP_F_CC),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(63H_01H, 0x63, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(63H_02H, 0x63, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(64H, 0x64, IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(64H_40H, 0x64, 0x40, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(65H, 0x65, IAP_M_AGENT | IAP_M_CORE,
|
|
|
|
IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(65H, 0x65, IAP_M_CORE, IAP_F_CC),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(66H, 0x66, IAP_M_AGENT | IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(67H, 0x67, IAP_M_AGENT | IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(67H, 0x67, IAP_M_AGENT, IAP_F_CC),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(68H, 0x68, IAP_M_AGENT | IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(69H, 0x69, IAP_M_AGENT | IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(6AH, 0x6A, IAP_M_AGENT | IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(6BH, 0x6B, IAP_M_AGENT | IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
|
|
|
|
|
|
|
IAPDESCR(6CH, 0x6C, IAP_M_AGENT | IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(6CH_01H, 0x6C, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(6DH, 0x6D, IAP_M_AGENT | IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(6DH, 0x6D, IAP_M_CORE, IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(6EH, 0x6E, IAP_M_AGENT | IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(6EH, 0x6E, IAP_M_CORE, IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(6FH, 0x6F, IAP_M_AGENT | IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(6FH, 0x6F, IAP_M_CORE, IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(70H, 0x70, IAP_M_AGENT | IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(70H, 0x70, IAP_M_CORE, IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(77H, 0x77, IAP_M_AGENT | IAP_M_SNOOPRESPONSE,
|
|
|
|
IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(77H, 0x77, IAP_M_AGENT | IAP_M_MESI, IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(78H, 0x78, IAP_M_CORE, IAP_F_CC),
|
|
|
|
IAPDESCR(78H, 0x78, IAP_M_CORE | IAP_M_SNOOPTYPE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(79H_02H, 0x79, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(79H_04H, 0x79, 0x04, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(79H_08H, 0x79, 0x08, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(79H_10H, 0x79, 0x10, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(79H_20H, 0x79, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(79H_30H, 0x79, 0x30, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(79H_18H, 0x79, 0x18, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(79H_24H, 0x79, 0x24, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
|
|
|
IAPDESCR(79H_3CH, 0x79, 0x3C, IAP_F_FM | IAP_F_IB | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(7AH, 0x7A, IAP_M_AGENT, IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(7BH, 0x7B, IAP_M_AGENT, IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(7DH, 0x7D, IAP_M_CORE, IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(7EH, 0x7E, IAP_M_AGENT | IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(7EH_00H, 0x7E, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(7FH, 0x7F, IAP_M_CORE, IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(80H_00H, 0x80, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(80H_01H, 0x80, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(80H_02H, 0x80, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_I7 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(80H_03H, 0x80, 0x03, IAP_F_FM | IAP_F_CA | IAP_F_I7 |
|
|
|
|
IAP_F_WM),
|
|
|
|
IAPDESCR(80H_04H, 0x80, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(81H_00H, 0x81, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(81H_01H, 0x81, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(81H_02H, 0x81, 0x02, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(82H_01H, 0x82, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(82H_02H, 0x82, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(82H_04H, 0x82, 0x04, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(82H_10H, 0x82, 0x10, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(82H_12H, 0x82, 0x12, IAP_F_FM | IAP_F_CC2),
|
|
|
|
IAPDESCR(82H_40H, 0x82, 0x40, IAP_F_FM | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(83H_01H, 0x83, 0x01, IAP_F_FM | IAP_F_I7O),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(83H_02H, 0x83, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(85H_00H, 0x85, 0x00, IAP_F_FM | IAP_F_CC),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(85H_01H, 0x85, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(85H_02H, 0x85, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(85H_04H, 0x85, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_I7O |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(85H_10H, 0x85, 0x10, IAP_F_FM | IAP_F_I7O | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(85H_20H, 0x85, 0x20, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(85H_40H, 0x85, 0x40, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(85H_80H, 0x85, 0x80, IAP_F_FM | IAP_F_WM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(86H_00H, 0x86, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
|
|
|
|
IAPDESCR(87H_00H, 0x87, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(87H_01H, 0x87, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(87H_02H, 0x87, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(87H_04H, 0x87, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(87H_08H, 0x87, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(87H_0FH, 0x87, 0x0F, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(88H_00H, 0x88, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(88H_01H, 0x88, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(88H_02H, 0x88, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(88H_04H, 0x88, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(88H_07H, 0x88, 0x07, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(88H_08H, 0x88, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(88H_10H, 0x88, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(88H_20H, 0x88, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(88H_30H, 0x88, 0x30, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(88H_40H, 0x88, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(88H_7FH, 0x88, 0x7F, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(88H_80H, 0x88, 0x80, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(88H_FFH, 0x88, 0xFF, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(89H_00H, 0x89, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(89H_01H, 0x89, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(89H_02H, 0x89, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(89H_04H, 0x89, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(89H_07H, 0x89, 0x07, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(89H_08H, 0x89, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(89H_10H, 0x89, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(89H_20H, 0x89, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(89H_30H, 0x89, 0x30, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(89H_40H, 0x89, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(89H_7FH, 0x89, 0x7F, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(89H_80H, 0x89, 0x80, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(89H_FFH, 0x89, 0xFF, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(8AH_00H, 0x8A, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(8BH_00H, 0x8B, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(8CH_00H, 0x8C, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(8DH_00H, 0x8D, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(8EH_00H, 0x8E, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(8FH_00H, 0x8F, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
|
|
|
|
IAPDESCR(90H_00H, 0x90, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(91H_00H, 0x91, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(92H_00H, 0x92, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(93H_00H, 0x93, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(94H_00H, 0x94, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(9CH_01H, 0x9C, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(97H_00H, 0x97, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(98H_00H, 0x98, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(A0H_00H, 0xA0, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A1H_01H, 0xA1, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A1H_02H, 0xA1, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A1H_04H, 0xA1, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A1H_08H, 0xA1, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(A1H_0CH, 0xA1, 0x0C, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A1H_10H, 0xA1, 0x10, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A1H_20H, 0xA1, 0x20, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(A1H_30H, 0xA1, 0x30, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(A1H_40H, 0xA1, 0x40, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(A1H_80H, 0xA1, 0x80, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(A2H_00H, 0xA2, 0x00, IAP_F_FM | IAP_F_CC),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_01H, 0xA2, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_02H, 0xA2, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_04H, 0xA2, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_08H, 0xA2, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_10H, 0xA2, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_20H, 0xA2, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_40H, 0xA2, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(A2H_80H, 0xA2, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
|
|
|
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(A3H_01H, 0xA3, 0x01, IAP_F_FM | IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(A3H_02H, 0xA3, 0x02, IAP_F_FM | IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(A3H_04H, 0xA3, 0x04, IAP_F_FM | IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(A3H_08H, 0xA3, 0x08, IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(A6H_01H, 0xA6, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(A7H_01H, 0xA7, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(A8H_01H, 0xA8, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(AAH_01H, 0xAA, 0x01, IAP_F_FM | IAP_F_CC2),
|
|
|
|
IAPDESCR(AAH_02H, 0xAA, 0x02, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(AAH_03H, 0xAA, 0x03, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(AAH_08H, 0xAA, 0x08, IAP_F_FM | IAP_F_CC2),
|
|
|
|
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(ABH_01H, 0xAB, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(ABH_02H, 0xAB, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(ACH_02H, 0xAC, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(ACH_08H, 0xAC, 0x08, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(ACH_0AH, 0xAC, 0x0A, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(AEH_01H, 0xAE, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(B0H_00H, 0xB0, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(B0H_01H, 0xB0, 0x01, IAP_F_FM | IAP_F_WM | IAP_F_I7O |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(B0H_02H, 0xB0, 0x02, IAP_F_FM | IAP_F_WM | IAP_F_I7O | IAP_F_IB |
|
|
|
|
IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(B0H_04H, 0xB0, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_I7O |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(B0H_08H, 0xB0, 0x08, IAP_F_FM | IAP_F_WM | IAP_F_I7O |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-15 19:45:03 +00:00
|
|
|
IAPDESCR(B0H_10H, 0xB0, 0x10, IAP_F_FM | IAP_F_WM | IAP_F_I7O),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(B0H_20H, 0xB0, 0x20, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(B0H_40H, 0xB0, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B0H_80H, 0xB0, 0x80, IAP_F_FM | IAP_F_CA | IAP_F_WM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(B1H_00H, 0xB1, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(B1H_01H, 0xB1, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(B1H_02H, 0xB1, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(B1H_04H, 0xB1, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B1H_08H, 0xB1, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B1H_10H, 0xB1, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B1H_1FH, 0xB1, 0x1F, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B1H_20H, 0xB1, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B1H_3FH, 0xB1, 0x3F, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B1H_40H, 0xB1, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B1H_80H, 0xB1, 0x80, IAP_F_FM | IAP_F_CA | IAP_F_I7 |
|
|
|
|
IAP_F_WM),
|
|
|
|
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(B2H_01H, 0xB2, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(B3H_01H, 0xB3, 0x01, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
|
|
|
IAP_F_WM | IAP_F_I7O),
|
|
|
|
IAPDESCR(B3H_02H, 0xB3, 0x02, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
|
|
|
IAP_F_WM | IAP_F_I7O),
|
|
|
|
IAPDESCR(B3H_04H, 0xB3, 0x04, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
|
|
|
IAP_F_WM | IAP_F_I7O),
|
|
|
|
IAPDESCR(B3H_08H, 0xB3, 0x08, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(B3H_10H, 0xB3, 0x10, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(B3H_20H, 0xB3, 0x20, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(B3H_81H, 0xB3, 0x81, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(B3H_82H, 0xB3, 0x82, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(B3H_84H, 0xB3, 0x84, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(B3H_88H, 0xB3, 0x88, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(B3H_90H, 0xB3, 0x90, IAP_F_FM | IAP_F_CA),
|
|
|
|
IAPDESCR(B3H_A0H, 0xB3, 0xA0, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(B4H_01H, 0xB4, 0x01, IAP_F_FM | IAP_F_WM),
|
|
|
|
IAPDESCR(B4H_02H, 0xB4, 0x02, IAP_F_FM | IAP_F_WM),
|
|
|
|
IAPDESCR(B4H_04H, 0xB4, 0x04, IAP_F_FM | IAP_F_WM),
|
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(B6H_01H, 0xB6, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
|
|
|
IAPDESCR(B7H_01H, 0xB7, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(B8H_01H, 0xB8, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B8H_02H, 0xB8, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(B8H_04H, 0xB8, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(BAH_01H, 0xBA, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(BAH_02H, 0xBA, 0x02, IAP_F_FM | IAP_F_I7O),
|
|
|
|
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(BBH_01H, 0xBB, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(BDH_01H, 0xBD, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(BDH_20H, 0xBD, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(BFH_05H, 0xBF, 0x05, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
|
|
|
IAPDESCR(C0H_00H, 0xC0, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C0H_01H, 0xC0, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C0H_02H, 0xC0, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2012-03-01 21:23:26 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C0H_04H, 0xC0, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(C0H_08H, 0xC0, 0x08, IAP_F_FM | IAP_F_CC2E),
|
|
|
|
|
|
|
|
IAPDESCR(C1H_00H, 0xC1, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(C1H_01H, 0xC1, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C1H_02H, 0xC1, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_SBX),
|
|
|
|
IAPDESCR(C1H_08H, 0xC1, 0x08, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C1H_10H, 0xC1, 0x10, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C1H_20H, 0xC1, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(C1H_FEH, 0xC1, 0xFE, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(C2H_00H, 0xC2, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C2H_01H, 0xC2, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C2H_02H, 0xC2, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C2H_04H, 0xC2, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(C2H_07H, 0xC2, 0x07, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(C2H_08H, 0xC2, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(C2H_0FH, 0xC2, 0x0F, IAP_F_FM | IAP_F_CC2),
|
|
|
|
IAPDESCR(C2H_10H, 0xC2, 0x10, IAP_F_FM | IAP_F_CA),
|
|
|
|
|
|
|
|
IAPDESCR(C3H_00H, 0xC3, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C3H_01H, 0xC3, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(C3H_02H, 0xC3, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C3H_04H, 0xC3, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C3H_10H, 0xC3, 0x10, IAP_F_FM | IAP_F_I7O),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C3H_20H, 0xC3, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(C4H_00H, 0xC4, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C4H_01H, 0xC4, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C4H_02H, 0xC4, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C4H_04H, 0xC4, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(C4H_08H, 0xC4, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(C4H_0CH, 0xC4, 0x0C, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(C4H_0FH, 0xC4, 0x0F, IAP_F_FM | IAP_F_CA),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C4H_10H, 0xC4, 0x10, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C4H_20H, 0xC4, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C4H_40H, 0xC4, 0x40, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C5H_00H, 0xC5, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C5H_01H, 0xC5, 0x01, IAP_F_FM | IAP_F_WM | IAP_F_SB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(C5H_02H, 0xC5, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C5H_04H, 0xC5, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_SB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C5H_10H, 0xC5, 0x10, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(C5H_20H, 0xC5, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(C6H_00H, 0xC6, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(C6H_01H, 0xC6, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(C6H_02H, 0xC6, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(C7H_00H, 0xC7, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C7H_01H, 0xC7, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(C7H_02H, 0xC7, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(C7H_04H, 0xC7, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(C7H_08H, 0xC7, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(C7H_10H, 0xC7, 0x10, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(C7H_1FH, 0xC7, 0x1F, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C8H_00H, 0xC8, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(C8H_20H, 0xC8, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(C9H_00H, 0xC9, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(CAH_00H, 0xCA, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(CAH_01H, 0xCA, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(CAH_02H, 0xCA, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(CAH_04H, 0xCA, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(CAH_08H, 0xCA, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(CAH_10H, 0xCA, 0x10, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(CAH_1EH, 0xCA, 0x1E, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(CBH_01H, 0xCB, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(CBH_02H, 0xCB, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(CBH_04H, 0xCB, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(CBH_08H, 0xCB, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(CBH_10H, 0xCB, 0x10, IAP_F_FM | IAP_F_CC2 | IAP_F_I7 |
|
|
|
|
IAP_F_WM),
|
|
|
|
IAPDESCR(CBH_40H, 0xCB, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(CBH_80H, 0xCB, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(CCH_00H, 0xCC, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(CCH_01H, 0xCC, 0x01, IAP_F_FM | IAP_F_ALLCPUSCORE2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(CCH_02H, 0xCC, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(CCH_03H, 0xCC, 0x03, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(CCH_20H, 0xCC, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(CDH_00H, 0xCD, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(CDH_01H, 0xCD, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(CDH_02H, 0xCD, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(CEH_00H, 0xCE, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(CFH_00H, 0xCF, 0x00, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(D0H_00H, 0xD0, 0x00, IAP_F_FM | IAP_F_CC),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(D0H_01H, 0xD0, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(D0H_02H, 0xD0, 0x02, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(D0H_10H, 0xD0, 0x10, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(D0H_20H, 0xD0, 0x20, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(D0H_40H, 0xD0, 0x40, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(D0H_80H, 0xD0, 0X80, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(D1H_01H, 0xD1, 0x01, IAP_F_FM | IAP_F_WM | IAP_F_SB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(D1H_02H, 0xD1, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(D1H_04H, 0xD1, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(D1H_08H, 0xD1, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(D1H_20H, 0xD1, 0x20, IAP_F_FM | IAP_F_SBX | IAP_F_IBX),
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(D1H_40H, 0xD1, 0x40, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(D2H_01H, 0xD2, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(D2H_02H, 0xD2, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(D2H_04H, 0xD2, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(D2H_08H, 0xD2, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_I7 | IAP_F_WM | IAP_F_SB | IAP_F_IB | IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(D2H_0FH, 0xD2, 0x0F, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(D2H_10H, 0xD2, 0x10, IAP_F_FM | IAP_F_CC2E),
|
|
|
|
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(D3H_01H, 0xD3, 0x01, IAP_F_FM | IAP_F_IB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
|
|
|
IAPDESCR(D3H_04H, 0xD3, 0x04, IAP_F_FM | IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(D3H_10H, 0xD3, 0x10, IAP_F_IBX),
|
|
|
|
IAPDESCR(D3H_20H, 0xD3, 0x20, IAP_F_IBX),
|
2012-09-06 13:54:01 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(D4H_01H, 0xD4, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(D4H_02H, 0xD4, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(D4H_04H, 0xD4, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(D4H_08H, 0xD4, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(D4H_0FH, 0xD4, 0x0F, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(D5H_01H, 0xD5, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2 |
|
|
|
|
IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
IAPDESCR(D5H_02H, 0xD5, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(D5H_04H, 0xD5, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(D5H_08H, 0xD5, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(D5H_0FH, 0xD5, 0x0F, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(D7H_00H, 0xD7, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(D8H_00H, 0xD8, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(D8H_01H, 0xD8, 0x01, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(D8H_02H, 0xD8, 0x02, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(D8H_03H, 0xD8, 0x03, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(D8H_04H, 0xD8, 0x04, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(D9H_00H, 0xD9, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(D9H_01H, 0xD9, 0x01, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(D9H_02H, 0xD9, 0x02, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(D9H_03H, 0xD9, 0x03, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(DAH_00H, 0xDA, 0x00, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(DAH_01H, 0xDA, 0x01, IAP_F_FM | IAP_F_CC),
|
|
|
|
IAPDESCR(DAH_02H, 0xDA, 0x02, IAP_F_FM | IAP_F_CC),
|
|
|
|
|
|
|
|
IAPDESCR(DBH_00H, 0xDB, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(DBH_01H, 0xDB, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(DCH_01H, 0xDC, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(DCH_02H, 0xDC, 0x02, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(DCH_04H, 0xDC, 0x04, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(DCH_08H, 0xDC, 0x08, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(DCH_10H, 0xDC, 0x10, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
IAPDESCR(DCH_1FH, 0xDC, 0x1F, IAP_F_FM | IAP_F_CA | IAP_F_CC2),
|
|
|
|
|
|
|
|
IAPDESCR(E0H_00H, 0xE0, 0x00, IAP_F_FM | IAP_F_CC | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(E0H_01H, 0xE0, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_I7 |
|
|
|
|
IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(E2H_00H, 0xE2, 0x00, IAP_F_FM | IAP_F_CC),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(E4H_00H, 0xE4, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(E4H_01H, 0xE4, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(E5H_01H, 0xE5, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
IAPDESCR(E6H_00H, 0xE6, 0x00, IAP_F_FM | IAP_F_CC | IAP_F_CC2),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(E6H_01H, 0xE6, 0x01, IAP_F_FM | IAP_F_CA | IAP_F_I7 |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_WM | IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(E6H_02H, 0xE6, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2013-01-31 22:09:53 +00:00
|
|
|
IAPDESCR(E6H_1FH, 0xE6, 0x1F, IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(E8H_01H, 0xE8, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
IAPDESCR(E8H_02H, 0xE8, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
2012-01-04 07:58:36 +00:00
|
|
|
IAPDESCR(E8H_03H, 0xE8, 0x03, IAP_F_FM | IAP_F_I7O),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(ECH_01H, 0xEC, 0x01, IAP_F_FM | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(F0H_00H, 0xF0, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_01H, 0xF0, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_02H, 0xF0, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_04H, 0xF0, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_08H, 0xF0, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_10H, 0xF0, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_20H, 0xF0, 0x20, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_40H, 0xF0, 0x40, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F0H_80H, 0xF0, 0x80, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
2012-10-19 17:01:27 +00:00
|
|
|
IAPDESCR(F1H_01H, 0xF1, 0x01, IAP_F_FM | IAP_F_SB | IAP_F_IB |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F1H_02H, 0xF1, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F1H_04H, 0xF1, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F1H_07H, 0xF1, 0x07, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
|
|
|
|
IAPDESCR(F2H_01H, 0xF2, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F2H_02H, 0xF2, 0x02, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F2H_04H, 0xF2, 0x04, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F2H_08H, 0xF2, 0x08, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2013-01-31 22:09:53 +00:00
|
|
|
IAP_F_SB | IAP_F_IB | IAP_F_SBX | IAP_F_IBX),
|
|
|
|
IAPDESCR(F2H_0AH, 0xF2, 0x0A, IAP_F_FM | IAP_F_SB | IAP_F_SBX |
|
|
|
|
IAP_F_IBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
IAPDESCR(F2H_0FH, 0xF2, 0x0F, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(F3H_01H, 0xF3, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F3H_02H, 0xF3, 0x02, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F3H_04H, 0xF3, 0x04, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F3H_08H, 0xF3, 0x08, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F3H_10H, 0xF3, 0x10, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F3H_20H, 0xF3, 0x20, IAP_F_FM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(F4H_01H, 0xF4, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F4H_02H, 0xF4, 0x02, IAP_F_FM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F4H_04H, 0xF4, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_I7O),
|
|
|
|
IAPDESCR(F4H_08H, 0xF4, 0x08, IAP_F_FM | IAP_F_I7O),
|
2012-03-01 21:23:26 +00:00
|
|
|
IAPDESCR(F4H_10H, 0xF4, 0x10, IAP_F_FM | IAP_F_I7 | IAP_F_WM |
|
2012-10-19 17:01:27 +00:00
|
|
|
IAP_F_SB | IAP_F_SBX),
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
IAPDESCR(F6H_01H, 0xF6, 0x01, IAP_F_FM | IAP_F_I7 | IAP_F_WM),
|
|
|
|
|
|
|
|
IAPDESCR(F7H_01H, 0xF7, 0x01, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(F7H_02H, 0xF7, 0x02, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(F7H_04H, 0xF7, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
|
|
|
|
IAPDESCR(F8H_00H, 0xF8, 0x00, IAP_F_FM | IAP_F_ALLCPUSCORE2),
|
|
|
|
IAPDESCR(F8H_01H, 0xF8, 0x01, IAP_F_FM | IAP_F_I7O),
|
|
|
|
|
|
|
|
IAPDESCR(FDH_01H, 0xFD, 0x01, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(FDH_02H, 0xFD, 0x02, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(FDH_04H, 0xFD, 0x04, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(FDH_08H, 0xFD, 0x08, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(FDH_10H, 0xFD, 0x10, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(FDH_20H, 0xFD, 0x20, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
|
|
|
IAPDESCR(FDH_40H, 0xFD, 0x40, IAP_F_FM | IAP_F_WM | IAP_F_I7),
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
static const int niap_events = sizeof(iap_events) / sizeof(iap_events[0]);
|
|
|
|
|
|
|
|
static pmc_value_t
|
|
|
|
iap_perfctr_value_to_reload_count(pmc_value_t v)
|
|
|
|
{
|
|
|
|
v &= (1ULL << core_iap_width) - 1;
|
|
|
|
return (1ULL << core_iap_width) - v;
|
|
|
|
}
|
|
|
|
|
|
|
|
static pmc_value_t
|
|
|
|
iap_reload_count_to_perfctr_value(pmc_value_t rlc)
|
|
|
|
{
|
|
|
|
return (1ULL << core_iap_width) - rlc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_pmc_has_overflowed(int ri)
|
|
|
|
{
|
|
|
|
uint64_t v;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* We treat a Core (i.e., Intel architecture v1) PMC as has
|
|
|
|
* having overflowed if its MSB is zero.
|
|
|
|
*/
|
|
|
|
v = rdpmc(ri);
|
|
|
|
return ((v & (1ULL << (core_iap_width - 1))) == 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Check an event against the set of supported architectural events.
|
|
|
|
*
|
|
|
|
* Returns 1 if the event is architectural and unsupported on this
|
|
|
|
* CPU. Returns 0 otherwise.
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_architectural_event_is_unsupported(enum pmc_event pe)
|
|
|
|
{
|
|
|
|
enum core_arch_events ae;
|
|
|
|
|
|
|
|
switch (pe) {
|
|
|
|
case PMC_EV_IAP_EVENT_3CH_00H:
|
|
|
|
ae = CORE_AE_UNHALTED_CORE_CYCLES;
|
|
|
|
break;
|
|
|
|
case PMC_EV_IAP_EVENT_C0H_00H:
|
|
|
|
ae = CORE_AE_INSTRUCTION_RETIRED;
|
|
|
|
break;
|
|
|
|
case PMC_EV_IAP_EVENT_3CH_01H:
|
|
|
|
ae = CORE_AE_UNHALTED_REFERENCE_CYCLES;
|
|
|
|
break;
|
|
|
|
case PMC_EV_IAP_EVENT_2EH_4FH:
|
|
|
|
ae = CORE_AE_LLC_REFERENCE;
|
|
|
|
break;
|
|
|
|
case PMC_EV_IAP_EVENT_2EH_41H:
|
|
|
|
ae = CORE_AE_LLC_MISSES;
|
|
|
|
break;
|
|
|
|
case PMC_EV_IAP_EVENT_C4H_00H:
|
|
|
|
ae = CORE_AE_BRANCH_INSTRUCTION_RETIRED;
|
|
|
|
break;
|
|
|
|
case PMC_EV_IAP_EVENT_C5H_00H:
|
|
|
|
ae = CORE_AE_BRANCH_MISSES_RETIRED;
|
|
|
|
break;
|
|
|
|
|
|
|
|
default: /* Non architectural event. */
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
return ((core_architectural_events & (1 << ae)) == 0);
|
|
|
|
}
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
static int
|
|
|
|
iap_event_corei7_ok_on_counter(enum pmc_event pe, int ri)
|
|
|
|
{
|
|
|
|
uint32_t mask;
|
|
|
|
|
|
|
|
switch (pe) {
|
|
|
|
/*
|
|
|
|
* Events valid only on counter 0, 1.
|
|
|
|
*/
|
|
|
|
case PMC_EV_IAP_EVENT_40H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_40H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_40H_04H:
|
|
|
|
case PMC_EV_IAP_EVENT_40H_08H:
|
|
|
|
case PMC_EV_IAP_EVENT_40H_0FH:
|
|
|
|
case PMC_EV_IAP_EVENT_41H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_41H_04H:
|
|
|
|
case PMC_EV_IAP_EVENT_41H_08H:
|
|
|
|
case PMC_EV_IAP_EVENT_42H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_42H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_42H_04H:
|
|
|
|
case PMC_EV_IAP_EVENT_42H_08H:
|
|
|
|
case PMC_EV_IAP_EVENT_43H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_43H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_51H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_51H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_51H_04H:
|
|
|
|
case PMC_EV_IAP_EVENT_51H_08H:
|
|
|
|
case PMC_EV_IAP_EVENT_63H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_63H_02H:
|
|
|
|
mask = 0x3;
|
|
|
|
break;
|
|
|
|
|
|
|
|
default:
|
|
|
|
mask = ~0; /* Any row index is ok. */
|
|
|
|
}
|
|
|
|
|
|
|
|
return (mask & (1 << ri));
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_event_westmere_ok_on_counter(enum pmc_event pe, int ri)
|
|
|
|
{
|
|
|
|
uint32_t mask;
|
|
|
|
|
|
|
|
switch (pe) {
|
|
|
|
/*
|
|
|
|
* Events valid only on counter 0.
|
|
|
|
*/
|
2011-12-02 10:02:49 +00:00
|
|
|
case PMC_EV_IAP_EVENT_60H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_60H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_60H_04H:
|
|
|
|
case PMC_EV_IAP_EVENT_60H_08H:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_EV_IAP_EVENT_B3H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_B3H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_B3H_04H:
|
|
|
|
mask = 0x1;
|
|
|
|
break;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Events valid only on counter 0, 1.
|
|
|
|
*/
|
2011-12-02 10:02:49 +00:00
|
|
|
case PMC_EV_IAP_EVENT_4CH_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_4EH_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_4EH_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_4EH_04H:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_EV_IAP_EVENT_51H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_51H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_51H_04H:
|
|
|
|
case PMC_EV_IAP_EVENT_51H_08H:
|
|
|
|
case PMC_EV_IAP_EVENT_63H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_63H_02H:
|
|
|
|
mask = 0x3;
|
|
|
|
break;
|
|
|
|
|
|
|
|
default:
|
|
|
|
mask = ~0; /* Any row index is ok. */
|
|
|
|
}
|
|
|
|
|
|
|
|
return (mask & (1 << ri));
|
|
|
|
}
|
|
|
|
|
2012-03-01 21:23:26 +00:00
|
|
|
static int
|
2013-01-31 22:09:53 +00:00
|
|
|
iap_event_sb_sbx_ib_ibx_ok_on_counter(enum pmc_event pe, int ri)
|
2012-09-06 13:54:01 +00:00
|
|
|
{
|
|
|
|
uint32_t mask;
|
|
|
|
|
|
|
|
switch (pe) {
|
2012-09-07 14:45:59 +00:00
|
|
|
/* Events valid only on counter 0. */
|
|
|
|
case PMC_EV_IAP_EVENT_B7H_01H:
|
|
|
|
mask = 0x1;
|
|
|
|
break;
|
|
|
|
/* Events valid only on counter 1. */
|
|
|
|
case PMC_EV_IAP_EVENT_C0H_01H:
|
|
|
|
mask = 0x1;
|
|
|
|
break;
|
|
|
|
/* Events valid only on counter 2. */
|
2012-09-06 13:54:01 +00:00
|
|
|
case PMC_EV_IAP_EVENT_48H_01H:
|
2012-10-19 17:01:27 +00:00
|
|
|
case PMC_EV_IAP_EVENT_A2H_02H:
|
2012-09-06 13:54:01 +00:00
|
|
|
mask = 0x4;
|
|
|
|
break;
|
2012-09-07 14:45:59 +00:00
|
|
|
/* Events valid only on counter 3. */
|
2013-01-31 22:09:53 +00:00
|
|
|
case PMC_EV_IAP_EVENT_A3H_08H:
|
2012-09-07 14:45:59 +00:00
|
|
|
case PMC_EV_IAP_EVENT_BBH_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_CDH_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_CDH_02H:
|
|
|
|
mask = 0x8;
|
|
|
|
break;
|
2012-09-06 13:54:01 +00:00
|
|
|
default:
|
|
|
|
mask = ~0; /* Any row index is ok. */
|
|
|
|
}
|
|
|
|
|
|
|
|
return (mask & (1 << ri));
|
|
|
|
}
|
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
static int
|
|
|
|
iap_event_ok_on_counter(enum pmc_event pe, int ri)
|
|
|
|
{
|
|
|
|
uint32_t mask;
|
|
|
|
|
|
|
|
switch (pe) {
|
|
|
|
/*
|
|
|
|
* Events valid only on counter 0.
|
|
|
|
*/
|
|
|
|
case PMC_EV_IAP_EVENT_10H_00H:
|
|
|
|
case PMC_EV_IAP_EVENT_14H_00H:
|
|
|
|
case PMC_EV_IAP_EVENT_18H_00H:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_EV_IAP_EVENT_B3H_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_B3H_02H:
|
|
|
|
case PMC_EV_IAP_EVENT_B3H_04H:
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
case PMC_EV_IAP_EVENT_C1H_00H:
|
|
|
|
case PMC_EV_IAP_EVENT_CBH_01H:
|
|
|
|
case PMC_EV_IAP_EVENT_CBH_02H:
|
|
|
|
mask = (1 << 0);
|
|
|
|
break;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Events valid only on counter 1.
|
|
|
|
*/
|
|
|
|
case PMC_EV_IAP_EVENT_11H_00H:
|
|
|
|
case PMC_EV_IAP_EVENT_12H_00H:
|
|
|
|
case PMC_EV_IAP_EVENT_13H_00H:
|
|
|
|
mask = (1 << 1);
|
|
|
|
break;
|
|
|
|
|
|
|
|
default:
|
|
|
|
mask = ~0; /* Any row index is ok. */
|
|
|
|
}
|
|
|
|
|
|
|
|
return (mask & (1 << ri));
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_allocate_pmc(int cpu, int ri, struct pmc *pm,
|
|
|
|
const struct pmc_op_pmcallocate *a)
|
|
|
|
{
|
2011-12-12 13:12:55 +00:00
|
|
|
int n, model;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
enum pmc_event ev;
|
|
|
|
struct iap_event_descr *ie;
|
|
|
|
uint32_t c, caps, config, cpuflag, evsel, mask;
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[core,%d] illegal row-index value %d", __LINE__, ri));
|
|
|
|
|
|
|
|
/* check requested capabilities */
|
|
|
|
caps = a->pm_caps;
|
|
|
|
if ((IAP_PMC_CAPS & caps) != caps)
|
|
|
|
return (EPERM);
|
|
|
|
|
|
|
|
ev = pm->pm_event;
|
|
|
|
|
|
|
|
if (iap_architectural_event_is_unsupported(ev))
|
|
|
|
return (EOPNOTSUPP);
|
|
|
|
|
2011-12-12 13:12:55 +00:00
|
|
|
/*
|
|
|
|
* A small number of events are not supported in all the
|
|
|
|
* processors based on a given microarchitecture.
|
|
|
|
*/
|
|
|
|
if (ev == PMC_EV_IAP_EVENT_0FH_01H || ev == PMC_EV_IAP_EVENT_0FH_80H) {
|
|
|
|
model = ((cpu_id & 0xF0000) >> 12) | ((cpu_id & 0xF0) >> 4);
|
|
|
|
if (core_cputype == PMC_CPU_INTEL_COREI7 && model != 0x2E)
|
|
|
|
return (EINVAL);
|
|
|
|
}
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
switch (core_cputype) {
|
|
|
|
case PMC_CPU_INTEL_COREI7:
|
|
|
|
if (iap_event_corei7_ok_on_counter(ev, ri) == 0)
|
|
|
|
return (EINVAL);
|
|
|
|
break;
|
2012-03-01 21:23:26 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE:
|
2012-10-19 17:01:27 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE_XEON:
|
2012-09-07 14:45:59 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE:
|
2013-01-31 22:09:53 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE_XEON:
|
|
|
|
if (iap_event_sb_sbx_ib_ibx_ok_on_counter(ev, ri) == 0)
|
2012-03-01 21:23:26 +00:00
|
|
|
return (EINVAL);
|
|
|
|
break;
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE:
|
|
|
|
if (iap_event_westmere_ok_on_counter(ev, ri) == 0)
|
|
|
|
return (EINVAL);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
if (iap_event_ok_on_counter(ev, ri) == 0)
|
|
|
|
return (EINVAL);
|
|
|
|
}
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Look for an event descriptor with matching CPU and event id
|
|
|
|
* fields.
|
|
|
|
*/
|
|
|
|
|
|
|
|
switch (core_cputype) {
|
|
|
|
default:
|
|
|
|
case PMC_CPU_INTEL_ATOM:
|
|
|
|
cpuflag = IAP_F_CA;
|
|
|
|
break;
|
|
|
|
case PMC_CPU_INTEL_CORE:
|
|
|
|
cpuflag = IAP_F_CC;
|
|
|
|
break;
|
|
|
|
case PMC_CPU_INTEL_CORE2:
|
|
|
|
cpuflag = IAP_F_CC2;
|
|
|
|
break;
|
|
|
|
case PMC_CPU_INTEL_CORE2EXTREME:
|
2008-12-03 17:30:36 +00:00
|
|
|
cpuflag = IAP_F_CC2 | IAP_F_CC2E;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
break;
|
2009-01-27 07:29:37 +00:00
|
|
|
case PMC_CPU_INTEL_COREI7:
|
|
|
|
cpuflag = IAP_F_I7;
|
|
|
|
break;
|
2012-09-06 13:54:01 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE:
|
|
|
|
cpuflag = IAP_F_IB;
|
|
|
|
break;
|
2013-01-31 22:09:53 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE_XEON:
|
|
|
|
cpuflag = IAP_F_IBX;
|
|
|
|
break;
|
2012-03-01 21:23:26 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE:
|
|
|
|
cpuflag = IAP_F_SB;
|
|
|
|
break;
|
2012-10-19 17:01:27 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE_XEON:
|
|
|
|
cpuflag = IAP_F_SBX;
|
|
|
|
break;
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE:
|
|
|
|
cpuflag = IAP_F_WM;
|
|
|
|
break;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
for (n = 0, ie = iap_events; n < niap_events; n++, ie++)
|
|
|
|
if (ie->iap_ev == ev && ie->iap_flags & cpuflag)
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (n == niap_events)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* A matching event descriptor has been found, so start
|
|
|
|
* assembling the contents of the event select register.
|
|
|
|
*/
|
|
|
|
evsel = ie->iap_evcode;
|
|
|
|
|
|
|
|
config = a->pm_md.pm_iap.pm_iap_config & ~IAP_F_CMASK;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the event uses a fixed umask value, reject any umask
|
|
|
|
* bits set by the user.
|
|
|
|
*/
|
|
|
|
if (ie->iap_flags & IAP_F_FM) {
|
|
|
|
|
|
|
|
if (IAP_UMASK(config) != 0)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
evsel |= (ie->iap_umask << 8);
|
|
|
|
|
|
|
|
} else {
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Otherwise, the UMASK value needs to be taken from
|
|
|
|
* the MD fields of the allocation request. Reject
|
|
|
|
* requests that specify reserved bits.
|
|
|
|
*/
|
|
|
|
|
|
|
|
mask = 0;
|
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
if (ie->iap_umask & IAP_M_CORE) {
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
if ((c = (config & IAP_F_CORE)) != IAP_CORE_ALL &&
|
|
|
|
c != IAP_CORE_THIS)
|
|
|
|
return (EINVAL);
|
|
|
|
mask |= IAP_F_CORE;
|
|
|
|
}
|
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
if (ie->iap_umask & IAP_M_AGENT)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
mask |= IAP_F_AGENT;
|
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
if (ie->iap_umask & IAP_M_PREFETCH) {
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
if ((c = (config & IAP_F_PREFETCH)) ==
|
|
|
|
IAP_PREFETCH_RESERVED)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
mask |= IAP_F_PREFETCH;
|
|
|
|
}
|
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
if (ie->iap_umask & IAP_M_MESI)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
mask |= IAP_F_MESI;
|
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
if (ie->iap_umask & IAP_M_SNOOPRESPONSE)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
mask |= IAP_F_SNOOPRESPONSE;
|
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
if (ie->iap_umask & IAP_M_SNOOPTYPE)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
mask |= IAP_F_SNOOPTYPE;
|
|
|
|
|
2009-12-26 14:39:23 +00:00
|
|
|
if (ie->iap_umask & IAP_M_TRANSITION)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
mask |= IAP_F_TRANSITION;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If bits outside of the allowed set of umask bits
|
|
|
|
* are set, reject the request.
|
|
|
|
*/
|
|
|
|
if (config & ~mask)
|
|
|
|
return (EINVAL);
|
|
|
|
|
|
|
|
evsel |= (config & mask);
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2012-03-01 21:23:26 +00:00
|
|
|
* Only Atom and SandyBridge CPUs support the 'ANY' qualifier.
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
*/
|
2012-03-01 21:23:26 +00:00
|
|
|
if (core_cputype == PMC_CPU_INTEL_ATOM ||
|
2012-10-19 17:01:27 +00:00
|
|
|
core_cputype == PMC_CPU_INTEL_SANDYBRIDGE ||
|
|
|
|
core_cputype == PMC_CPU_INTEL_SANDYBRIDGE_XEON)
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
evsel |= (config & IAP_ANY);
|
|
|
|
else if (config & IAP_ANY)
|
|
|
|
return (EINVAL);
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
/*
|
|
|
|
* Check offcore response configuration.
|
|
|
|
*/
|
|
|
|
if (a->pm_md.pm_iap.pm_iap_rsp != 0) {
|
|
|
|
if (ev != PMC_EV_IAP_EVENT_B7H_01H &&
|
|
|
|
ev != PMC_EV_IAP_EVENT_BBH_01H)
|
|
|
|
return (EINVAL);
|
|
|
|
if (core_cputype == PMC_CPU_INTEL_COREI7 &&
|
|
|
|
ev == PMC_EV_IAP_EVENT_BBH_01H)
|
|
|
|
return (EINVAL);
|
2012-09-06 13:54:01 +00:00
|
|
|
if ((core_cputype == PMC_CPU_INTEL_COREI7 ||
|
|
|
|
core_cputype == PMC_CPU_INTEL_WESTMERE) &&
|
|
|
|
a->pm_md.pm_iap.pm_iap_rsp & ~IA_OFFCORE_RSP_MASK_I7WM)
|
|
|
|
return (EINVAL);
|
|
|
|
else if ((core_cputype == PMC_CPU_INTEL_SANDYBRIDGE ||
|
2013-01-31 22:09:53 +00:00
|
|
|
core_cputype == PMC_CPU_INTEL_SANDYBRIDGE_XEON ||
|
|
|
|
core_cputype == PMC_CPU_INTEL_IVYBRIDGE ||
|
|
|
|
core_cputype == PMC_CPU_INTEL_IVYBRIDGE_XEON) &&
|
2012-09-06 13:54:01 +00:00
|
|
|
a->pm_md.pm_iap.pm_iap_rsp & ~IA_OFFCORE_RSP_MASK_SBIB)
|
2010-04-02 13:23:49 +00:00
|
|
|
return (EINVAL);
|
2012-09-06 13:54:01 +00:00
|
|
|
pm->pm_md.pm_iap.pm_iap_rsp = a->pm_md.pm_iap.pm_iap_rsp;
|
2010-04-02 13:23:49 +00:00
|
|
|
}
|
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
if (caps & PMC_CAP_THRESHOLD)
|
|
|
|
evsel |= (a->pm_md.pm_iap.pm_iap_config & IAP_F_CMASK);
|
|
|
|
if (caps & PMC_CAP_USER)
|
|
|
|
evsel |= IAP_USR;
|
|
|
|
if (caps & PMC_CAP_SYSTEM)
|
|
|
|
evsel |= IAP_OS;
|
|
|
|
if ((caps & (PMC_CAP_USER | PMC_CAP_SYSTEM)) == 0)
|
|
|
|
evsel |= (IAP_OS | IAP_USR);
|
|
|
|
if (caps & PMC_CAP_EDGE)
|
|
|
|
evsel |= IAP_EDGE;
|
|
|
|
if (caps & PMC_CAP_INVERT)
|
|
|
|
evsel |= IAP_INV;
|
|
|
|
if (caps & PMC_CAP_INTERRUPT)
|
|
|
|
evsel |= IAP_INT;
|
|
|
|
|
|
|
|
pm->pm_md.pm_iap.pm_iap_evsel = evsel;
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_config_pmc(int cpu, int ri, struct pmc *pm)
|
|
|
|
{
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU %d", __LINE__, cpu));
|
|
|
|
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
PMCDBG(MDP,CFG,1, "iap-config cpu=%d ri=%d pm=%p", cpu, ri, pm);
|
|
|
|
|
|
|
|
KASSERT(core_pcpu[cpu] != NULL, ("[core,%d] null per-cpu %d", __LINE__,
|
|
|
|
cpu));
|
|
|
|
|
|
|
|
core_pcpu[cpu]->pc_corepmcs[ri].phw_pmc = pm;
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_describe(int cpu, int ri, struct pmc_info *pi, struct pmc **ppmc)
|
|
|
|
{
|
|
|
|
int error;
|
|
|
|
struct pmc_hw *phw;
|
|
|
|
char iap_name[PMC_NAME_MAX];
|
|
|
|
|
|
|
|
phw = &core_pcpu[cpu]->pc_corepmcs[ri];
|
|
|
|
|
|
|
|
(void) snprintf(iap_name, sizeof(iap_name), "IAP-%d", ri);
|
|
|
|
if ((error = copystr(iap_name, pi->pm_name, PMC_NAME_MAX,
|
|
|
|
NULL)) != 0)
|
|
|
|
return (error);
|
|
|
|
|
|
|
|
pi->pm_class = PMC_CLASS_IAP;
|
|
|
|
|
|
|
|
if (phw->phw_state & PMC_PHW_FLAG_IS_ENABLED) {
|
|
|
|
pi->pm_enabled = TRUE;
|
|
|
|
*ppmc = phw->phw_pmc;
|
|
|
|
} else {
|
|
|
|
pi->pm_enabled = FALSE;
|
|
|
|
*ppmc = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_get_config(int cpu, int ri, struct pmc **ppm)
|
|
|
|
{
|
|
|
|
*ppm = core_pcpu[cpu]->pc_corepmcs[ri].phw_pmc;
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_get_msr(int ri, uint32_t *msr)
|
|
|
|
{
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[iap,%d] ri %d out of range", __LINE__, ri));
|
|
|
|
|
|
|
|
*msr = ri;
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_read_pmc(int cpu, int ri, pmc_value_t *v)
|
|
|
|
{
|
|
|
|
struct pmc *pm;
|
|
|
|
pmc_value_t tmp;
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal cpu value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
pm = core_pcpu[cpu]->pc_corepmcs[ri].phw_pmc;
|
|
|
|
|
|
|
|
KASSERT(pm,
|
|
|
|
("[core,%d] cpu %d ri %d pmc not configured", __LINE__, cpu,
|
|
|
|
ri));
|
|
|
|
|
|
|
|
tmp = rdpmc(ri);
|
|
|
|
if (PMC_IS_SAMPLING_MODE(PMC_TO_MODE(pm)))
|
|
|
|
*v = iap_perfctr_value_to_reload_count(tmp);
|
|
|
|
else
|
2012-03-06 17:17:03 +00:00
|
|
|
*v = tmp & ((1ULL << core_iap_width) - 1);
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
PMCDBG(MDP,REA,1, "iap-read cpu=%d ri=%d msr=0x%x -> v=%jx", cpu, ri,
|
|
|
|
ri, *v);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_release_pmc(int cpu, int ri, struct pmc *pm)
|
|
|
|
{
|
|
|
|
(void) pm;
|
|
|
|
|
|
|
|
PMCDBG(MDP,REL,1, "iap-release cpu=%d ri=%d pm=%p", cpu, ri,
|
|
|
|
pm);
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
KASSERT(core_pcpu[cpu]->pc_corepmcs[ri].phw_pmc
|
|
|
|
== NULL, ("[core,%d] PHW pmc non-NULL", __LINE__));
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_start_pmc(int cpu, int ri)
|
|
|
|
{
|
|
|
|
struct pmc *pm;
|
|
|
|
uint32_t evsel;
|
|
|
|
struct core_cpu *cc;
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal CPU value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[core,%d] illegal row-index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
cc = core_pcpu[cpu];
|
|
|
|
pm = cc->pc_corepmcs[ri].phw_pmc;
|
|
|
|
|
|
|
|
KASSERT(pm,
|
|
|
|
("[core,%d] starting cpu%d,ri%d with no pmc configured",
|
|
|
|
__LINE__, cpu, ri));
|
|
|
|
|
|
|
|
PMCDBG(MDP,STA,1, "iap-start cpu=%d ri=%d", cpu, ri);
|
|
|
|
|
|
|
|
evsel = pm->pm_md.pm_iap.pm_iap_evsel;
|
|
|
|
|
|
|
|
PMCDBG(MDP,STA,2, "iap-start/2 cpu=%d ri=%d evselmsr=0x%x evsel=0x%x",
|
|
|
|
cpu, ri, IAP_EVSEL0 + ri, evsel);
|
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
/* Event specific configuration. */
|
|
|
|
switch (pm->pm_event) {
|
|
|
|
case PMC_EV_IAP_EVENT_B7H_01H:
|
|
|
|
wrmsr(IA_OFFCORE_RSP0, pm->pm_md.pm_iap.pm_iap_rsp);
|
|
|
|
break;
|
|
|
|
case PMC_EV_IAP_EVENT_BBH_01H:
|
|
|
|
wrmsr(IA_OFFCORE_RSP1, pm->pm_md.pm_iap.pm_iap_rsp);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
wrmsr(IAP_EVSEL0 + ri, evsel | IAP_EN);
|
|
|
|
|
|
|
|
if (core_cputype == PMC_CPU_INTEL_CORE)
|
|
|
|
return (0);
|
|
|
|
|
|
|
|
do {
|
|
|
|
cc->pc_resync = 0;
|
|
|
|
cc->pc_globalctrl |= (1ULL << ri);
|
|
|
|
wrmsr(IA_GLOBAL_CTRL, cc->pc_globalctrl);
|
|
|
|
} while (cc->pc_resync != 0);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_stop_pmc(int cpu, int ri)
|
|
|
|
{
|
|
|
|
struct pmc *pm;
|
|
|
|
struct core_cpu *cc;
|
2010-07-13 19:37:45 +00:00
|
|
|
uint64_t msr;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal cpu value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[core,%d] illegal row index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
cc = core_pcpu[cpu];
|
|
|
|
pm = cc->pc_corepmcs[ri].phw_pmc;
|
|
|
|
|
|
|
|
KASSERT(pm,
|
|
|
|
("[core,%d] cpu%d ri%d no configured PMC to stop", __LINE__,
|
|
|
|
cpu, ri));
|
|
|
|
|
|
|
|
PMCDBG(MDP,STO,1, "iap-stop cpu=%d ri=%d", cpu, ri);
|
|
|
|
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IAP_EVSEL0 + ri) & ~IAP_EVSEL_MASK;
|
|
|
|
wrmsr(IAP_EVSEL0 + ri, msr); /* stop hw */
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
if (core_cputype == PMC_CPU_INTEL_CORE)
|
|
|
|
return (0);
|
|
|
|
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = 0;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
do {
|
|
|
|
cc->pc_resync = 0;
|
|
|
|
cc->pc_globalctrl &= ~(1ULL << ri);
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IA_GLOBAL_CTRL) & ~IA_GLOBAL_CTRL_MASK;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
wrmsr(IA_GLOBAL_CTRL, cc->pc_globalctrl);
|
|
|
|
} while (cc->pc_resync != 0);
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
iap_write_pmc(int cpu, int ri, pmc_value_t v)
|
|
|
|
{
|
|
|
|
struct pmc *pm;
|
|
|
|
struct core_cpu *cc;
|
|
|
|
|
|
|
|
KASSERT(cpu >= 0 && cpu < pmc_cpu_max(),
|
|
|
|
("[core,%d] illegal cpu value %d", __LINE__, cpu));
|
|
|
|
KASSERT(ri >= 0 && ri < core_iap_npmc,
|
|
|
|
("[core,%d] illegal row index %d", __LINE__, ri));
|
|
|
|
|
|
|
|
cc = core_pcpu[cpu];
|
|
|
|
pm = cc->pc_corepmcs[ri].phw_pmc;
|
|
|
|
|
|
|
|
KASSERT(pm,
|
|
|
|
("[core,%d] cpu%d ri%d no configured PMC to stop", __LINE__,
|
|
|
|
cpu, ri));
|
|
|
|
|
|
|
|
PMCDBG(MDP,WRI,1, "iap-write cpu=%d ri=%d msr=0x%x v=%jx", cpu, ri,
|
|
|
|
IAP_PMC0 + ri, v);
|
|
|
|
|
|
|
|
if (PMC_IS_SAMPLING_MODE(PMC_TO_MODE(pm)))
|
|
|
|
v = iap_reload_count_to_perfctr_value(v);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Write the new value to the counter. The counter will be in
|
|
|
|
* a stopped state when the pcd_write() entry point is called.
|
|
|
|
*/
|
|
|
|
|
2010-07-13 19:37:45 +00:00
|
|
|
wrmsr(IAP_PMC0 + ri, v & ((1ULL << core_iap_width) - 1));
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static void
|
|
|
|
iap_initialize(struct pmc_mdep *md, int maxcpu, int npmc, int pmcwidth,
|
|
|
|
int flags)
|
|
|
|
{
|
|
|
|
struct pmc_classdep *pcd;
|
|
|
|
|
|
|
|
KASSERT(md != NULL, ("[iap,%d] md is NULL", __LINE__));
|
|
|
|
|
|
|
|
PMCDBG(MDP,INI,1, "%s", "iap-initialize");
|
|
|
|
|
|
|
|
/* Remember the set of architectural events supported. */
|
|
|
|
core_architectural_events = ~flags;
|
|
|
|
|
|
|
|
pcd = &md->pmd_classdep[PMC_MDEP_CLASS_INDEX_IAP];
|
|
|
|
|
|
|
|
pcd->pcd_caps = IAP_PMC_CAPS;
|
|
|
|
pcd->pcd_class = PMC_CLASS_IAP;
|
|
|
|
pcd->pcd_num = npmc;
|
|
|
|
pcd->pcd_ri = md->pmd_npmc;
|
|
|
|
pcd->pcd_width = pmcwidth;
|
|
|
|
|
|
|
|
pcd->pcd_allocate_pmc = iap_allocate_pmc;
|
|
|
|
pcd->pcd_config_pmc = iap_config_pmc;
|
|
|
|
pcd->pcd_describe = iap_describe;
|
|
|
|
pcd->pcd_get_config = iap_get_config;
|
|
|
|
pcd->pcd_get_msr = iap_get_msr;
|
|
|
|
pcd->pcd_pcpu_fini = core_pcpu_fini;
|
|
|
|
pcd->pcd_pcpu_init = core_pcpu_init;
|
|
|
|
pcd->pcd_read_pmc = iap_read_pmc;
|
|
|
|
pcd->pcd_release_pmc = iap_release_pmc;
|
|
|
|
pcd->pcd_start_pmc = iap_start_pmc;
|
|
|
|
pcd->pcd_stop_pmc = iap_stop_pmc;
|
|
|
|
pcd->pcd_write_pmc = iap_write_pmc;
|
|
|
|
|
|
|
|
md->pmd_npmc += npmc;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
core_intr(int cpu, struct trapframe *tf)
|
|
|
|
{
|
|
|
|
pmc_value_t v;
|
|
|
|
struct pmc *pm;
|
|
|
|
struct core_cpu *cc;
|
|
|
|
int error, found_interrupt, ri;
|
2010-07-29 17:52:23 +00:00
|
|
|
uint64_t msr;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
PMCDBG(MDP,INT, 1, "cpu=%d tf=0x%p um=%d", cpu, (void *) tf,
|
|
|
|
TRAPF_USERMODE(tf));
|
|
|
|
|
2008-12-16 11:04:02 +00:00
|
|
|
found_interrupt = 0;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
cc = core_pcpu[cpu];
|
|
|
|
|
|
|
|
for (ri = 0; ri < core_iap_npmc; ri++) {
|
|
|
|
|
|
|
|
if ((pm = cc->pc_corepmcs[ri].phw_pmc) == NULL ||
|
|
|
|
!PMC_IS_SAMPLING_MODE(PMC_TO_MODE(pm)))
|
|
|
|
continue;
|
|
|
|
|
2008-12-16 11:04:02 +00:00
|
|
|
if (!iap_pmc_has_overflowed(ri))
|
|
|
|
continue;
|
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
found_interrupt = 1;
|
|
|
|
|
|
|
|
if (pm->pm_state != PMC_STATE_RUNNING)
|
|
|
|
continue;
|
|
|
|
|
2012-03-28 20:58:30 +00:00
|
|
|
error = pmc_process_interrupt(cpu, PMC_HR, pm, tf,
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
TRAPF_USERMODE(tf));
|
|
|
|
|
|
|
|
v = pm->pm_sc.pm_reloadcount;
|
|
|
|
v = iaf_reload_count_to_perfctr_value(v);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Stop the counter, reload it but only restart it if
|
|
|
|
* the PMC is not stalled.
|
|
|
|
*/
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IAP_EVSEL0 + ri) & ~IAP_EVSEL_MASK;
|
|
|
|
wrmsr(IAP_EVSEL0 + ri, msr);
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
wrmsr(IAP_PMC0 + ri, v);
|
|
|
|
|
|
|
|
if (error)
|
|
|
|
continue;
|
|
|
|
|
2010-07-29 17:52:23 +00:00
|
|
|
wrmsr(IAP_EVSEL0 + ri, msr | (pm->pm_md.pm_iap.pm_iap_evsel |
|
|
|
|
IAP_EN));
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
if (found_interrupt)
|
2009-08-14 21:05:08 +00:00
|
|
|
lapic_reenable_pmc();
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
atomic_add_int(found_interrupt ? &pmc_stats.pm_intr_processed :
|
|
|
|
&pmc_stats.pm_intr_ignored, 1);
|
|
|
|
|
|
|
|
return (found_interrupt);
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
core2_intr(int cpu, struct trapframe *tf)
|
|
|
|
{
|
|
|
|
int error, found_interrupt, n;
|
2010-07-29 17:52:23 +00:00
|
|
|
uint64_t flag, intrstatus, intrenable, msr;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
struct pmc *pm;
|
|
|
|
struct core_cpu *cc;
|
|
|
|
pmc_value_t v;
|
|
|
|
|
|
|
|
PMCDBG(MDP,INT, 1, "cpu=%d tf=0x%p um=%d", cpu, (void *) tf,
|
|
|
|
TRAPF_USERMODE(tf));
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The IA_GLOBAL_STATUS (MSR 0x38E) register indicates which
|
|
|
|
* PMCs have a pending PMI interrupt. We take a 'snapshot' of
|
|
|
|
* the current set of interrupting PMCs and process these
|
|
|
|
* after stopping them.
|
|
|
|
*/
|
|
|
|
intrstatus = rdmsr(IA_GLOBAL_STATUS);
|
|
|
|
intrenable = intrstatus & core_pmcmask;
|
|
|
|
|
|
|
|
PMCDBG(MDP,INT, 1, "cpu=%d intrstatus=%jx", cpu,
|
|
|
|
(uintmax_t) intrstatus);
|
|
|
|
|
2008-12-16 11:04:02 +00:00
|
|
|
found_interrupt = 0;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
cc = core_pcpu[cpu];
|
2008-12-16 11:04:02 +00:00
|
|
|
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
KASSERT(cc != NULL, ("[core,%d] null pcpu", __LINE__));
|
|
|
|
|
|
|
|
cc->pc_globalctrl &= ~intrenable;
|
|
|
|
cc->pc_resync = 1; /* MSRs now potentially out of sync. */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Stop PMCs and clear overflow status bits.
|
|
|
|
*/
|
2010-07-29 17:52:23 +00:00
|
|
|
msr = rdmsr(IA_GLOBAL_CTRL) & ~IA_GLOBAL_CTRL_MASK;
|
|
|
|
wrmsr(IA_GLOBAL_CTRL, msr);
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
wrmsr(IA_GLOBAL_OVF_CTRL, intrenable |
|
|
|
|
IA_GLOBAL_STATUS_FLAG_OVFBUF |
|
|
|
|
IA_GLOBAL_STATUS_FLAG_CONDCHG);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Look for interrupts from fixed function PMCs.
|
|
|
|
*/
|
|
|
|
for (n = 0, flag = (1ULL << IAF_OFFSET); n < core_iaf_npmc;
|
|
|
|
n++, flag <<= 1) {
|
|
|
|
|
|
|
|
if ((intrstatus & flag) == 0)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
found_interrupt = 1;
|
|
|
|
|
|
|
|
pm = cc->pc_corepmcs[n + core_iaf_ri].phw_pmc;
|
|
|
|
if (pm == NULL || pm->pm_state != PMC_STATE_RUNNING ||
|
|
|
|
!PMC_IS_SAMPLING_MODE(PMC_TO_MODE(pm)))
|
|
|
|
continue;
|
|
|
|
|
2012-03-28 20:58:30 +00:00
|
|
|
error = pmc_process_interrupt(cpu, PMC_HR, pm, tf,
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
TRAPF_USERMODE(tf));
|
2010-04-02 13:23:49 +00:00
|
|
|
if (error)
|
|
|
|
intrenable &= ~flag;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
v = iaf_reload_count_to_perfctr_value(pm->pm_sc.pm_reloadcount);
|
|
|
|
|
|
|
|
/* Reload sampling count. */
|
|
|
|
wrmsr(IAF_CTR0 + n, v);
|
|
|
|
|
|
|
|
PMCDBG(MDP,INT, 1, "iaf-intr cpu=%d error=%d v=%jx(%jx)", cpu, error,
|
|
|
|
(uintmax_t) v, (uintmax_t) rdpmc(IAF_RI_TO_MSR(n)));
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Process interrupts from the programmable counters.
|
|
|
|
*/
|
|
|
|
for (n = 0, flag = 1; n < core_iap_npmc; n++, flag <<= 1) {
|
|
|
|
if ((intrstatus & flag) == 0)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
found_interrupt = 1;
|
|
|
|
|
|
|
|
pm = cc->pc_corepmcs[n].phw_pmc;
|
|
|
|
if (pm == NULL || pm->pm_state != PMC_STATE_RUNNING ||
|
|
|
|
!PMC_IS_SAMPLING_MODE(PMC_TO_MODE(pm)))
|
|
|
|
continue;
|
|
|
|
|
2012-03-28 20:58:30 +00:00
|
|
|
error = pmc_process_interrupt(cpu, PMC_HR, pm, tf,
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
TRAPF_USERMODE(tf));
|
|
|
|
if (error)
|
|
|
|
intrenable &= ~flag;
|
|
|
|
|
|
|
|
v = iap_reload_count_to_perfctr_value(pm->pm_sc.pm_reloadcount);
|
|
|
|
|
|
|
|
PMCDBG(MDP,INT, 1, "iap-intr cpu=%d error=%d v=%jx", cpu, error,
|
|
|
|
(uintmax_t) v);
|
|
|
|
|
|
|
|
/* Reload sampling count. */
|
|
|
|
wrmsr(IAP_PMC0 + n, v);
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Reenable all non-stalled PMCs.
|
|
|
|
*/
|
|
|
|
PMCDBG(MDP,INT, 1, "cpu=%d intrenable=%jx", cpu,
|
|
|
|
(uintmax_t) intrenable);
|
|
|
|
|
|
|
|
cc->pc_globalctrl |= intrenable;
|
|
|
|
|
2010-07-29 17:52:23 +00:00
|
|
|
wrmsr(IA_GLOBAL_CTRL, cc->pc_globalctrl & IA_GLOBAL_CTRL_MASK);
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
PMCDBG(MDP,INT, 1, "cpu=%d fixedctrl=%jx globalctrl=%jx status=%jx "
|
|
|
|
"ovf=%jx", cpu, (uintmax_t) rdmsr(IAF_CTRL),
|
|
|
|
(uintmax_t) rdmsr(IA_GLOBAL_CTRL),
|
|
|
|
(uintmax_t) rdmsr(IA_GLOBAL_STATUS),
|
|
|
|
(uintmax_t) rdmsr(IA_GLOBAL_OVF_CTRL));
|
|
|
|
|
|
|
|
if (found_interrupt)
|
2009-08-14 21:05:08 +00:00
|
|
|
lapic_reenable_pmc();
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
atomic_add_int(found_interrupt ? &pmc_stats.pm_intr_processed :
|
|
|
|
&pmc_stats.pm_intr_ignored, 1);
|
|
|
|
|
|
|
|
return (found_interrupt);
|
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
pmc_core_initialize(struct pmc_mdep *md, int maxcpu)
|
|
|
|
{
|
|
|
|
int cpuid[CORE_CPUID_REQUEST_SIZE];
|
|
|
|
int ipa_version, flags, nflags;
|
|
|
|
|
|
|
|
do_cpuid(CORE_CPUID_REQUEST, cpuid);
|
|
|
|
|
|
|
|
ipa_version = cpuid[CORE_CPUID_EAX] & 0xFF;
|
|
|
|
|
|
|
|
PMCDBG(MDP,INI,1,"core-init cputype=%d ncpu=%d ipa-version=%d",
|
|
|
|
md->pmd_cputype, maxcpu, ipa_version);
|
|
|
|
|
2012-03-27 18:22:14 +00:00
|
|
|
if (ipa_version < 1 || ipa_version > 3) {
|
|
|
|
/* Unknown PMC architecture. */
|
|
|
|
printf("hwpc_core: unknown PMC architecture: %d\n",
|
|
|
|
ipa_version);
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
return (EPROGMISMATCH);
|
2012-03-27 18:22:14 +00:00
|
|
|
}
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
|
|
|
|
core_cputype = md->pmd_cputype;
|
|
|
|
|
|
|
|
core_pmcmask = 0;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Initialize programmable counters.
|
|
|
|
*/
|
|
|
|
KASSERT(ipa_version >= 1,
|
|
|
|
("[core,%d] ipa_version %d too small", __LINE__, ipa_version));
|
|
|
|
|
|
|
|
core_iap_npmc = (cpuid[CORE_CPUID_EAX] >> 8) & 0xFF;
|
|
|
|
core_iap_width = (cpuid[CORE_CPUID_EAX] >> 16) & 0xFF;
|
|
|
|
|
|
|
|
core_pmcmask |= ((1ULL << core_iap_npmc) - 1);
|
|
|
|
|
|
|
|
nflags = (cpuid[CORE_CPUID_EAX] >> 24) & 0xFF;
|
|
|
|
flags = cpuid[CORE_CPUID_EBX] & ((1 << nflags) - 1);
|
|
|
|
|
|
|
|
iap_initialize(md, maxcpu, core_iap_npmc, core_iap_width, flags);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Initialize fixed function counters, if present.
|
|
|
|
*/
|
|
|
|
if (core_cputype != PMC_CPU_INTEL_CORE) {
|
|
|
|
KASSERT(ipa_version >= 2,
|
|
|
|
("[core,%d] ipa_version %d too small", __LINE__,
|
|
|
|
ipa_version));
|
|
|
|
|
|
|
|
core_iaf_ri = core_iap_npmc;
|
|
|
|
core_iaf_npmc = cpuid[CORE_CPUID_EDX] & 0x1F;
|
|
|
|
core_iaf_width = (cpuid[CORE_CPUID_EDX] >> 5) & 0xFF;
|
|
|
|
|
2010-09-05 13:31:14 +00:00
|
|
|
iaf_initialize(md, maxcpu, core_iaf_npmc, core_iaf_width);
|
|
|
|
core_pmcmask |= ((1ULL << core_iaf_npmc) - 1) << IAF_OFFSET;
|
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
2008-11-27 09:00:47 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
PMCDBG(MDP,INI,1,"core-init pmcmask=0x%jx iafri=%d", core_pmcmask,
|
|
|
|
core_iaf_ri);
|
|
|
|
|
|
|
|
core_pcpu = malloc(sizeof(struct core_cpu **) * maxcpu, M_PMC,
|
|
|
|
M_ZERO | M_WAITOK);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Choose the appropriate interrupt handler.
|
|
|
|
*/
|
|
|
|
if (ipa_version == 1)
|
|
|
|
md->pmd_intr = core_intr;
|
|
|
|
else
|
|
|
|
md->pmd_intr = core2_intr;
|
|
|
|
|
|
|
|
md->pmd_pcpu_fini = NULL;
|
|
|
|
md->pmd_pcpu_init = NULL;
|
|
|
|
|
|
|
|
return (0);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
pmc_core_finalize(struct pmc_mdep *md)
|
|
|
|
{
|
|
|
|
PMCDBG(MDP,INI,1, "%s", "core-finalize");
|
|
|
|
|
|
|
|
free(core_pcpu, M_PMC);
|
|
|
|
core_pcpu = NULL;
|
|
|
|
}
|