2005-04-19 04:01:25 +00:00
|
|
|
/*-
|
2008-09-15 06:47:52 +00:00
|
|
|
* Copyright (c) 2003-2005,2008 Joseph Koshy
|
2007-12-07 08:20:17 +00:00
|
|
|
* Copyright (c) 2007 The FreeBSD Foundation
|
2005-04-19 04:01:25 +00:00
|
|
|
* All rights reserved.
|
|
|
|
*
|
2007-12-07 08:20:17 +00:00
|
|
|
* Portions of this software were developed by A. Joseph Koshy under
|
|
|
|
* sponsorship from the FreeBSD Foundation and Google, Inc.
|
|
|
|
*
|
2005-04-19 04:01:25 +00:00
|
|
|
* 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.
|
|
|
|
*
|
|
|
|
* $FreeBSD$
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef _MACHINE_PMC_MDEP_H
|
|
|
|
#define _MACHINE_PMC_MDEP_H 1
|
|
|
|
|
2008-11-09 17:37:54 +00:00
|
|
|
#ifdef _KERNEL
|
|
|
|
struct pmc_mdep;
|
|
|
|
#endif
|
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
/*
|
|
|
|
* On the i386 platform we support the following PMCs.
|
|
|
|
*
|
2008-11-09 17:37:54 +00:00
|
|
|
* TSC The timestamp counter
|
2005-06-09 19:45:09 +00:00
|
|
|
* K7 AMD Athlon XP/MP and other 32 bit processors.
|
|
|
|
* K8 AMD Athlon64 and Opteron PMCs in 32 bit mode.
|
|
|
|
* PIV Intel P4/HTT and P4/EMT64
|
|
|
|
* PPRO Intel Pentium Pro, Pentium-II, Pentium-III, Celeron and
|
|
|
|
* Pentium-M processors
|
|
|
|
* PENTIUM Intel Pentium MMX.
|
2008-11-09 17:37:54 +00:00
|
|
|
* IAP Intel Core/Core2/Atom programmable PMCs.
|
|
|
|
* IAF Intel fixed-function PMCs.
|
2005-06-09 19:45:09 +00:00
|
|
|
*/
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
#include <dev/hwpmc/hwpmc_amd.h> /* K7 and K8 */
|
- 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 <dev/hwpmc/hwpmc_core.h>
|
2005-06-09 19:45:09 +00:00
|
|
|
#include <dev/hwpmc/hwpmc_piv.h>
|
|
|
|
#include <dev/hwpmc/hwpmc_ppro.h>
|
|
|
|
#include <dev/hwpmc/hwpmc_pentium.h>
|
2008-11-09 17:37:54 +00:00
|
|
|
#include <dev/hwpmc/hwpmc_tsc.h>
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Intel processors implementing V2 and later of the Intel performance
|
|
|
|
* measurement architecture have PMCs of the following classes: TSC,
|
|
|
|
* IAF and IAP.
|
|
|
|
*/
|
|
|
|
#define PMC_MDEP_CLASS_INDEX_TSC 0
|
|
|
|
#define PMC_MDEP_CLASS_INDEX_K7 1
|
|
|
|
#define PMC_MDEP_CLASS_INDEX_K8 1
|
|
|
|
#define PMC_MDEP_CLASS_INDEX_P4 1
|
|
|
|
#define PMC_MDEP_CLASS_INDEX_P5 1
|
|
|
|
#define PMC_MDEP_CLASS_INDEX_P6 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
|
|
|
#define PMC_MDEP_CLASS_INDEX_IAP 1
|
|
|
|
#define PMC_MDEP_CLASS_INDEX_IAF 2
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
/*
|
|
|
|
* Architecture specific extensions to <sys/pmc.h> structures.
|
|
|
|
*/
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
union pmc_md_op_pmcallocate {
|
|
|
|
struct pmc_md_amd_op_pmcallocate pm_amd;
|
- 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_md_iaf_op_pmcallocate pm_iaf;
|
|
|
|
struct pmc_md_iap_op_pmcallocate pm_iap;
|
2005-06-09 19:45:09 +00:00
|
|
|
struct pmc_md_p4_op_pmcallocate pm_p4;
|
- 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_md_pentium_op_pmcallocate pm_pentium;
|
|
|
|
struct pmc_md_ppro_op_pmcallocate pm_ppro;
|
2005-06-09 19:45:09 +00:00
|
|
|
uint64_t __pad[4];
|
|
|
|
};
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
/* Logging */
|
|
|
|
#define PMCLOG_READADDR PMCLOG_READ32
|
|
|
|
#define PMCLOG_EMITADDR PMCLOG_EMIT32
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
#ifdef _KERNEL
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
/* MD extension for 'struct pmc' */
|
|
|
|
union pmc_md_pmc {
|
|
|
|
struct pmc_md_amd_pmc pm_amd;
|
- 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_md_iaf_pmc pm_iaf;
|
|
|
|
struct pmc_md_iap_pmc pm_iap;
|
2005-06-09 19:45:09 +00:00
|
|
|
struct pmc_md_p4_pmc pm_p4;
|
- 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_md_pentium_pmc pm_pentium;
|
|
|
|
struct pmc_md_ppro_pmc pm_ppro;
|
2005-06-09 19:45:09 +00:00
|
|
|
};
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2005-06-09 19:45:09 +00:00
|
|
|
struct pmc;
|
2008-11-09 17:37:54 +00:00
|
|
|
struct pmc_mdep;
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2007-12-07 08:20:17 +00:00
|
|
|
#define PMC_TRAPFRAME_TO_PC(TF) ((TF)->tf_eip)
|
|
|
|
#define PMC_TRAPFRAME_TO_FP(TF) ((TF)->tf_ebp)
|
2008-09-15 06:47:52 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* The layout of the stack frame on entry into the NMI handler depends on
|
|
|
|
* whether a privilege level change (and consequent stack switch) was
|
|
|
|
* required for entry.
|
|
|
|
*
|
|
|
|
* When processing an interrupt when in user mode, the processor switches
|
|
|
|
* stacks, and saves the user mode stack pointer on the kernel stack. The
|
|
|
|
* user mode stack pointer is then available to the interrupt handler
|
|
|
|
* at frame->tf_esp.
|
|
|
|
*
|
|
|
|
* When processing an interrupt while in kernel mode, the processor
|
|
|
|
* continues to use the existing (kernel) stack. Therefore we determine
|
|
|
|
* the stack pointer for the interrupted kernel procedure by adding an
|
|
|
|
* offset to the current frame pointer.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define PMC_TRAPFRAME_TO_USER_SP(TF) ((TF)->tf_esp)
|
|
|
|
#define PMC_TRAPFRAME_TO_KERNEL_SP(TF) ((uintptr_t) &((TF)->tf_esp))
|
2007-12-07 08:20:17 +00:00
|
|
|
|
|
|
|
#define PMC_IN_KERNEL_STACK(S,START,END) \
|
|
|
|
((S) >= (START) && (S) < (END))
|
|
|
|
#define PMC_IN_KERNEL(va) (((va) >= USRSTACK) && \
|
|
|
|
((va) < VM_MAX_KERNEL_ADDRESS))
|
|
|
|
|
|
|
|
#define PMC_IN_USERSPACE(va) ((va) <= VM_MAXUSER_ADDRESS)
|
|
|
|
|
|
|
|
#define PMC_IN_TRAP_HANDLER(PC) \
|
|
|
|
((PC) >= (uintptr_t) start_exceptions && \
|
|
|
|
(PC) < (uintptr_t) end_exceptions)
|
|
|
|
|
|
|
|
#define PMC_AT_FUNCTION_PROLOGUE_PUSH_BP(I) \
|
2008-09-05 14:45:56 +00:00
|
|
|
(((I) & 0x00ffffff) == 0xe58955) /* pushl %ebp; movl %esp,%ebp */
|
2007-12-07 08:20:17 +00:00
|
|
|
#define PMC_AT_FUNCTION_PROLOGUE_MOV_SP_BP(I) \
|
2008-09-05 14:45:56 +00:00
|
|
|
(((I) & 0x0000ffff) == 0xe589) /* movl %esp,%ebp */
|
2007-12-07 08:20:17 +00:00
|
|
|
#define PMC_AT_FUNCTION_EPILOGUE_RET(I) \
|
|
|
|
(((I) & 0xFF) == 0xC3) /* ret */
|
|
|
|
|
2005-04-19 04:01:25 +00:00
|
|
|
/*
|
|
|
|
* Prototypes
|
|
|
|
*/
|
|
|
|
|
2007-12-07 08:20:17 +00:00
|
|
|
void start_exceptions(void), end_exceptions(void);
|
2005-06-09 19:45:09 +00:00
|
|
|
void pmc_x86_lapic_enable_pmc_interrupt(void);
|
2005-04-19 04:01:25 +00:00
|
|
|
|
2008-11-09 17:37:54 +00:00
|
|
|
struct pmc_mdep *pmc_amd_initialize(void);
|
|
|
|
void pmc_amd_finalize(struct pmc_mdep *_md);
|
|
|
|
struct pmc_mdep *pmc_intel_initialize(void);
|
|
|
|
void pmc_intel_finalize(struct pmc_mdep *_md);
|
|
|
|
|
2005-04-19 04:01:25 +00:00
|
|
|
#endif /* _KERNEL */
|
|
|
|
#endif /* _MACHINE_PMC_MDEP_H */
|