On Mon, Aug 31, 2009 at 8:48 PM, Polina Dudnik wrote:
> I see. It seems like it would be more appropriate to have tester test larger
> requests because we are getting a false sense of correctness by running the
> test. It tests the protocol logic well but not the data correctness.
It's a "false sh
I see. It seems like it would be more appropriate to have tester test larger
requests because we are getting a false sense of correctness by running the
test. It tests the protocol logic well but not the data correctness.
Also, is there a maximum on the size of the m5 request? I would like to test
Good question. Looks like historical cruft to me. I think there used
to be a mode that tested variable-size accesses but that mode got
ripped out. Note that access_size is log2 of the access size, so
setting it to 0 means byte accesses.
Steve
On Mon, Aug 31, 2009 at 3:30 PM, Polina Dudnik wrot
Hi,
I have a question: why is it that the access_size is first calculated as
random() % 4 and then reset to zero before issuing the request in
MemTest::tick?
Thank you.
Polina
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m
