1994-05-24 10:09:53 +00:00
|
|
|
/*-
|
|
|
|
* Copyright (c) 1982, 1986, 1993
|
|
|
|
* The Regents of the University of California. 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.
|
|
|
|
* 3. All advertising materials mentioning features or use of this software
|
|
|
|
* must display the following acknowledgement:
|
|
|
|
* This product includes software developed by the University of
|
|
|
|
* California, Berkeley and its contributors.
|
|
|
|
* 4. Neither the name of the University nor the names of its contributors
|
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
* without specific prior written permission.
|
|
|
|
*
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS 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 REGENTS 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.
|
|
|
|
*
|
|
|
|
* @(#)subr_prof.c 8.3 (Berkeley) 9/23/93
|
1999-08-28 01:08:13 +00:00
|
|
|
* $FreeBSD$
|
1994-05-24 10:09:53 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
#include <sys/param.h>
|
|
|
|
#include <sys/systm.h>
|
1995-11-12 06:43:28 +00:00
|
|
|
#include <sys/sysproto.h>
|
1999-10-12 02:54:23 +00:00
|
|
|
#include <sys/kernel.h>
|
2001-05-01 08:13:21 +00:00
|
|
|
#include <sys/lock.h>
|
|
|
|
#include <sys/mutex.h>
|
1994-05-24 10:09:53 +00:00
|
|
|
#include <sys/proc.h>
|
1995-12-06 23:37:44 +00:00
|
|
|
#include <sys/resourcevar.h>
|
1999-10-12 02:54:23 +00:00
|
|
|
#include <sys/sysctl.h>
|
1995-03-16 18:17:34 +00:00
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
#include <machine/cpu.h>
|
|
|
|
|
|
|
|
#ifdef GPROF
|
|
|
|
#include <sys/malloc.h>
|
|
|
|
#include <sys/gmon.h>
|
1999-05-06 09:44:57 +00:00
|
|
|
#undef MCOUNT
|
1994-05-24 10:09:53 +00:00
|
|
|
|
1997-10-12 20:26:33 +00:00
|
|
|
static MALLOC_DEFINE(M_GPROF, "gprof", "kernel profiling buffer");
|
1997-10-11 18:31:40 +00:00
|
|
|
|
2002-03-19 21:25:46 +00:00
|
|
|
static void kmstartup(void *);
|
1995-08-28 09:19:25 +00:00
|
|
|
SYSINIT(kmem, SI_SUB_KPROF, SI_ORDER_FIRST, kmstartup, NULL)
|
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
struct gmonparam _gmonparam = { GMON_PROF_OFF };
|
|
|
|
|
1996-10-17 19:32:31 +00:00
|
|
|
#ifdef GUPROF
|
1999-05-06 09:44:57 +00:00
|
|
|
#include <machine/asmacros.h>
|
|
|
|
|
1996-10-17 19:32:31 +00:00
|
|
|
void
|
|
|
|
nullfunc_loop_profiled()
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < CALIB_SCALE; i++)
|
|
|
|
nullfunc_profiled();
|
|
|
|
}
|
|
|
|
|
1996-12-13 12:59:28 +00:00
|
|
|
#define nullfunc_loop_profiled_end nullfunc_profiled /* XXX */
|
|
|
|
|
1996-10-17 19:32:31 +00:00
|
|
|
void
|
|
|
|
nullfunc_profiled()
|
|
|
|
{
|
|
|
|
}
|
|
|
|
#endif /* GUPROF */
|
|
|
|
|
2001-10-30 15:04:57 +00:00
|
|
|
/*
|
|
|
|
* Update the histograms to support extending the text region arbitrarily.
|
|
|
|
* This is done slightly naively (no sparse regions), so will waste slight
|
|
|
|
* amounts of memory, but will overall work nicely enough to allow profiling
|
|
|
|
* of KLDs.
|
|
|
|
*/
|
|
|
|
void
|
|
|
|
kmupetext(uintfptr_t nhighpc)
|
|
|
|
{
|
|
|
|
struct gmonparam np; /* slightly large */
|
|
|
|
struct gmonparam *p = &_gmonparam;
|
|
|
|
char *cp;
|
|
|
|
|
|
|
|
GIANT_REQUIRED;
|
|
|
|
bcopy(p, &np, sizeof(*p));
|
|
|
|
np.highpc = ROUNDUP(nhighpc, HISTFRACTION * sizeof(HISTCOUNTER));
|
|
|
|
if (np.highpc <= p->highpc)
|
|
|
|
return;
|
|
|
|
np.textsize = np.highpc - p->lowpc;
|
|
|
|
np.kcountsize = np.textsize / HISTFRACTION;
|
|
|
|
np.hashfraction = HASHFRACTION;
|
|
|
|
np.fromssize = np.textsize / HASHFRACTION;
|
|
|
|
np.tolimit = np.textsize * ARCDENSITY / 100;
|
|
|
|
if (np.tolimit < MINARCS)
|
|
|
|
np.tolimit = MINARCS;
|
|
|
|
else if (np.tolimit > MAXARCS)
|
|
|
|
np.tolimit = MAXARCS;
|
|
|
|
np.tossize = np.tolimit * sizeof(struct tostruct);
|
|
|
|
cp = malloc(np.kcountsize + np.fromssize + np.tossize,
|
2003-01-21 08:56:16 +00:00
|
|
|
M_GPROF, 0);
|
2001-10-30 15:04:57 +00:00
|
|
|
/*
|
|
|
|
* Check for something else extending highpc while we slept.
|
|
|
|
*/
|
|
|
|
if (np.highpc <= p->highpc) {
|
|
|
|
free(cp, M_GPROF);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
np.tos = (struct tostruct *)cp;
|
|
|
|
cp += np.tossize;
|
|
|
|
np.kcount = (HISTCOUNTER *)cp;
|
|
|
|
cp += np.kcountsize;
|
|
|
|
np.froms = (u_short *)cp;
|
|
|
|
#ifdef GUPROF
|
|
|
|
/* Reinitialize pointers to overhead counters. */
|
|
|
|
np.cputime_count = &KCOUNT(&np, PC_TO_I(&np, cputime));
|
|
|
|
np.mcount_count = &KCOUNT(&np, PC_TO_I(&np, mcount));
|
|
|
|
np.mexitcount_count = &KCOUNT(&np, PC_TO_I(&np, mexitcount));
|
|
|
|
#endif
|
2001-12-18 00:27:18 +00:00
|
|
|
critical_enter();
|
2001-10-30 15:04:57 +00:00
|
|
|
bcopy(p->tos, np.tos, p->tossize);
|
|
|
|
bzero((char *)np.tos + p->tossize, np.tossize - p->tossize);
|
|
|
|
bcopy(p->kcount, np.kcount, p->kcountsize);
|
|
|
|
bzero((char *)np.kcount + p->kcountsize, np.kcountsize -
|
|
|
|
p->kcountsize);
|
|
|
|
bcopy(p->froms, np.froms, p->fromssize);
|
|
|
|
bzero((char *)np.froms + p->fromssize, np.fromssize - p->fromssize);
|
|
|
|
cp = (char *)p->tos;
|
|
|
|
bcopy(&np, p, sizeof(*p));
|
2001-12-18 00:27:18 +00:00
|
|
|
critical_exit();
|
2001-10-30 15:04:57 +00:00
|
|
|
free(cp, M_GPROF);
|
|
|
|
}
|
|
|
|
|
1995-08-29 03:09:14 +00:00
|
|
|
static void
|
1995-12-02 17:11:20 +00:00
|
|
|
kmstartup(dummy)
|
|
|
|
void *dummy;
|
1994-05-24 10:09:53 +00:00
|
|
|
{
|
|
|
|
char *cp;
|
|
|
|
struct gmonparam *p = &_gmonparam;
|
1995-12-29 15:30:05 +00:00
|
|
|
#ifdef GUPROF
|
1996-10-17 19:32:31 +00:00
|
|
|
int cputime_overhead;
|
|
|
|
int empty_loop_time;
|
1995-12-29 15:30:05 +00:00
|
|
|
int i;
|
1996-10-17 19:32:31 +00:00
|
|
|
int mcount_overhead;
|
|
|
|
int mexitcount_overhead;
|
|
|
|
int nullfunc_loop_overhead;
|
|
|
|
int nullfunc_loop_profiled_time;
|
1998-07-14 05:09:48 +00:00
|
|
|
uintfptr_t tmp_addr;
|
2000-12-07 22:38:22 +00:00
|
|
|
#endif
|
1995-12-29 15:30:05 +00:00
|
|
|
|
1994-05-24 10:09:53 +00:00
|
|
|
/*
|
|
|
|
* Round lowpc and highpc to multiples of the density we're using
|
|
|
|
* so the rest of the scaling (here and in gprof) stays in ints.
|
|
|
|
*/
|
1995-01-29 03:03:23 +00:00
|
|
|
p->lowpc = ROUNDDOWN((u_long)btext, HISTFRACTION * sizeof(HISTCOUNTER));
|
1994-05-24 10:09:53 +00:00
|
|
|
p->highpc = ROUNDUP((u_long)etext, HISTFRACTION * sizeof(HISTCOUNTER));
|
|
|
|
p->textsize = p->highpc - p->lowpc;
|
1996-10-17 19:32:31 +00:00
|
|
|
printf("Profiling kernel, textsize=%lu [%x..%x]\n",
|
1994-05-24 10:09:53 +00:00
|
|
|
p->textsize, p->lowpc, p->highpc);
|
|
|
|
p->kcountsize = p->textsize / HISTFRACTION;
|
|
|
|
p->hashfraction = HASHFRACTION;
|
|
|
|
p->fromssize = p->textsize / HASHFRACTION;
|
|
|
|
p->tolimit = p->textsize * ARCDENSITY / 100;
|
|
|
|
if (p->tolimit < MINARCS)
|
|
|
|
p->tolimit = MINARCS;
|
|
|
|
else if (p->tolimit > MAXARCS)
|
|
|
|
p->tolimit = MAXARCS;
|
|
|
|
p->tossize = p->tolimit * sizeof(struct tostruct);
|
|
|
|
cp = (char *)malloc(p->kcountsize + p->fromssize + p->tossize,
|
2003-01-21 08:56:16 +00:00
|
|
|
M_GPROF, M_ZERO);
|
1994-05-24 10:09:53 +00:00
|
|
|
p->tos = (struct tostruct *)cp;
|
|
|
|
cp += p->tossize;
|
1995-12-29 15:30:05 +00:00
|
|
|
p->kcount = (HISTCOUNTER *)cp;
|
1994-05-24 10:09:53 +00:00
|
|
|
cp += p->kcountsize;
|
|
|
|
p->froms = (u_short *)cp;
|
1995-12-29 15:30:05 +00:00
|
|
|
|
|
|
|
#ifdef GUPROF
|
1996-10-17 19:32:31 +00:00
|
|
|
/* Initialize pointers to overhead counters. */
|
1995-12-29 15:30:05 +00:00
|
|
|
p->cputime_count = &KCOUNT(p, PC_TO_I(p, cputime));
|
|
|
|
p->mcount_count = &KCOUNT(p, PC_TO_I(p, mcount));
|
|
|
|
p->mexitcount_count = &KCOUNT(p, PC_TO_I(p, mexitcount));
|
|
|
|
|
|
|
|
/*
|
1996-10-17 19:32:31 +00:00
|
|
|
* Disable interrupts to avoid interference while we calibrate
|
|
|
|
* things.
|
1995-12-29 15:30:05 +00:00
|
|
|
*/
|
2001-12-18 00:27:18 +00:00
|
|
|
critical_enter();
|
1995-12-29 15:30:05 +00:00
|
|
|
|
1996-10-17 19:32:31 +00:00
|
|
|
/*
|
|
|
|
* Determine overheads.
|
|
|
|
* XXX this needs to be repeated for each useful timer/counter.
|
|
|
|
*/
|
|
|
|
cputime_overhead = 0;
|
|
|
|
startguprof(p);
|
1995-12-29 15:30:05 +00:00
|
|
|
for (i = 0; i < CALIB_SCALE; i++)
|
1996-10-17 19:32:31 +00:00
|
|
|
cputime_overhead += cputime();
|
|
|
|
|
|
|
|
empty_loop();
|
|
|
|
startguprof(p);
|
|
|
|
empty_loop();
|
|
|
|
empty_loop_time = cputime();
|
|
|
|
|
|
|
|
nullfunc_loop_profiled();
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Start profiling. There won't be any normal function calls since
|
|
|
|
* interrupts are disabled, but we will call the profiling routines
|
|
|
|
* directly to determine their overheads.
|
|
|
|
*/
|
|
|
|
p->state = GMON_PROF_HIRES;
|
|
|
|
|
|
|
|
startguprof(p);
|
|
|
|
nullfunc_loop_profiled();
|
1995-12-29 15:30:05 +00:00
|
|
|
|
1996-10-17 19:32:31 +00:00
|
|
|
startguprof(p);
|
1995-12-29 15:30:05 +00:00
|
|
|
for (i = 0; i < CALIB_SCALE; i++)
|
1998-05-01 16:40:21 +00:00
|
|
|
#if defined(__i386__) && __GNUC__ >= 2
|
1998-04-15 17:47:40 +00:00
|
|
|
__asm("pushl %0; call __mcount; popl %%ecx"
|
|
|
|
:
|
|
|
|
: "i" (profil)
|
|
|
|
: "ax", "bx", "cx", "dx", "memory");
|
2002-10-01 13:15:11 +00:00
|
|
|
#elif defined(lint)
|
1995-12-29 15:30:05 +00:00
|
|
|
#else
|
|
|
|
#error
|
|
|
|
#endif
|
1996-10-17 19:32:31 +00:00
|
|
|
mcount_overhead = KCOUNT(p, PC_TO_I(p, profil));
|
1995-12-29 15:30:05 +00:00
|
|
|
|
1996-10-17 19:32:31 +00:00
|
|
|
startguprof(p);
|
1995-12-29 15:30:05 +00:00
|
|
|
for (i = 0; i < CALIB_SCALE; i++)
|
1998-05-01 16:40:21 +00:00
|
|
|
#if defined(__i386__) && __GNUC__ >= 2
|
1999-05-06 09:44:57 +00:00
|
|
|
__asm("call " __XSTRING(HIDENAME(mexitcount)) "; 1:"
|
1998-04-15 17:47:40 +00:00
|
|
|
: : : "ax", "bx", "cx", "dx", "memory");
|
|
|
|
__asm("movl $1b,%0" : "=rm" (tmp_addr));
|
2002-10-01 13:15:11 +00:00
|
|
|
#elif defined(lint)
|
1995-12-29 15:30:05 +00:00
|
|
|
#else
|
|
|
|
#error
|
|
|
|
#endif
|
1996-12-13 12:59:28 +00:00
|
|
|
mexitcount_overhead = KCOUNT(p, PC_TO_I(p, tmp_addr));
|
1995-12-29 15:30:05 +00:00
|
|
|
|
|
|
|
p->state = GMON_PROF_OFF;
|
1996-10-17 19:32:31 +00:00
|
|
|
stopguprof(p);
|
|
|
|
|
2001-12-18 00:27:18 +00:00
|
|
|
critical_exit();
|
1995-12-29 15:30:05 +00:00
|
|
|
|
1996-10-17 19:32:31 +00:00
|
|
|
nullfunc_loop_profiled_time = 0;
|
1998-07-14 05:09:48 +00:00
|
|
|
for (tmp_addr = (uintfptr_t)nullfunc_loop_profiled;
|
|
|
|
tmp_addr < (uintfptr_t)nullfunc_loop_profiled_end;
|
1996-12-13 12:59:28 +00:00
|
|
|
tmp_addr += HISTFRACTION * sizeof(HISTCOUNTER))
|
|
|
|
nullfunc_loop_profiled_time += KCOUNT(p, PC_TO_I(p, tmp_addr));
|
1996-10-17 19:32:31 +00:00
|
|
|
#define CALIB_DOSCALE(count) (((count) + CALIB_SCALE / 3) / CALIB_SCALE)
|
|
|
|
#define c2n(count, freq) ((int)((count) * 1000000000LL / freq))
|
|
|
|
printf("cputime %d, empty_loop %d, nullfunc_loop_profiled %d, mcount %d, mexitcount %d\n",
|
|
|
|
CALIB_DOSCALE(c2n(cputime_overhead, p->profrate)),
|
|
|
|
CALIB_DOSCALE(c2n(empty_loop_time, p->profrate)),
|
|
|
|
CALIB_DOSCALE(c2n(nullfunc_loop_profiled_time, p->profrate)),
|
|
|
|
CALIB_DOSCALE(c2n(mcount_overhead, p->profrate)),
|
|
|
|
CALIB_DOSCALE(c2n(mexitcount_overhead, p->profrate)));
|
|
|
|
cputime_overhead -= empty_loop_time;
|
|
|
|
mcount_overhead -= empty_loop_time;
|
|
|
|
mexitcount_overhead -= empty_loop_time;
|
|
|
|
|
|
|
|
/*-
|
|
|
|
* Profiling overheads are determined by the times between the
|
|
|
|
* following events:
|
|
|
|
* MC1: mcount() is called
|
|
|
|
* MC2: cputime() (called from mcount()) latches the timer
|
|
|
|
* MC3: mcount() completes
|
|
|
|
* ME1: mexitcount() is called
|
|
|
|
* ME2: cputime() (called from mexitcount()) latches the timer
|
|
|
|
* ME3: mexitcount() completes.
|
|
|
|
* The times between the events vary slightly depending on instruction
|
|
|
|
* combination and cache misses, etc. Attempt to determine the
|
|
|
|
* minimum times. These can be subtracted from the profiling times
|
|
|
|
* without much risk of reducing the profiling times below what they
|
|
|
|
* would be when profiling is not configured. Abbreviate:
|
|
|
|
* ab = minimum time between MC1 and MC3
|
|
|
|
* a = minumum time between MC1 and MC2
|
|
|
|
* b = minimum time between MC2 and MC3
|
|
|
|
* cd = minimum time between ME1 and ME3
|
|
|
|
* c = minimum time between ME1 and ME2
|
|
|
|
* d = minimum time between ME2 and ME3.
|
|
|
|
* These satisfy the relations:
|
|
|
|
* ab <= mcount_overhead (just measured)
|
|
|
|
* a + b <= ab
|
|
|
|
* cd <= mexitcount_overhead (just measured)
|
|
|
|
* c + d <= cd
|
|
|
|
* a + d <= nullfunc_loop_profiled_time (just measured)
|
|
|
|
* a >= 0, b >= 0, c >= 0, d >= 0.
|
|
|
|
* Assume that ab and cd are equal to the minimums.
|
|
|
|
*/
|
|
|
|
p->cputime_overhead = CALIB_DOSCALE(cputime_overhead);
|
|
|
|
p->mcount_overhead = CALIB_DOSCALE(mcount_overhead - cputime_overhead);
|
|
|
|
p->mexitcount_overhead = CALIB_DOSCALE(mexitcount_overhead
|
|
|
|
- cputime_overhead);
|
|
|
|
nullfunc_loop_overhead = nullfunc_loop_profiled_time - empty_loop_time;
|
|
|
|
p->mexitcount_post_overhead = CALIB_DOSCALE((mcount_overhead
|
|
|
|
- nullfunc_loop_overhead)
|
|
|
|
/ 4);
|
|
|
|
p->mexitcount_pre_overhead = p->mexitcount_overhead
|
|
|
|
+ p->cputime_overhead
|
|
|
|
- p->mexitcount_post_overhead;
|
|
|
|
p->mcount_pre_overhead = CALIB_DOSCALE(nullfunc_loop_overhead)
|
|
|
|
- p->mexitcount_post_overhead;
|
|
|
|
p->mcount_post_overhead = p->mcount_overhead
|
|
|
|
+ p->cputime_overhead
|
|
|
|
- p->mcount_pre_overhead;
|
|
|
|
printf(
|
|
|
|
"Profiling overheads: mcount: %d+%d, %d+%d; mexitcount: %d+%d, %d+%d nsec\n",
|
|
|
|
c2n(p->cputime_overhead, p->profrate),
|
|
|
|
c2n(p->mcount_overhead, p->profrate),
|
|
|
|
c2n(p->mcount_pre_overhead, p->profrate),
|
|
|
|
c2n(p->mcount_post_overhead, p->profrate),
|
|
|
|
c2n(p->cputime_overhead, p->profrate),
|
|
|
|
c2n(p->mexitcount_overhead, p->profrate),
|
|
|
|
c2n(p->mexitcount_pre_overhead, p->profrate),
|
|
|
|
c2n(p->mexitcount_post_overhead, p->profrate));
|
|
|
|
printf(
|
|
|
|
"Profiling overheads: mcount: %d+%d, %d+%d; mexitcount: %d+%d, %d+%d cycles\n",
|
|
|
|
p->cputime_overhead, p->mcount_overhead,
|
|
|
|
p->mcount_pre_overhead, p->mcount_post_overhead,
|
|
|
|
p->cputime_overhead, p->mexitcount_overhead,
|
|
|
|
p->mexitcount_pre_overhead, p->mexitcount_post_overhead);
|
1995-12-29 15:30:05 +00:00
|
|
|
#endif /* GUPROF */
|
1994-05-24 10:09:53 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Return kernel profiling information.
|
|
|
|
*/
|
1995-11-20 12:42:39 +00:00
|
|
|
static int
|
2000-07-04 11:25:35 +00:00
|
|
|
sysctl_kern_prof(SYSCTL_HANDLER_ARGS)
|
1994-05-24 10:09:53 +00:00
|
|
|
{
|
1995-11-20 12:42:39 +00:00
|
|
|
int *name = (int *) arg1;
|
|
|
|
u_int namelen = arg2;
|
1994-05-24 10:09:53 +00:00
|
|
|
struct gmonparam *gp = &_gmonparam;
|
|
|
|
int error;
|
1995-12-29 15:30:05 +00:00
|
|
|
int state;
|
1994-05-24 10:09:53 +00:00
|
|
|
|
|
|
|
/* all sysctl names at this level are terminal */
|
|
|
|
if (namelen != 1)
|
|
|
|
return (ENOTDIR); /* overloaded */
|
|
|
|
|
|
|
|
switch (name[0]) {
|
|
|
|
case GPROF_STATE:
|
1995-12-29 15:30:05 +00:00
|
|
|
state = gp->state;
|
|
|
|
error = sysctl_handle_int(oidp, &state, 0, req);
|
1994-05-24 10:09:53 +00:00
|
|
|
if (error)
|
|
|
|
return (error);
|
1995-12-29 15:30:05 +00:00
|
|
|
if (!req->newptr)
|
|
|
|
return (0);
|
|
|
|
if (state == GMON_PROF_OFF) {
|
|
|
|
gp->state = state;
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
PROC_LOCK(&proc0);
|
1996-10-17 19:32:31 +00:00
|
|
|
stopprofclock(&proc0);
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
PROC_UNLOCK(&proc0);
|
1996-10-17 19:32:31 +00:00
|
|
|
stopguprof(gp);
|
1995-12-29 15:30:05 +00:00
|
|
|
} else if (state == GMON_PROF_ON) {
|
1996-10-17 19:32:31 +00:00
|
|
|
gp->state = GMON_PROF_OFF;
|
|
|
|
stopguprof(gp);
|
1995-12-29 15:30:05 +00:00
|
|
|
gp->profrate = profhz;
|
1994-05-24 10:09:53 +00:00
|
|
|
startprofclock(&proc0);
|
1996-10-17 19:32:31 +00:00
|
|
|
gp->state = state;
|
1995-12-29 15:30:05 +00:00
|
|
|
#ifdef GUPROF
|
|
|
|
} else if (state == GMON_PROF_HIRES) {
|
1996-10-17 19:32:31 +00:00
|
|
|
gp->state = GMON_PROF_OFF;
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
PROC_LOCK(&proc0);
|
1995-12-29 15:30:05 +00:00
|
|
|
stopprofclock(&proc0);
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
PROC_UNLOCK(&proc0);
|
1996-10-17 19:32:31 +00:00
|
|
|
startguprof(gp);
|
1995-12-29 15:30:05 +00:00
|
|
|
gp->state = state;
|
|
|
|
#endif
|
|
|
|
} else if (state != gp->state)
|
|
|
|
return (EINVAL);
|
1994-05-24 10:09:53 +00:00
|
|
|
return (0);
|
|
|
|
case GPROF_COUNT:
|
1995-11-20 12:42:39 +00:00
|
|
|
return (sysctl_handle_opaque(oidp,
|
|
|
|
gp->kcount, gp->kcountsize, req));
|
1994-05-24 10:09:53 +00:00
|
|
|
case GPROF_FROMS:
|
1995-11-20 12:42:39 +00:00
|
|
|
return (sysctl_handle_opaque(oidp,
|
|
|
|
gp->froms, gp->fromssize, req));
|
1994-05-24 10:09:53 +00:00
|
|
|
case GPROF_TOS:
|
1995-11-20 12:42:39 +00:00
|
|
|
return (sysctl_handle_opaque(oidp,
|
|
|
|
gp->tos, gp->tossize, req));
|
1994-05-24 10:09:53 +00:00
|
|
|
case GPROF_GMONPARAM:
|
1995-11-20 12:42:39 +00:00
|
|
|
return (sysctl_handle_opaque(oidp, gp, sizeof *gp, req));
|
1994-05-24 10:09:53 +00:00
|
|
|
default:
|
|
|
|
return (EOPNOTSUPP);
|
|
|
|
}
|
|
|
|
/* NOTREACHED */
|
|
|
|
}
|
1995-11-20 12:42:39 +00:00
|
|
|
|
|
|
|
SYSCTL_NODE(_kern, KERN_PROF, prof, CTLFLAG_RW, sysctl_kern_prof, "");
|
1994-05-24 10:09:53 +00:00
|
|
|
#endif /* GPROF */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Profiling system call.
|
|
|
|
*
|
|
|
|
* The scale factor is a fixed point number with 16 bits of fraction, so that
|
|
|
|
* 1.0 is represented as 0x10000. A scale factor of 0 turns off profiling.
|
|
|
|
*/
|
1995-11-12 06:43:28 +00:00
|
|
|
#ifndef _SYS_SYSPROTO_H_
|
1994-05-24 10:09:53 +00:00
|
|
|
struct profil_args {
|
|
|
|
caddr_t samples;
|
1998-09-05 14:30:11 +00:00
|
|
|
size_t size;
|
|
|
|
size_t offset;
|
1994-05-24 10:09:53 +00:00
|
|
|
u_int scale;
|
|
|
|
};
|
1995-11-12 06:43:28 +00:00
|
|
|
#endif
|
2001-09-01 05:47:58 +00:00
|
|
|
/*
|
|
|
|
* MPSAFE
|
|
|
|
*/
|
1994-05-24 10:09:53 +00:00
|
|
|
/* ARGSUSED */
|
1994-05-25 09:21:21 +00:00
|
|
|
int
|
2001-09-12 08:38:13 +00:00
|
|
|
profil(td, uap)
|
|
|
|
struct thread *td;
|
1994-05-24 10:09:53 +00:00
|
|
|
register struct profil_args *uap;
|
|
|
|
{
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
struct uprof *upp;
|
1994-05-24 10:09:53 +00:00
|
|
|
int s;
|
2001-09-01 05:47:58 +00:00
|
|
|
int error = 0;
|
|
|
|
|
|
|
|
mtx_lock(&Giant);
|
1994-05-24 10:09:53 +00:00
|
|
|
|
2001-09-01 05:47:58 +00:00
|
|
|
if (uap->scale > (1 << 16)) {
|
|
|
|
error = EINVAL;
|
|
|
|
goto done2;
|
|
|
|
}
|
1994-05-24 10:09:53 +00:00
|
|
|
if (uap->scale == 0) {
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
PROC_LOCK(td->td_proc);
|
2001-09-12 08:38:13 +00:00
|
|
|
stopprofclock(td->td_proc);
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
PROC_UNLOCK(td->td_proc);
|
2001-09-01 05:47:58 +00:00
|
|
|
goto done2;
|
1994-05-24 10:09:53 +00:00
|
|
|
}
|
2001-09-12 08:38:13 +00:00
|
|
|
upp = &td->td_proc->p_stats->p_prof;
|
1994-05-24 10:09:53 +00:00
|
|
|
|
|
|
|
/* Block profile interrupts while changing state. */
|
|
|
|
s = splstatclock();
|
|
|
|
upp->pr_off = uap->offset;
|
|
|
|
upp->pr_scale = uap->scale;
|
|
|
|
upp->pr_base = uap->samples;
|
|
|
|
upp->pr_size = uap->size;
|
2001-09-12 08:38:13 +00:00
|
|
|
startprofclock(td->td_proc);
|
1994-05-24 10:09:53 +00:00
|
|
|
splx(s);
|
|
|
|
|
2001-09-01 05:47:58 +00:00
|
|
|
done2:
|
|
|
|
mtx_unlock(&Giant);
|
|
|
|
return (error);
|
1994-05-24 10:09:53 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Scale is a fixed-point number with the binary point 16 bits
|
|
|
|
* into the value, and is <= 1.0. pc is at most 32 bits, so the
|
|
|
|
* intermediate result is at most 48 bits.
|
|
|
|
*/
|
|
|
|
#define PC_TO_INDEX(pc, prof) \
|
|
|
|
((int)(((u_quad_t)((pc) - (prof)->pr_off) * \
|
|
|
|
(u_quad_t)((prof)->pr_scale)) >> 16) & ~1)
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Collect user-level profiling statistics; called on a profiling tick,
|
|
|
|
* when a process is running in user-mode. This routine may be called
|
|
|
|
* from an interrupt context. We try to update the user profiling buffers
|
|
|
|
* cheaply with fuswintr() and suswintr(). If that fails, we revert to
|
|
|
|
* an AST that will vector us to trap() with a context in which copyin
|
|
|
|
* and copyout will work. Trap will then call addupc_task().
|
|
|
|
*
|
|
|
|
* Note that we may (rarely) not get around to the AST soon enough, and
|
|
|
|
* lose profile ticks when the next tick overwrites this one, but in this
|
|
|
|
* case the system is overloaded and the profile is probably already
|
|
|
|
* inaccurate.
|
|
|
|
*/
|
|
|
|
void
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
addupc_intr(struct thread *td, uintptr_t pc, u_int ticks)
|
1994-05-24 10:09:53 +00:00
|
|
|
{
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
struct uprof *prof;
|
|
|
|
caddr_t addr;
|
|
|
|
u_int i;
|
|
|
|
int v;
|
1994-05-24 10:09:53 +00:00
|
|
|
|
|
|
|
if (ticks == 0)
|
|
|
|
return;
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
prof = &td->td_proc->p_stats->p_prof;
|
1994-05-24 10:09:53 +00:00
|
|
|
if (pc < prof->pr_off ||
|
|
|
|
(i = PC_TO_INDEX(pc, prof)) >= prof->pr_size)
|
|
|
|
return; /* out of range; ignore */
|
|
|
|
|
|
|
|
addr = prof->pr_base + i;
|
|
|
|
if ((v = fuswintr(addr)) == -1 || suswintr(addr, v + ticks) == -1) {
|
2001-08-10 22:53:32 +00:00
|
|
|
mtx_lock_spin(&sched_lock);
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
td->td_praddr = pc;
|
|
|
|
td->td_prticks = ticks;
|
|
|
|
td->td_flags |= (TDF_OWEUPC | TDF_ASTPENDING);
|
2001-08-10 22:53:32 +00:00
|
|
|
mtx_unlock_spin(&sched_lock);
|
1994-05-24 10:09:53 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Much like before, but we can afford to take faults here. If the
|
|
|
|
* update fails, we simply turn off profiling.
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
* XXXKSE, don't use kse unless we got sched lock.
|
1994-05-24 10:09:53 +00:00
|
|
|
*/
|
1995-12-26 01:21:39 +00:00
|
|
|
void
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
addupc_task(struct thread *td, uintptr_t pc, u_int ticks)
|
1994-05-24 10:09:53 +00:00
|
|
|
{
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
struct proc *p = td->td_proc;
|
1994-05-24 10:09:53 +00:00
|
|
|
register struct uprof *prof;
|
|
|
|
register caddr_t addr;
|
|
|
|
register u_int i;
|
|
|
|
u_short v;
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
int stop = 0;
|
1994-05-24 10:09:53 +00:00
|
|
|
|
2001-12-18 09:06:10 +00:00
|
|
|
if (ticks == 0)
|
1994-05-24 10:09:53 +00:00
|
|
|
return;
|
|
|
|
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
PROC_LOCK(p);
|
|
|
|
mtx_lock_spin(&sched_lock);
|
|
|
|
if (!(p->p_sflag & PS_PROFIL)) {
|
|
|
|
mtx_unlock_spin(&sched_lock);
|
|
|
|
PROC_UNLOCK(p);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
p->p_profthreads++;
|
|
|
|
mtx_unlock_spin(&sched_lock);
|
|
|
|
PROC_UNLOCK(p);
|
1994-05-24 10:09:53 +00:00
|
|
|
prof = &p->p_stats->p_prof;
|
|
|
|
if (pc < prof->pr_off ||
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
(i = PC_TO_INDEX(pc, prof)) >= prof->pr_size) {
|
|
|
|
goto out;
|
|
|
|
}
|
1994-05-24 10:09:53 +00:00
|
|
|
|
|
|
|
addr = prof->pr_base + i;
|
2002-06-29 02:00:02 +00:00
|
|
|
if (copyin(addr, &v, sizeof(v)) == 0) {
|
1994-05-24 10:09:53 +00:00
|
|
|
v += ticks;
|
2002-06-29 02:00:02 +00:00
|
|
|
if (copyout(&v, addr, sizeof(v)) == 0)
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
stop = 1;
|
|
|
|
|
|
|
|
out:
|
|
|
|
PROC_LOCK(p);
|
|
|
|
if (--p->p_profthreads == 0) {
|
|
|
|
if (p->p_sflag & PS_STOPPROF) {
|
|
|
|
wakeup(&p->p_profthreads);
|
|
|
|
stop = 0;
|
|
|
|
}
|
1994-05-24 10:09:53 +00:00
|
|
|
}
|
Move UPCALL related data structure out of kse, introduce a new
data structure called kse_upcall to manage UPCALL. All KSE binding
and loaning code are gone.
A thread owns an upcall can collect all completed syscall contexts in
its ksegrp, turn itself into UPCALL mode, and takes those contexts back
to userland. Any thread without upcall structure has to export their
contexts and exit at user boundary.
Any thread running in user mode owns an upcall structure, when it enters
kernel, if the kse mailbox's current thread pointer is not NULL, then
when the thread is blocked in kernel, a new UPCALL thread is created and
the upcall structure is transfered to the new UPCALL thread. if the kse
mailbox's current thread pointer is NULL, then when a thread is blocked
in kernel, no UPCALL thread will be created.
Each upcall always has an owner thread. Userland can remove an upcall by
calling kse_exit, when all upcalls in ksegrp are removed, the group is
atomatically shutdown. An upcall owner thread also exits when process is
in exiting state. when an owner thread exits, the upcall it owns is also
removed.
KSE is a pure scheduler entity. it represents a virtual cpu. when a thread
is running, it always has a KSE associated with it. scheduler is free to
assign a KSE to thread according thread priority, if thread priority is changed,
KSE can be moved from one thread to another.
When a ksegrp is created, there is always N KSEs created in the group. the
N is the number of physical cpu in the current system. This makes it is
possible that even an userland UTS is single CPU safe, threads in kernel still
can execute on different cpu in parallel. Userland calls kse_create to add more
upcall structures into ksegrp to increase concurrent in userland itself, kernel
is not restricted by number of upcalls userland provides.
The code hasn't been tested under SMP by author due to lack of hardware.
Reviewed by: julian
2003-01-26 11:41:35 +00:00
|
|
|
if (stop)
|
|
|
|
stopprofclock(p);
|
|
|
|
PROC_UNLOCK(p);
|
1994-05-24 10:09:53 +00:00
|
|
|
}
|
2003-01-06 07:40:49 +00:00
|
|
|
|
|
|
|
#if defined(__i386__) && __GNUC__ >= 2
|
|
|
|
/*
|
|
|
|
* Support for "--test-coverage --profile-arcs" in GCC.
|
|
|
|
*
|
|
|
|
* We need to call all the functions in the .ctor section, in order
|
|
|
|
* to get all the counter-arrays strung into a list.
|
|
|
|
*
|
|
|
|
* XXX: the .ctors call __bb_init_func which is located in over in
|
|
|
|
* XXX: i386/i386/support.s for historical reasons. There is probably
|
|
|
|
* XXX: no reason for that to be assembler anymore, but doing it right
|
|
|
|
* XXX: in MI C code requires one to reverse-engineer the type-selection
|
|
|
|
* XXX: inside GCC. Have fun.
|
|
|
|
*
|
|
|
|
* XXX: Worrisome perspective: Calling the .ctors may make C++ in the
|
|
|
|
* XXX: kernel feasible. Don't.
|
|
|
|
*/
|
|
|
|
typedef void (*ctor_t)(void);
|
|
|
|
extern ctor_t _start_ctors, _stop_ctors;
|
|
|
|
|
|
|
|
static void
|
|
|
|
tcov_init(void *foo __unused)
|
|
|
|
{
|
|
|
|
ctor_t *p, q;
|
|
|
|
|
|
|
|
for (p = &_start_ctors; p < &_stop_ctors; p++) {
|
|
|
|
q = *p;
|
|
|
|
q();
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2003-01-07 19:09:10 +00:00
|
|
|
SYSINIT(tcov_init, SI_SUB_KPROF, SI_ORDER_SECOND, tcov_init, NULL)
|
2003-01-06 07:40:49 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* GCC contains magic to recognize calls to for instance execve() and
|
|
|
|
* puts in calls to this function to preserve the profile counters.
|
|
|
|
* XXX: Put zinging punchline here.
|
|
|
|
*/
|
|
|
|
void __bb_fork_func(void);
|
|
|
|
void
|
|
|
|
__bb_fork_func(void)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|