2004-01-12 04:00:35 +01:00
|
|
|
/*
|
2005-06-05 11:16:00 +02:00
|
|
|
* Copyright (c) 2004-2005 The Regents of The University of Michigan
|
2004-01-12 04:00:35 +01:00
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions are
|
|
|
|
* met: redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer;
|
|
|
|
* 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;
|
|
|
|
* neither the name of the copyright holders 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 COPYRIGHT HOLDERS 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 COPYRIGHT
|
|
|
|
* OWNER 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.
|
|
|
|
*/
|
|
|
|
|
2004-05-30 23:45:46 +02:00
|
|
|
/**
|
|
|
|
* @file
|
2004-07-31 06:55:05 +02:00
|
|
|
* This code loads the linux kernel, console, pal and patches certain
|
|
|
|
* functions. The symbol tables are loaded so that traces can show
|
|
|
|
* the executing function and we can skip functions. Various delay
|
|
|
|
* loops are skipped and their final values manually computed to speed
|
|
|
|
* up boot time.
|
2004-05-30 23:45:46 +02:00
|
|
|
*/
|
|
|
|
|
2004-11-16 02:30:51 +01:00
|
|
|
#include "base/loader/symtab.hh"
|
2004-01-12 04:00:35 +01:00
|
|
|
#include "cpu/exec_context.hh"
|
2005-06-05 02:50:10 +02:00
|
|
|
#include "cpu/base.hh"
|
2004-01-12 04:00:35 +01:00
|
|
|
#include "kern/linux/linux_events.hh"
|
|
|
|
#include "kern/linux/linux_system.hh"
|
2005-06-05 02:50:10 +02:00
|
|
|
#include "mem/functional/memory_control.hh"
|
|
|
|
#include "mem/functional/physical.hh"
|
2004-01-12 04:00:35 +01:00
|
|
|
#include "sim/builder.hh"
|
2004-02-06 00:23:16 +01:00
|
|
|
#include "dev/platform.hh"
|
2004-01-12 04:00:35 +01:00
|
|
|
#include "targetarch/vtophys.hh"
|
|
|
|
|
|
|
|
using namespace std;
|
|
|
|
|
2004-08-20 17:35:31 +02:00
|
|
|
LinuxSystem::LinuxSystem(Params *p)
|
|
|
|
: System(p)
|
2004-01-12 04:00:35 +01:00
|
|
|
{
|
|
|
|
Addr addr = 0;
|
2004-02-22 02:31:08 +01:00
|
|
|
|
2004-05-30 23:45:46 +02:00
|
|
|
/**
|
2004-08-20 17:35:31 +02:00
|
|
|
* find the address of the est_cycle_freq variable and insert it
|
|
|
|
* so we don't through the lengthly process of trying to
|
|
|
|
* calculated it by using the PIT, RTC, etc.
|
2004-05-30 23:45:46 +02:00
|
|
|
*/
|
2004-01-26 19:26:34 +01:00
|
|
|
if (kernelSymtab->findAddress("est_cycle_freq", addr)) {
|
2004-01-12 04:00:35 +01:00
|
|
|
Addr paddr = vtophys(physmem, addr);
|
2004-01-26 19:26:34 +01:00
|
|
|
uint8_t *est_cycle_frequency =
|
|
|
|
physmem->dma_addr(paddr, sizeof(uint64_t));
|
2004-01-12 04:00:35 +01:00
|
|
|
|
2004-01-26 19:26:34 +01:00
|
|
|
if (est_cycle_frequency)
|
Make the notion of a global event tick independent of the actual
CPU cycle ticks. This allows the user to have CPUs of different
frequencies, and also allows frequencies and latencies that are
not evenly divisible by the CPU frequency. For now, the CPU
frequency is still set to the global frequency, but soon, we'll
hopefully make the global frequency fixed at something like 1THz
and set all other frequencies independently.
arch/alpha/ev5.cc:
The cycles counter is based on the current cpu cycle.
cpu/base_cpu.cc:
frequency isn't the cpu parameter anymore, cycleTime is.
cpu/base_cpu.hh:
frequency isn't the cpu parameter anymore, cycleTime is.
create several public functions for getting the cpu frequency
and the numbers of ticks for a given number of cycles, etc.
cpu/memtest/memtest.cc:
cpu/simple_cpu/simple_cpu.cc:
cpu/simple_cpu/simple_cpu.hh:
cpu/trace/trace_cpu.cc:
Now that ticks aren't cpu cycles, fixup code to advance
by the proper number of ticks.
cpu/memtest/memtest.hh:
cpu/trace/trace_cpu.hh:
Provide a function to get the number of ticks for a given
number of cycles.
dev/alpha_console.cc:
Update for changes in the way that frequencies and latencies are
accessed. Move some stuff to init()
dev/alpha_console.hh:
Need a pointer to the system and the cpu to get the frequency
so we can pass the info to the console code.
dev/etherbus.cc:
dev/etherbus.hh:
dev/etherlink.cc:
dev/etherlink.hh:
dev/ethertap.cc:
dev/ide_disk.hh:
dev/ns_gige.cc:
dev/ns_gige.hh:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
dev/ide_disk.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
Add some extra debugging printfs
dev/platform.cc:
dev/sinic.cc:
dev/sinic.hh:
outline the constructor and destructor
dev/platform.hh:
outline the constructor and destructor.
don't keep track of the interrupt frequency. Only provide the
accessor function.
dev/tsunami.cc:
dev/tsunami.hh:
outline the constructor and destructor
Don't set the interrupt frequency here. Get it from the actual device
that does the interrupting.
dev/tsunami_io.cc:
dev/tsunami_io.hh:
Make the interrupt interval a configuration parameter. (And convert
the interval to the new latency/frequency stuff in the python)
kern/linux/linux_system.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
kern/tru64/tru64_system.cc:
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
python/m5/config.py:
Fix support for cycle_time relative latencies and frequencies.
Add support for getting a NetworkBandwidth or a MemoryBandwidth.
python/m5/objects/BaseCPU.mpy:
All CPUs now have a cycle_time. The default is the global frequency,
but it is now possible to set the global frequency to some large value
(like 1THz) and set each CPU frequency independently.
python/m5/objects/BaseCache.mpy:
python/m5/objects/Ide.mpy:
Make this a Latency parameter
python/m5/objects/BaseSystem.mpy:
We need to pass the boot CPU's frequency to the system
python/m5/objects/Ethernet.mpy:
Update parameter types to use latency and bandwidth types
python/m5/objects/Platform.mpy:
this frequency isn't needed. We get it from the clock interrupt.
python/m5/objects/Tsunami.mpy:
The clock generator should hold the frequency
sim/eventq.hh:
Need to remove this assertion because the writeback event
queue is different from the CPU's event queue which can cause
this assertion to fail.
sim/process.cc:
Fix comment.
sim/system.hh:
Struct member to hold the boot CPU's frequency.
sim/universe.cc:
remove unneeded variable.
--HG--
extra : convert_revision : 51efe4041095234bf458d9b3b0d417f4cae16fdc
2005-04-11 21:32:06 +02:00
|
|
|
*(uint64_t *)est_cycle_frequency =
|
|
|
|
Clock::Frequency / p->boot_cpu_frequency;
|
2004-01-12 04:00:35 +01:00
|
|
|
}
|
|
|
|
|
2004-02-22 02:31:08 +01:00
|
|
|
|
2004-05-30 23:45:46 +02:00
|
|
|
/**
|
|
|
|
* Since we aren't using a bootloader, we have to copy the kernel arguments
|
|
|
|
* directly into the kernels memory.
|
|
|
|
*/
|
2004-05-27 00:48:11 +02:00
|
|
|
{
|
|
|
|
Addr paddr = vtophys(physmem, PARAM_ADDR);
|
|
|
|
char *commandline = (char*)physmem->dma_addr(paddr, sizeof(uint64_t));
|
|
|
|
if (commandline)
|
2004-08-20 17:35:31 +02:00
|
|
|
strcpy(commandline, params->boot_osflags.c_str());
|
2004-05-27 00:48:11 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2004-06-30 22:06:47 +02:00
|
|
|
/**
|
|
|
|
* EV5 only supports 127 ASNs so we are going to tell the kernel that the
|
|
|
|
* paritiuclar EV6 we have only supports 127 asns.
|
|
|
|
* @todo At some point we should change ev5.hh and the palcode to support
|
|
|
|
* 255 ASNs.
|
|
|
|
*/
|
|
|
|
if (kernelSymtab->findAddress("dp264_mv", addr)) {
|
|
|
|
Addr paddr = vtophys(physmem, addr);
|
|
|
|
char *dp264_mv = (char *)physmem->dma_addr(paddr, sizeof(uint64_t));
|
|
|
|
|
|
|
|
if (dp264_mv) {
|
2005-08-15 22:59:58 +02:00
|
|
|
*(uint32_t*)(dp264_mv+0x18) = htog((uint32_t)127);
|
2004-06-30 22:06:47 +02:00
|
|
|
} else
|
2004-08-20 17:35:31 +02:00
|
|
|
panic("could not translate dp264_mv addr\n");
|
2004-06-30 22:06:47 +02:00
|
|
|
|
|
|
|
} else
|
2004-08-20 17:35:31 +02:00
|
|
|
panic("could not find dp264_mv\n");
|
2004-06-30 22:06:47 +02:00
|
|
|
|
2005-02-09 16:27:00 +01:00
|
|
|
#ifndef NDEBUG
|
2004-08-20 17:35:31 +02:00
|
|
|
kernelPanicEvent = new BreakPCEvent(&pcEventQueue, "kernel panic");
|
2004-01-12 04:00:35 +01:00
|
|
|
if (kernelSymtab->findAddress("panic", addr))
|
|
|
|
kernelPanicEvent->schedule(addr);
|
|
|
|
else
|
|
|
|
panic("could not find kernel symbol \'panic\'");
|
2005-04-28 23:24:04 +02:00
|
|
|
#if 0
|
2005-02-09 16:27:00 +01:00
|
|
|
kernelDieEvent = new BreakPCEvent(&pcEventQueue, "die if kernel");
|
|
|
|
if (kernelSymtab->findAddress("die_if_kernel", addr))
|
|
|
|
kernelDieEvent->schedule(addr);
|
|
|
|
else
|
|
|
|
panic("could not find kernel symbol \'die_if_kernel\'");
|
2005-04-28 23:24:04 +02:00
|
|
|
#endif
|
2005-02-09 16:27:00 +01:00
|
|
|
|
2004-05-12 04:42:45 +02:00
|
|
|
#endif
|
2004-01-12 04:00:35 +01:00
|
|
|
|
2004-05-30 23:45:46 +02:00
|
|
|
/**
|
2004-08-20 17:35:31 +02:00
|
|
|
* Any time ide_delay_50ms, calibarte_delay or
|
|
|
|
* determine_cpu_caches is called just skip the
|
|
|
|
* function. Currently determine_cpu_caches only is used put
|
|
|
|
* information in proc, however if that changes in the future we
|
|
|
|
* will have to fill in the cache size variables appropriately.
|
2004-05-30 23:45:46 +02:00
|
|
|
*/
|
2004-08-20 17:35:31 +02:00
|
|
|
skipIdeDelay50msEvent = new SkipFuncEvent(&pcEventQueue, "ide_delay_50ms");
|
2004-03-23 23:10:07 +01:00
|
|
|
if (kernelSymtab->findAddress("ide_delay_50ms", addr))
|
2004-05-30 23:45:46 +02:00
|
|
|
skipIdeDelay50msEvent->schedule(addr+sizeof(MachInst));
|
2004-03-23 23:10:07 +01:00
|
|
|
|
2004-08-20 17:35:31 +02:00
|
|
|
skipDelayLoopEvent = new LinuxSkipDelayLoopEvent(&pcEventQueue,
|
|
|
|
"calibrate_delay");
|
2005-05-03 01:01:11 +02:00
|
|
|
if (kernelSymtab->findAddress("calibrate_delay", addr)) {
|
|
|
|
skipDelayLoopEvent->schedule(addr + 3 * sizeof(MachInst));
|
|
|
|
}
|
2004-02-06 00:23:16 +01:00
|
|
|
|
2004-08-20 17:35:31 +02:00
|
|
|
skipCacheProbeEvent = new SkipFuncEvent(&pcEventQueue,
|
|
|
|
"determine_cpu_caches");
|
2004-05-10 02:14:18 +02:00
|
|
|
if (kernelSymtab->findAddress("determine_cpu_caches", addr))
|
2004-05-30 23:45:46 +02:00
|
|
|
skipCacheProbeEvent->schedule(addr+sizeof(MachInst));
|
2004-07-31 06:55:05 +02:00
|
|
|
|
2004-08-20 17:35:31 +02:00
|
|
|
debugPrintkEvent = new DebugPrintkEvent(&pcEventQueue, "dprintk");
|
2004-07-31 06:55:05 +02:00
|
|
|
if (kernelSymtab->findAddress("dprintk", addr))
|
2004-08-20 17:35:31 +02:00
|
|
|
debugPrintkEvent->schedule(addr+8);
|
|
|
|
|
|
|
|
idleStartEvent = new IdleStartEvent(&pcEventQueue, "cpu_idle", this);
|
|
|
|
if (kernelSymtab->findAddress("cpu_idle", addr))
|
|
|
|
idleStartEvent->schedule(addr);
|
2004-08-19 05:06:51 +02:00
|
|
|
|
2004-08-20 17:35:31 +02:00
|
|
|
printThreadEvent = new PrintThreadInfo(&pcEventQueue, "threadinfo");
|
|
|
|
if (kernelSymtab->findAddress("alpha_switch_to", addr) && DTRACE(Thread))
|
|
|
|
printThreadEvent->schedule(addr + sizeof(MachInst) * 6);
|
2004-09-03 20:12:59 +02:00
|
|
|
|
|
|
|
intStartEvent = new InterruptStartEvent(&pcEventQueue, "intStartEvent");
|
2004-09-16 06:37:21 +02:00
|
|
|
|
2004-09-24 20:16:51 +02:00
|
|
|
if (params->bin_int) {
|
|
|
|
if (palSymtab->findAddress("sys_int_21", addr))
|
|
|
|
intStartEvent->schedule(addr + sizeof(MachInst) * 2);
|
|
|
|
else
|
|
|
|
panic("could not find symbol: sys_int_21\n");
|
|
|
|
|
|
|
|
intEndEvent = new InterruptEndEvent(&pcEventQueue, "intEndEvent");
|
|
|
|
if (palSymtab->findAddress("rti_to_kern", addr))
|
|
|
|
intEndEvent->schedule(addr) ;
|
|
|
|
else
|
|
|
|
panic("could not find symbol: rti_to_kern\n");
|
|
|
|
|
|
|
|
intEndEvent2 = new InterruptEndEvent(&pcEventQueue, "intEndEvent2");
|
|
|
|
if (palSymtab->findAddress("rti_to_user", addr))
|
|
|
|
intEndEvent2->schedule(addr);
|
|
|
|
else
|
|
|
|
panic("could not find symbol: rti_to_user\n");
|
|
|
|
|
|
|
|
|
|
|
|
intEndEvent3 = new InterruptEndEvent(&pcEventQueue, "intEndEvent3");
|
|
|
|
if (kernelSymtab->findAddress("do_softirq", addr))
|
|
|
|
intEndEvent3->schedule(addr + sizeof(MachInst) * 2);
|
|
|
|
else
|
|
|
|
panic("could not find symbol: do_softirq\n");
|
|
|
|
}
|
2004-01-12 04:00:35 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
LinuxSystem::~LinuxSystem()
|
|
|
|
{
|
2005-02-09 16:27:00 +01:00
|
|
|
#ifndef NDEBUG
|
2004-01-12 04:00:35 +01:00
|
|
|
delete kernelPanicEvent;
|
2004-08-20 17:35:31 +02:00
|
|
|
#endif
|
2004-05-18 19:53:11 +02:00
|
|
|
delete skipIdeDelay50msEvent;
|
|
|
|
delete skipDelayLoopEvent;
|
|
|
|
delete skipCacheProbeEvent;
|
2004-08-20 17:35:31 +02:00
|
|
|
delete debugPrintkEvent;
|
|
|
|
delete idleStartEvent;
|
2004-09-03 20:12:59 +02:00
|
|
|
delete printThreadEvent;
|
|
|
|
delete intStartEvent;
|
2004-09-16 06:37:21 +02:00
|
|
|
delete intEndEvent;
|
|
|
|
delete intEndEvent2;
|
2004-01-12 04:00:35 +01:00
|
|
|
}
|
|
|
|
|
2004-05-27 00:48:11 +02:00
|
|
|
|
2004-02-06 00:23:16 +01:00
|
|
|
void
|
|
|
|
LinuxSystem::setDelayLoop(ExecContext *xc)
|
|
|
|
{
|
|
|
|
Addr addr = 0;
|
|
|
|
if (kernelSymtab->findAddress("loops_per_jiffy", addr)) {
|
|
|
|
Addr paddr = vtophys(physmem, addr);
|
|
|
|
|
|
|
|
uint8_t *loops_per_jiffy =
|
|
|
|
physmem->dma_addr(paddr, sizeof(uint32_t));
|
|
|
|
|
Make the notion of a global event tick independent of the actual
CPU cycle ticks. This allows the user to have CPUs of different
frequencies, and also allows frequencies and latencies that are
not evenly divisible by the CPU frequency. For now, the CPU
frequency is still set to the global frequency, but soon, we'll
hopefully make the global frequency fixed at something like 1THz
and set all other frequencies independently.
arch/alpha/ev5.cc:
The cycles counter is based on the current cpu cycle.
cpu/base_cpu.cc:
frequency isn't the cpu parameter anymore, cycleTime is.
cpu/base_cpu.hh:
frequency isn't the cpu parameter anymore, cycleTime is.
create several public functions for getting the cpu frequency
and the numbers of ticks for a given number of cycles, etc.
cpu/memtest/memtest.cc:
cpu/simple_cpu/simple_cpu.cc:
cpu/simple_cpu/simple_cpu.hh:
cpu/trace/trace_cpu.cc:
Now that ticks aren't cpu cycles, fixup code to advance
by the proper number of ticks.
cpu/memtest/memtest.hh:
cpu/trace/trace_cpu.hh:
Provide a function to get the number of ticks for a given
number of cycles.
dev/alpha_console.cc:
Update for changes in the way that frequencies and latencies are
accessed. Move some stuff to init()
dev/alpha_console.hh:
Need a pointer to the system and the cpu to get the frequency
so we can pass the info to the console code.
dev/etherbus.cc:
dev/etherbus.hh:
dev/etherlink.cc:
dev/etherlink.hh:
dev/ethertap.cc:
dev/ide_disk.hh:
dev/ns_gige.cc:
dev/ns_gige.hh:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
dev/ide_disk.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
Add some extra debugging printfs
dev/platform.cc:
dev/sinic.cc:
dev/sinic.hh:
outline the constructor and destructor
dev/platform.hh:
outline the constructor and destructor.
don't keep track of the interrupt frequency. Only provide the
accessor function.
dev/tsunami.cc:
dev/tsunami.hh:
outline the constructor and destructor
Don't set the interrupt frequency here. Get it from the actual device
that does the interrupting.
dev/tsunami_io.cc:
dev/tsunami_io.hh:
Make the interrupt interval a configuration parameter. (And convert
the interval to the new latency/frequency stuff in the python)
kern/linux/linux_system.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
kern/tru64/tru64_system.cc:
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
python/m5/config.py:
Fix support for cycle_time relative latencies and frequencies.
Add support for getting a NetworkBandwidth or a MemoryBandwidth.
python/m5/objects/BaseCPU.mpy:
All CPUs now have a cycle_time. The default is the global frequency,
but it is now possible to set the global frequency to some large value
(like 1THz) and set each CPU frequency independently.
python/m5/objects/BaseCache.mpy:
python/m5/objects/Ide.mpy:
Make this a Latency parameter
python/m5/objects/BaseSystem.mpy:
We need to pass the boot CPU's frequency to the system
python/m5/objects/Ethernet.mpy:
Update parameter types to use latency and bandwidth types
python/m5/objects/Platform.mpy:
this frequency isn't needed. We get it from the clock interrupt.
python/m5/objects/Tsunami.mpy:
The clock generator should hold the frequency
sim/eventq.hh:
Need to remove this assertion because the writeback event
queue is different from the CPU's event queue which can cause
this assertion to fail.
sim/process.cc:
Fix comment.
sim/system.hh:
Struct member to hold the boot CPU's frequency.
sim/universe.cc:
remove unneeded variable.
--HG--
extra : convert_revision : 51efe4041095234bf458d9b3b0d417f4cae16fdc
2005-04-11 21:32:06 +02:00
|
|
|
Tick cpuFreq = xc->cpu->frequency();
|
|
|
|
Tick intrFreq = platform->intrFrequency();
|
2004-02-06 00:23:16 +01:00
|
|
|
*(uint32_t *)loops_per_jiffy =
|
|
|
|
(uint32_t)((cpuFreq / intrFreq) * 0.9988);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2004-01-12 04:00:35 +01:00
|
|
|
BEGIN_DECLARE_SIM_OBJECT_PARAMS(LinuxSystem)
|
|
|
|
|
Make the notion of a global event tick independent of the actual
CPU cycle ticks. This allows the user to have CPUs of different
frequencies, and also allows frequencies and latencies that are
not evenly divisible by the CPU frequency. For now, the CPU
frequency is still set to the global frequency, but soon, we'll
hopefully make the global frequency fixed at something like 1THz
and set all other frequencies independently.
arch/alpha/ev5.cc:
The cycles counter is based on the current cpu cycle.
cpu/base_cpu.cc:
frequency isn't the cpu parameter anymore, cycleTime is.
cpu/base_cpu.hh:
frequency isn't the cpu parameter anymore, cycleTime is.
create several public functions for getting the cpu frequency
and the numbers of ticks for a given number of cycles, etc.
cpu/memtest/memtest.cc:
cpu/simple_cpu/simple_cpu.cc:
cpu/simple_cpu/simple_cpu.hh:
cpu/trace/trace_cpu.cc:
Now that ticks aren't cpu cycles, fixup code to advance
by the proper number of ticks.
cpu/memtest/memtest.hh:
cpu/trace/trace_cpu.hh:
Provide a function to get the number of ticks for a given
number of cycles.
dev/alpha_console.cc:
Update for changes in the way that frequencies and latencies are
accessed. Move some stuff to init()
dev/alpha_console.hh:
Need a pointer to the system and the cpu to get the frequency
so we can pass the info to the console code.
dev/etherbus.cc:
dev/etherbus.hh:
dev/etherlink.cc:
dev/etherlink.hh:
dev/ethertap.cc:
dev/ide_disk.hh:
dev/ns_gige.cc:
dev/ns_gige.hh:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
dev/ide_disk.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
Add some extra debugging printfs
dev/platform.cc:
dev/sinic.cc:
dev/sinic.hh:
outline the constructor and destructor
dev/platform.hh:
outline the constructor and destructor.
don't keep track of the interrupt frequency. Only provide the
accessor function.
dev/tsunami.cc:
dev/tsunami.hh:
outline the constructor and destructor
Don't set the interrupt frequency here. Get it from the actual device
that does the interrupting.
dev/tsunami_io.cc:
dev/tsunami_io.hh:
Make the interrupt interval a configuration parameter. (And convert
the interval to the new latency/frequency stuff in the python)
kern/linux/linux_system.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
kern/tru64/tru64_system.cc:
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
python/m5/config.py:
Fix support for cycle_time relative latencies and frequencies.
Add support for getting a NetworkBandwidth or a MemoryBandwidth.
python/m5/objects/BaseCPU.mpy:
All CPUs now have a cycle_time. The default is the global frequency,
but it is now possible to set the global frequency to some large value
(like 1THz) and set each CPU frequency independently.
python/m5/objects/BaseCache.mpy:
python/m5/objects/Ide.mpy:
Make this a Latency parameter
python/m5/objects/BaseSystem.mpy:
We need to pass the boot CPU's frequency to the system
python/m5/objects/Ethernet.mpy:
Update parameter types to use latency and bandwidth types
python/m5/objects/Platform.mpy:
this frequency isn't needed. We get it from the clock interrupt.
python/m5/objects/Tsunami.mpy:
The clock generator should hold the frequency
sim/eventq.hh:
Need to remove this assertion because the writeback event
queue is different from the CPU's event queue which can cause
this assertion to fail.
sim/process.cc:
Fix comment.
sim/system.hh:
Struct member to hold the boot CPU's frequency.
sim/universe.cc:
remove unneeded variable.
--HG--
extra : convert_revision : 51efe4041095234bf458d9b3b0d417f4cae16fdc
2005-04-11 21:32:06 +02:00
|
|
|
Param<Tick> boot_cpu_frequency;
|
2005-01-15 10:12:25 +01:00
|
|
|
SimObjectParam<MemoryController *> memctrl;
|
2004-01-12 04:00:35 +01:00
|
|
|
SimObjectParam<PhysicalMemory *> physmem;
|
|
|
|
|
2005-01-15 10:12:25 +01:00
|
|
|
Param<string> kernel;
|
|
|
|
Param<string> console;
|
|
|
|
Param<string> pal;
|
2004-01-12 04:00:35 +01:00
|
|
|
|
2004-08-20 17:35:31 +02:00
|
|
|
Param<string> boot_osflags;
|
2004-07-02 00:03:05 +02:00
|
|
|
Param<string> readfile;
|
2004-08-20 17:35:31 +02:00
|
|
|
Param<unsigned int> init_param;
|
|
|
|
|
|
|
|
Param<uint64_t> system_type;
|
|
|
|
Param<uint64_t> system_rev;
|
|
|
|
|
|
|
|
Param<bool> bin;
|
|
|
|
VectorParam<string> binned_fns;
|
2004-09-03 20:12:59 +02:00
|
|
|
Param<bool> bin_int;
|
2004-07-02 00:03:05 +02:00
|
|
|
|
2004-01-12 04:00:35 +01:00
|
|
|
END_DECLARE_SIM_OBJECT_PARAMS(LinuxSystem)
|
|
|
|
|
|
|
|
BEGIN_INIT_SIM_OBJECT_PARAMS(LinuxSystem)
|
|
|
|
|
Make the notion of a global event tick independent of the actual
CPU cycle ticks. This allows the user to have CPUs of different
frequencies, and also allows frequencies and latencies that are
not evenly divisible by the CPU frequency. For now, the CPU
frequency is still set to the global frequency, but soon, we'll
hopefully make the global frequency fixed at something like 1THz
and set all other frequencies independently.
arch/alpha/ev5.cc:
The cycles counter is based on the current cpu cycle.
cpu/base_cpu.cc:
frequency isn't the cpu parameter anymore, cycleTime is.
cpu/base_cpu.hh:
frequency isn't the cpu parameter anymore, cycleTime is.
create several public functions for getting the cpu frequency
and the numbers of ticks for a given number of cycles, etc.
cpu/memtest/memtest.cc:
cpu/simple_cpu/simple_cpu.cc:
cpu/simple_cpu/simple_cpu.hh:
cpu/trace/trace_cpu.cc:
Now that ticks aren't cpu cycles, fixup code to advance
by the proper number of ticks.
cpu/memtest/memtest.hh:
cpu/trace/trace_cpu.hh:
Provide a function to get the number of ticks for a given
number of cycles.
dev/alpha_console.cc:
Update for changes in the way that frequencies and latencies are
accessed. Move some stuff to init()
dev/alpha_console.hh:
Need a pointer to the system and the cpu to get the frequency
so we can pass the info to the console code.
dev/etherbus.cc:
dev/etherbus.hh:
dev/etherlink.cc:
dev/etherlink.hh:
dev/ethertap.cc:
dev/ide_disk.hh:
dev/ns_gige.cc:
dev/ns_gige.hh:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
dev/ide_disk.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
Add some extra debugging printfs
dev/platform.cc:
dev/sinic.cc:
dev/sinic.hh:
outline the constructor and destructor
dev/platform.hh:
outline the constructor and destructor.
don't keep track of the interrupt frequency. Only provide the
accessor function.
dev/tsunami.cc:
dev/tsunami.hh:
outline the constructor and destructor
Don't set the interrupt frequency here. Get it from the actual device
that does the interrupting.
dev/tsunami_io.cc:
dev/tsunami_io.hh:
Make the interrupt interval a configuration parameter. (And convert
the interval to the new latency/frequency stuff in the python)
kern/linux/linux_system.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
kern/tru64/tru64_system.cc:
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
python/m5/config.py:
Fix support for cycle_time relative latencies and frequencies.
Add support for getting a NetworkBandwidth or a MemoryBandwidth.
python/m5/objects/BaseCPU.mpy:
All CPUs now have a cycle_time. The default is the global frequency,
but it is now possible to set the global frequency to some large value
(like 1THz) and set each CPU frequency independently.
python/m5/objects/BaseCache.mpy:
python/m5/objects/Ide.mpy:
Make this a Latency parameter
python/m5/objects/BaseSystem.mpy:
We need to pass the boot CPU's frequency to the system
python/m5/objects/Ethernet.mpy:
Update parameter types to use latency and bandwidth types
python/m5/objects/Platform.mpy:
this frequency isn't needed. We get it from the clock interrupt.
python/m5/objects/Tsunami.mpy:
The clock generator should hold the frequency
sim/eventq.hh:
Need to remove this assertion because the writeback event
queue is different from the CPU's event queue which can cause
this assertion to fail.
sim/process.cc:
Fix comment.
sim/system.hh:
Struct member to hold the boot CPU's frequency.
sim/universe.cc:
remove unneeded variable.
--HG--
extra : convert_revision : 51efe4041095234bf458d9b3b0d417f4cae16fdc
2005-04-11 21:32:06 +02:00
|
|
|
INIT_PARAM(boot_cpu_frequency, "Frequency of the boot CPU"),
|
2005-01-15 10:12:25 +01:00
|
|
|
INIT_PARAM(memctrl, "memory controller"),
|
2004-01-12 04:00:35 +01:00
|
|
|
INIT_PARAM(physmem, "phsyical memory"),
|
2005-01-15 10:12:25 +01:00
|
|
|
INIT_PARAM(kernel, "file that contains the kernel code"),
|
|
|
|
INIT_PARAM(console, "file that contains the console code"),
|
|
|
|
INIT_PARAM(pal, "file that contains palcode"),
|
2004-01-12 04:00:35 +01:00
|
|
|
INIT_PARAM_DFLT(boot_osflags, "flags to pass to the kernel during boot",
|
2004-08-20 17:35:31 +02:00
|
|
|
"a"),
|
|
|
|
INIT_PARAM_DFLT(readfile, "file to read startup script from", ""),
|
|
|
|
INIT_PARAM_DFLT(init_param, "numerical value to pass into simulator", 0),
|
|
|
|
INIT_PARAM_DFLT(system_type, "Type of system we are emulating", 34),
|
|
|
|
INIT_PARAM_DFLT(system_rev, "Revision of system we are emulating", 1<<10),
|
|
|
|
INIT_PARAM_DFLT(bin, "is this system to be binned", false),
|
2004-09-03 20:12:59 +02:00
|
|
|
INIT_PARAM(binned_fns, "functions to be broken down and binned"),
|
2004-11-14 21:26:48 +01:00
|
|
|
INIT_PARAM_DFLT(bin_int, "is interrupt code binned seperately?", true)
|
2004-01-12 04:00:35 +01:00
|
|
|
|
|
|
|
END_INIT_SIM_OBJECT_PARAMS(LinuxSystem)
|
|
|
|
|
|
|
|
CREATE_SIM_OBJECT(LinuxSystem)
|
|
|
|
{
|
2004-08-20 17:35:31 +02:00
|
|
|
System::Params *p = new System::Params;
|
|
|
|
p->name = getInstanceName();
|
Make the notion of a global event tick independent of the actual
CPU cycle ticks. This allows the user to have CPUs of different
frequencies, and also allows frequencies and latencies that are
not evenly divisible by the CPU frequency. For now, the CPU
frequency is still set to the global frequency, but soon, we'll
hopefully make the global frequency fixed at something like 1THz
and set all other frequencies independently.
arch/alpha/ev5.cc:
The cycles counter is based on the current cpu cycle.
cpu/base_cpu.cc:
frequency isn't the cpu parameter anymore, cycleTime is.
cpu/base_cpu.hh:
frequency isn't the cpu parameter anymore, cycleTime is.
create several public functions for getting the cpu frequency
and the numbers of ticks for a given number of cycles, etc.
cpu/memtest/memtest.cc:
cpu/simple_cpu/simple_cpu.cc:
cpu/simple_cpu/simple_cpu.hh:
cpu/trace/trace_cpu.cc:
Now that ticks aren't cpu cycles, fixup code to advance
by the proper number of ticks.
cpu/memtest/memtest.hh:
cpu/trace/trace_cpu.hh:
Provide a function to get the number of ticks for a given
number of cycles.
dev/alpha_console.cc:
Update for changes in the way that frequencies and latencies are
accessed. Move some stuff to init()
dev/alpha_console.hh:
Need a pointer to the system and the cpu to get the frequency
so we can pass the info to the console code.
dev/etherbus.cc:
dev/etherbus.hh:
dev/etherlink.cc:
dev/etherlink.hh:
dev/ethertap.cc:
dev/ide_disk.hh:
dev/ns_gige.cc:
dev/ns_gige.hh:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
dev/ide_disk.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
Add some extra debugging printfs
dev/platform.cc:
dev/sinic.cc:
dev/sinic.hh:
outline the constructor and destructor
dev/platform.hh:
outline the constructor and destructor.
don't keep track of the interrupt frequency. Only provide the
accessor function.
dev/tsunami.cc:
dev/tsunami.hh:
outline the constructor and destructor
Don't set the interrupt frequency here. Get it from the actual device
that does the interrupting.
dev/tsunami_io.cc:
dev/tsunami_io.hh:
Make the interrupt interval a configuration parameter. (And convert
the interval to the new latency/frequency stuff in the python)
kern/linux/linux_system.cc:
update for changes in the way bandwidths are passed from
python to C++ to accomidate the new way that ticks works.
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
kern/tru64/tru64_system.cc:
For now, we must get the boot cpu's frequency as a parameter
since allowing the system to have a pointer to the boot cpu would
cause a cycle.
python/m5/config.py:
Fix support for cycle_time relative latencies and frequencies.
Add support for getting a NetworkBandwidth or a MemoryBandwidth.
python/m5/objects/BaseCPU.mpy:
All CPUs now have a cycle_time. The default is the global frequency,
but it is now possible to set the global frequency to some large value
(like 1THz) and set each CPU frequency independently.
python/m5/objects/BaseCache.mpy:
python/m5/objects/Ide.mpy:
Make this a Latency parameter
python/m5/objects/BaseSystem.mpy:
We need to pass the boot CPU's frequency to the system
python/m5/objects/Ethernet.mpy:
Update parameter types to use latency and bandwidth types
python/m5/objects/Platform.mpy:
this frequency isn't needed. We get it from the clock interrupt.
python/m5/objects/Tsunami.mpy:
The clock generator should hold the frequency
sim/eventq.hh:
Need to remove this assertion because the writeback event
queue is different from the CPU's event queue which can cause
this assertion to fail.
sim/process.cc:
Fix comment.
sim/system.hh:
Struct member to hold the boot CPU's frequency.
sim/universe.cc:
remove unneeded variable.
--HG--
extra : convert_revision : 51efe4041095234bf458d9b3b0d417f4cae16fdc
2005-04-11 21:32:06 +02:00
|
|
|
p->boot_cpu_frequency = boot_cpu_frequency;
|
2005-01-15 10:12:25 +01:00
|
|
|
p->memctrl = memctrl;
|
2004-08-20 17:35:31 +02:00
|
|
|
p->physmem = physmem;
|
2005-01-15 10:12:25 +01:00
|
|
|
p->kernel_path = kernel;
|
|
|
|
p->console_path = console;
|
|
|
|
p->palcode = pal;
|
2004-08-20 17:35:31 +02:00
|
|
|
p->boot_osflags = boot_osflags;
|
|
|
|
p->init_param = init_param;
|
|
|
|
p->readfile = readfile;
|
|
|
|
p->system_type = system_type;
|
|
|
|
p->system_rev = system_rev;
|
|
|
|
p->bin = bin;
|
|
|
|
p->binned_fns = binned_fns;
|
2004-09-03 20:12:59 +02:00
|
|
|
p->bin_int = bin_int;
|
2004-08-20 17:35:31 +02:00
|
|
|
return new LinuxSystem(p);
|
2004-01-12 04:00:35 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
REGISTER_SIM_OBJECT("LinuxSystem", LinuxSystem)
|
2004-08-20 17:35:31 +02:00
|
|
|
|