I figured out what I need to do to make the regression suite more
easily extensible. Yell at me if I don't actually do something to fix
it within a week.
Nate
On Tue, Nov 4, 2008 at 1:44 PM, Ali Saidi <[EMAIL PROTECTED]> wrote:
> ...and make a regression that catches the problem in the future.
On quick inspection there is no difference - it all happens in the parent
class, Process.
Incidentally, I have discovered that it works fine in Atomic CPU, just not
timing. If that sets off any ideas in anyone, let me know. Otherwise, I am
just going to keep digging.
Lisa
On Tue, Nov 4, 2008 a
...and make a regression that catches the problem in the future.
Every time we find a bug that isn't caught by a regression test I
think we need to create a configuration that will catch it. In the
future we'll never miss it again, and the new regression might catch
other bugs that the curre
It's definitely a bug... it used to work. I wonder if it has
something to do with migrating towards a more realistic paging model
for SE mode (though that happened quite a while ago---August 2007
according to hg---and if that was totally broken I'm surprised no one
noticed it yet). I'd take a loo
Hey guys,
I'm trying to run a timing CMP with caches using EIO traces, but the EIO
can't seem to be run on multicore platforms, the 2nd cpu inevitably itb
pagefaults continually on a single PC (presumably the first) and then dies.
Is this a bug or a feature? Is there something I don't know about
