It probably is a 8254... Tsunami was a system that DEC was trying to
make look like a x86 machine (for some reason).
Feel free to split them out, just make sure that the Alpha regressions
still pass.
Ali
On Mar 16, 2008, at 2:26 PM, Gabe Black wrote:
And actually, what PIT is tsunami us
And actually, what PIT is tsunami using? It looks very similar to
the I8254 which x86 uses. I would need a more complete implementation
than is in the IO chip, but the code could still be shared pretty easily.
Gabe
Gabe Black wrote:
Surprisingly, it looks like the RTC provided as part of
Surprisingly, it looks like the RTC provided as part of the CMOS
(don't ask me why) is exactly the same as the one provided by the
tsunami io chip. I'd like to split that out into a separate device or at
least a class that I can just use rather than redoing it all. Also, it
uses #define for
looks like it...
On Sun, Mar 16, 2008 at 11:37 AM, nathan binkert <[EMAIL PROTECTED]> wrote:
> Generally, yes. Memory leak?
>
> 2008/3/16 Steve Reinhardt <[EMAIL PROTECTED]>:
> > Funny, I got this error:
> >
> > system.cpu7: completed 630 read accesses @9833512177
> > system.cpu5: completed
The easiest, and probably slowest, way to find that sort of thing is
to run the debug version under valgrind for a while, and then just kill
m5. Make sure you turn on all the leak detection options. You should see
some unfreed memory here and there, but you'll see one (hopefully)
enormous pi
Generally, yes. Memory leak?
2008/3/16 Steve Reinhardt <[EMAIL PROTECTED]>:
> Funny, I got this error:
>
> system.cpu7: completed 630 read accesses @9833512177
> system.cpu5: completed 630 read accesses @9838116814
> terminate called after throwing an instance of 'std::bad_alloc'
>wha
Funny, I got this error:
system.cpu7: completed 630 read accesses @9833512177
system.cpu5: completed 630 read accesses @9838116814
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
Program aborted at cycle 9948602663
I've never even seen that before..
Ok.
Gabe
nathan binkert wrote:
Ok, lets make sure we get all of your licensing stuff settled before
then. We'll work on your stuff Tue and Wed, OK?
Nate
On Sun, Mar 16, 2008 at 10:32 AM, Gabe Black <[EMAIL PROTECTED]> wrote:
Supposedly I'll be flying to Seattle at the end of thi
Ok, lets make sure we get all of your licensing stuff settled before
then. We'll work on your stuff Tue and Wed, OK?
Nate
On Sun, Mar 16, 2008 at 10:32 AM, Gabe Black <[EMAIL PROTECTED]> wrote:
> Supposedly I'll be flying to Seattle at the end of this coming week
> (I don't have confirmat
Supposedly I'll be flying to Seattle at the end of this coming week
(I don't have confirmation yet), and hopefully shortly after I'll be
flying to some combination of California, Madison, and Boston, so I
might be hard to get a hold of soon.
Gabe
nathan binkert wrote:
My three big deadlin
This diff to memtest still fails around the 1 hour mark.
system.cpu0: completed 650 read accesses @10142894636
system.cpu1: completed 650 read accesses @10143875416
system.cpu7: completed 650 read accesses @10145185656
system.cpu5: completed 650 read accesses @10150092622
panic: s
I believe all the FAILEDs below are just the long runs whose stats didn't
get updated after my cache changes. I can't tell what happened on the last
one (the "Error 3"), so I'm hypothesizing that it was just a pool glitch and
I'm rerunning now.
Steve
On Sun, Mar 16, 2008 at 8:10 AM, Cron Daemon
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/
My three big deadlines are all over tomorrow. I'd like us to spend
some time this week to get everything all set to release the
repository. This job is mostly for myself and Gabe, but we need to
answer various questions about mailing list archives and such as well.
Nate
___
I would guess it returns -1, but I dunno. Why don't you access some
unallocated i/o port on a real machine and see what happens. For it to
work you'll need to run as root and call setiopl(3).
Ali
On Mar 16, 2008, at 1:28 AM, Gabe Black wrote:
I realize this is something I should probably
15 matches
Mail list logo
