2008-11-09 17:37:54 +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.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Common code for handling Intel CPUs.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <sys/cdefs.h>
|
|
|
|
__FBSDID("$FreeBSD$");
|
|
|
|
|
|
|
|
#include <sys/param.h>
|
|
|
|
#include <sys/pmc.h>
|
|
|
|
#include <sys/pmckern.h>
|
|
|
|
#include <sys/systm.h>
|
|
|
|
|
|
|
|
#include <machine/cpu.h>
|
2008-11-26 19:25:13 +00:00
|
|
|
#include <machine/cputypes.h>
|
2008-11-09 17:37:54 +00:00
|
|
|
#include <machine/md_var.h>
|
|
|
|
#include <machine/specialreg.h>
|
|
|
|
|
|
|
|
static int
|
|
|
|
intel_switch_in(struct pmc_cpu *pc, struct pmc_process *pp)
|
|
|
|
{
|
|
|
|
(void) pc;
|
|
|
|
|
2015-05-08 19:40:00 +00:00
|
|
|
PMCDBG3(MDP,SWI,1, "pc=%p pp=%p enable-msr=%d", pc, pp,
|
2008-11-09 17:37:54 +00:00
|
|
|
pp->pp_flags & PMC_PP_ENABLE_MSR_ACCESS);
|
|
|
|
|
|
|
|
/* allow the RDPMC instruction if needed */
|
|
|
|
if (pp->pp_flags & PMC_PP_ENABLE_MSR_ACCESS)
|
|
|
|
load_cr4(rcr4() | CR4_PCE);
|
|
|
|
|
2015-05-08 19:40:00 +00:00
|
|
|
PMCDBG1(MDP,SWI,1, "cr4=0x%jx", (uintmax_t) rcr4());
|
2008-11-09 17:37:54 +00:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int
|
|
|
|
intel_switch_out(struct pmc_cpu *pc, struct pmc_process *pp)
|
|
|
|
{
|
|
|
|
(void) pc;
|
|
|
|
(void) pp; /* can be NULL */
|
|
|
|
|
2015-05-08 19:40:00 +00:00
|
|
|
PMCDBG3(MDP,SWO,1, "pc=%p pp=%p cr4=0x%jx", pc, pp,
|
2008-11-09 17:37:54 +00:00
|
|
|
(uintmax_t) rcr4());
|
|
|
|
|
|
|
|
/* always turn off the RDPMC instruction */
|
2013-04-03 21:34:35 +00:00
|
|
|
load_cr4(rcr4() & ~CR4_PCE);
|
2008-11-09 17:37:54 +00:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
struct pmc_mdep *
|
|
|
|
pmc_intel_initialize(void)
|
|
|
|
{
|
|
|
|
struct pmc_mdep *pmc_mdep;
|
|
|
|
enum pmc_cputype cputype;
|
2013-12-20 14:03:56 +00:00
|
|
|
int error, model, nclasses, ncpus, stepping, verov;
|
2008-11-09 17:37:54 +00:00
|
|
|
|
2008-11-26 19:25:13 +00:00
|
|
|
KASSERT(cpu_vendor_id == CPU_VENDOR_INTEL,
|
2008-11-09 17:37:54 +00:00
|
|
|
("[intel,%d] Initializing non-intel processor", __LINE__));
|
|
|
|
|
2015-05-08 19:40:00 +00:00
|
|
|
PMCDBG1(MDP,INI,0, "intel-initialize cpuid=0x%x", cpu_id);
|
2008-11-09 17:37:54 +00:00
|
|
|
|
|
|
|
cputype = -1;
|
|
|
|
nclasses = 2;
|
2013-04-30 08:33:38 +00:00
|
|
|
error = 0;
|
2013-12-20 14:03:56 +00:00
|
|
|
verov = 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
|
|
|
model = ((cpu_id & 0xF0000) >> 12) | ((cpu_id & 0xF0) >> 4);
|
2013-12-20 14:03:56 +00:00
|
|
|
stepping = cpu_id & 0xF;
|
- 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
|
|
|
|
2008-11-09 17:37:54 +00:00
|
|
|
switch (cpu_id & 0xF00) {
|
|
|
|
#if defined(__i386__)
|
|
|
|
case 0x500: /* Pentium family processors */
|
|
|
|
cputype = PMC_CPU_INTEL_P5;
|
|
|
|
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
|
|
|
#endif
|
2008-11-09 17:37:54 +00:00
|
|
|
case 0x600: /* Pentium Pro, Celeron, Pentium II & III */
|
- 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
|
|
|
switch (model) {
|
|
|
|
#if defined(__i386__)
|
2008-11-09 17:37:54 +00:00
|
|
|
case 0x1:
|
|
|
|
cputype = PMC_CPU_INTEL_P6;
|
|
|
|
break;
|
|
|
|
case 0x3: case 0x5:
|
|
|
|
cputype = PMC_CPU_INTEL_PII;
|
|
|
|
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
|
|
|
case 0x6: case 0x16:
|
2008-11-09 17:37:54 +00:00
|
|
|
cputype = PMC_CPU_INTEL_CL;
|
|
|
|
break;
|
|
|
|
case 0x7: case 0x8: case 0xA: case 0xB:
|
|
|
|
cputype = PMC_CPU_INTEL_PIII;
|
|
|
|
break;
|
|
|
|
case 0x9: case 0xD:
|
|
|
|
cputype = PMC_CPU_INTEL_PM;
|
|
|
|
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
|
|
|
#endif
|
|
|
|
case 0xE:
|
|
|
|
cputype = PMC_CPU_INTEL_CORE;
|
|
|
|
break;
|
|
|
|
case 0xF:
|
2013-12-20 14:03:56 +00:00
|
|
|
/* Per Intel document 315338-020. */
|
|
|
|
if (stepping == 0x7) {
|
|
|
|
cputype = PMC_CPU_INTEL_CORE;
|
|
|
|
verov = 1;
|
|
|
|
} else {
|
|
|
|
cputype = PMC_CPU_INTEL_CORE2;
|
|
|
|
nclasses = 3;
|
|
|
|
}
|
- 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;
|
|
|
|
case 0x17:
|
|
|
|
cputype = PMC_CPU_INTEL_CORE2EXTREME;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
|
|
|
case 0x1C: /* Per Intel document 320047-002. */
|
|
|
|
cputype = PMC_CPU_INTEL_ATOM;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2009-01-27 07:29:37 +00:00
|
|
|
case 0x1A:
|
2013-04-03 21:34:35 +00:00
|
|
|
case 0x1E: /*
|
|
|
|
* Per Intel document 253669-032 9/2009,
|
|
|
|
* pages A-2 and A-57
|
|
|
|
*/
|
|
|
|
case 0x1F: /*
|
|
|
|
* Per Intel document 253669-032 9/2009,
|
|
|
|
* pages A-2 and A-57
|
|
|
|
*/
|
2009-01-27 07:29:37 +00:00
|
|
|
cputype = PMC_CPU_INTEL_COREI7;
|
2010-04-02 13:23:49 +00:00
|
|
|
nclasses = 5;
|
|
|
|
break;
|
2014-06-04 16:06:38 +00:00
|
|
|
case 0x2E:
|
|
|
|
cputype = PMC_CPU_INTEL_NEHALEM_EX;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2010-04-02 13:23:49 +00:00
|
|
|
case 0x25: /* Per Intel document 253669-033US 12/2009. */
|
|
|
|
case 0x2C: /* Per Intel document 253669-033US 12/2009. */
|
|
|
|
cputype = PMC_CPU_INTEL_WESTMERE;
|
|
|
|
nclasses = 5;
|
2009-01-27 07:29:37 +00:00
|
|
|
break;
|
2014-06-04 16:06:38 +00:00
|
|
|
case 0x2F: /* Westmere-EX, seen in wild */
|
|
|
|
cputype = PMC_CPU_INTEL_WESTMERE_EX;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2012-03-01 21:23:26 +00:00
|
|
|
case 0x2A: /* Per Intel document 253669-039US 05/2011. */
|
|
|
|
cputype = PMC_CPU_INTEL_SANDYBRIDGE;
|
|
|
|
nclasses = 5;
|
|
|
|
break;
|
2012-10-19 17:01:27 +00:00
|
|
|
case 0x2D: /* Per Intel document 253669-044US 08/2012. */
|
|
|
|
cputype = PMC_CPU_INTEL_SANDYBRIDGE_XEON;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2012-09-06 13:54:01 +00:00
|
|
|
case 0x3A: /* Per Intel document 253669-043US 05/2012. */
|
|
|
|
cputype = PMC_CPU_INTEL_IVYBRIDGE;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2013-01-31 22:09:53 +00:00
|
|
|
case 0x3E: /* Per Intel document 325462-045US 01/2013. */
|
|
|
|
cputype = PMC_CPU_INTEL_IVYBRIDGE_XEON;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2015-04-05 05:14:20 +00:00
|
|
|
case 0x3D:
|
|
|
|
cputype = PMC_CPU_INTEL_BROADWELL;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2015-01-14 12:46:58 +00:00
|
|
|
case 0x3F: /* Per Intel document 325462-045US 09/2014. */
|
|
|
|
case 0x46: /* Per Intel document 325462-045US 09/2014. */
|
|
|
|
/* Should 46 be XEON. probably its own? */
|
|
|
|
cputype = PMC_CPU_INTEL_HASWELL_XEON;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2013-03-28 19:15:54 +00:00
|
|
|
case 0x3C: /* Per Intel document 325462-045US 01/2013. */
|
2015-01-14 12:46:58 +00:00
|
|
|
case 0x45: /* Per Intel document 325462-045US 09/2014. */
|
2013-03-28 19:15:54 +00:00
|
|
|
cputype = PMC_CPU_INTEL_HASWELL;
|
|
|
|
nclasses = 5;
|
|
|
|
break;
|
2014-03-20 20:51:08 +00:00
|
|
|
case 0x4D: /* Per Intel document 330061-001 01/2014. */
|
|
|
|
cputype = PMC_CPU_INTEL_ATOM_SILVERMONT;
|
|
|
|
nclasses = 3;
|
|
|
|
break;
|
2008-11-09 17:37:54 +00:00
|
|
|
}
|
|
|
|
break;
|
|
|
|
#if defined(__i386__) || defined(__amd64__)
|
|
|
|
case 0xF00: /* P4 */
|
|
|
|
if (model >= 0 && model <= 6) /* known models */
|
|
|
|
cputype = PMC_CPU_INTEL_PIV;
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
if ((int) cputype == -1) {
|
|
|
|
printf("pmc: Unknown Intel CPU.\n");
|
|
|
|
return (NULL);
|
|
|
|
}
|
|
|
|
|
2012-03-28 20:58:30 +00:00
|
|
|
/* Allocate base class and initialize machine dependent struct */
|
|
|
|
pmc_mdep = pmc_mdep_alloc(nclasses);
|
2008-11-09 17:37:54 +00:00
|
|
|
|
2013-04-03 21:34:35 +00:00
|
|
|
pmc_mdep->pmd_cputype = cputype;
|
2008-11-09 17:37:54 +00:00
|
|
|
pmc_mdep->pmd_switch_in = intel_switch_in;
|
|
|
|
pmc_mdep->pmd_switch_out = intel_switch_out;
|
|
|
|
|
|
|
|
ncpus = pmc_cpu_max();
|
2013-04-30 14:56:41 +00:00
|
|
|
error = pmc_tsc_initialize(pmc_mdep, ncpus);
|
|
|
|
if (error)
|
|
|
|
goto error;
|
2008-11-09 17:37:54 +00:00
|
|
|
switch (cputype) {
|
|
|
|
#if defined(__i386__) || defined(__amd64__)
|
- 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
|
|
|
/*
|
|
|
|
* Intel Core, Core 2 and Atom processors.
|
|
|
|
*/
|
|
|
|
case PMC_CPU_INTEL_ATOM:
|
2014-03-20 20:51:08 +00:00
|
|
|
case PMC_CPU_INTEL_ATOM_SILVERMONT:
|
2015-04-05 05:14:20 +00:00
|
|
|
case PMC_CPU_INTEL_BROADWELL:
|
- 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_CPU_INTEL_CORE:
|
|
|
|
case PMC_CPU_INTEL_CORE2:
|
2008-12-03 17:30:36 +00:00
|
|
|
case PMC_CPU_INTEL_CORE2EXTREME:
|
2009-01-27 07:29:37 +00:00
|
|
|
case PMC_CPU_INTEL_COREI7:
|
2014-06-04 16:06:38 +00:00
|
|
|
case PMC_CPU_INTEL_NEHALEM_EX:
|
2012-09-06 13:54:01 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE:
|
2012-03-01 21:23:26 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE:
|
2014-06-04 16:06:38 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE_EX:
|
2012-10-19 17:01:27 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE_XEON:
|
2013-01-31 22:09:53 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE_XEON:
|
2013-03-28 19:15:54 +00:00
|
|
|
case PMC_CPU_INTEL_HASWELL:
|
2015-01-14 12:46:58 +00:00
|
|
|
case PMC_CPU_INTEL_HASWELL_XEON:
|
2013-12-20 14:03:56 +00:00
|
|
|
error = pmc_core_initialize(pmc_mdep, ncpus, verov);
|
- 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;
|
2008-11-09 17:37:54 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Intel Pentium 4 Processors, and P4/EMT64 processors.
|
|
|
|
*/
|
|
|
|
|
|
|
|
case PMC_CPU_INTEL_PIV:
|
|
|
|
error = pmc_p4_initialize(pmc_mdep, ncpus);
|
|
|
|
break;
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#if defined(__i386__)
|
|
|
|
/*
|
|
|
|
* P6 Family Processors
|
|
|
|
*/
|
|
|
|
|
|
|
|
case PMC_CPU_INTEL_P6:
|
|
|
|
case PMC_CPU_INTEL_CL:
|
|
|
|
case PMC_CPU_INTEL_PII:
|
|
|
|
case PMC_CPU_INTEL_PIII:
|
|
|
|
case PMC_CPU_INTEL_PM:
|
|
|
|
error = pmc_p6_initialize(pmc_mdep, ncpus);
|
|
|
|
break;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Intel Pentium PMCs.
|
|
|
|
*/
|
|
|
|
|
|
|
|
case PMC_CPU_INTEL_P5:
|
|
|
|
error = pmc_p5_initialize(pmc_mdep, ncpus);
|
|
|
|
break;
|
|
|
|
#endif
|
|
|
|
|
|
|
|
default:
|
|
|
|
KASSERT(0, ("[intel,%d] Unknown CPU type", __LINE__));
|
|
|
|
}
|
|
|
|
|
2013-04-30 14:56:41 +00:00
|
|
|
if (error) {
|
|
|
|
pmc_tsc_finalize(pmc_mdep);
|
2012-03-27 18:22:14 +00:00
|
|
|
goto error;
|
2013-04-30 14:56:41 +00:00
|
|
|
}
|
2012-03-27 18:22:14 +00:00
|
|
|
|
2010-04-02 13:23:49 +00:00
|
|
|
/*
|
|
|
|
* Init the uncore class.
|
|
|
|
*/
|
|
|
|
#if defined(__i386__) || defined(__amd64__)
|
|
|
|
switch (cputype) {
|
|
|
|
/*
|
|
|
|
* Intel Corei7 and Westmere processors.
|
|
|
|
*/
|
|
|
|
case PMC_CPU_INTEL_COREI7:
|
2013-03-28 19:15:54 +00:00
|
|
|
case PMC_CPU_INTEL_HASWELL:
|
2012-03-01 21:23:26 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE:
|
2015-04-05 05:14:20 +00:00
|
|
|
case PMC_CPU_INTEL_BROADWELL:
|
2010-04-02 13:23:49 +00:00
|
|
|
error = pmc_uncore_initialize(pmc_mdep, ncpus);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
#endif
|
2008-11-09 17:37:54 +00:00
|
|
|
error:
|
|
|
|
if (error) {
|
2013-04-30 08:33:38 +00:00
|
|
|
pmc_mdep_free(pmc_mdep);
|
2008-11-09 17:37:54 +00:00
|
|
|
pmc_mdep = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
return (pmc_mdep);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
pmc_intel_finalize(struct pmc_mdep *md)
|
|
|
|
{
|
|
|
|
pmc_tsc_finalize(md);
|
|
|
|
|
|
|
|
switch (md->pmd_cputype) {
|
|
|
|
#if defined(__i386__) || defined(__amd64__)
|
- 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_CPU_INTEL_ATOM:
|
2014-03-20 20:51:08 +00:00
|
|
|
case PMC_CPU_INTEL_ATOM_SILVERMONT:
|
2015-04-05 05:14:20 +00:00
|
|
|
case PMC_CPU_INTEL_BROADWELL:
|
- 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_CPU_INTEL_CORE:
|
|
|
|
case PMC_CPU_INTEL_CORE2:
|
2008-12-03 17:30:36 +00:00
|
|
|
case PMC_CPU_INTEL_CORE2EXTREME:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_COREI7:
|
2014-06-04 16:06:38 +00:00
|
|
|
case PMC_CPU_INTEL_NEHALEM_EX:
|
2013-03-28 19:15:54 +00:00
|
|
|
case PMC_CPU_INTEL_HASWELL:
|
2015-01-14 12:46:58 +00:00
|
|
|
case PMC_CPU_INTEL_HASWELL_XEON:
|
2012-09-06 13:54:01 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE:
|
2012-03-01 21:23:26 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE:
|
2014-06-04 16:06:38 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE_EX:
|
2012-10-19 17:01:27 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE_XEON:
|
2013-01-31 22:09:53 +00:00
|
|
|
case PMC_CPU_INTEL_IVYBRIDGE_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
|
|
|
pmc_core_finalize(md);
|
|
|
|
break;
|
|
|
|
|
2008-11-09 17:37:54 +00:00
|
|
|
case PMC_CPU_INTEL_PIV:
|
|
|
|
pmc_p4_finalize(md);
|
|
|
|
break;
|
|
|
|
#endif
|
|
|
|
#if defined(__i386__)
|
|
|
|
case PMC_CPU_INTEL_P6:
|
|
|
|
case PMC_CPU_INTEL_CL:
|
|
|
|
case PMC_CPU_INTEL_PII:
|
|
|
|
case PMC_CPU_INTEL_PIII:
|
|
|
|
case PMC_CPU_INTEL_PM:
|
|
|
|
pmc_p6_finalize(md);
|
|
|
|
break;
|
|
|
|
case PMC_CPU_INTEL_P5:
|
|
|
|
pmc_p5_finalize(md);
|
|
|
|
break;
|
|
|
|
#endif
|
|
|
|
default:
|
|
|
|
KASSERT(0, ("[intel,%d] unknown CPU type", __LINE__));
|
|
|
|
}
|
2010-04-02 13:23:49 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Uncore.
|
|
|
|
*/
|
|
|
|
#if defined(__i386__) || defined(__amd64__)
|
|
|
|
switch (md->pmd_cputype) {
|
2015-04-05 05:14:20 +00:00
|
|
|
case PMC_CPU_INTEL_BROADWELL:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_COREI7:
|
2013-03-28 19:15:54 +00:00
|
|
|
case PMC_CPU_INTEL_HASWELL:
|
2012-03-01 21:23:26 +00:00
|
|
|
case PMC_CPU_INTEL_SANDYBRIDGE:
|
2010-04-02 13:23:49 +00:00
|
|
|
case PMC_CPU_INTEL_WESTMERE:
|
|
|
|
pmc_uncore_finalize(md);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
#endif
|
2008-11-09 17:37:54 +00:00
|
|
|
}
|