I don't, and will not, "just do" anything.
It will work, just do it.
Ali
Gabe
Gabe Black wrote:
Two reasons. First, the BIOS is supposed to do that so if possible
I'd like to keep it out of the device itself. That's not a big deal
since it wouldn't be too hard to move if there ends up b
There's construction, then SimObject::init(), then
SimObject::regStats(), then SimObject::startup()
The first three are caused by the instantiate() call in Python, the
last is caused by the first call to simulate() from Python. See
src/python/m5/simulate.py
Nate
On Fri, May 30, 2008 at 10:49
On May 31, 2008, at 1:49 AM, Gabe Black wrote:
One other reason I just thought of is the same as the problem O3 had
with pointers and things not being completely constructed yet.
If the platform has a pointer to the device, that pointer will be
valid at time of construction. The O3 is a spec
One other reason I just thought of is the same as the problem O3 had
with pointers and things not being completely constructed yet. I want to
put the code that sets up the timer in the platform since that's more in
line with the timer being configured a certain way to start, aka it's a
standard
Two reasons. First, the BIOS is supposed to do that so if possible I'd
like to keep it out of the device itself. That's not a big deal since it
wouldn't be too hard to move if there ends up being an actual BIOS at
some point. Second, I was concerned that initializing it in the
constructor and t
I concur with Ali.
On Fri, May 30, 2008 at 5:39 PM, Ali Saidi <[EMAIL PROTECTED]> wrote:
> Why can't you just stick it in the constructor? You'll need to serialize
> that timer value when a checkpoint is dropped and create an event when the
> checkpoint is restored from, but you would need to do t
Why can't you just stick it in the constructor? You'll need to
serialize that timer value when a checkpoint is dropped and create an
event when the checkpoint is restored from, but you would need to do
that anyway. You can take a look at how we serialize the PIT for an
idea.
Ali
On May 3
The kernel is assuming that timer 0 has been set up to count with a
period of 0 (which is effectively 0x, it's maximum value) by the
BIOS during system bring up. It's trying to watch the value of the
timers count in order to switch from using the PIT for interrupts to the
APIC right afte
