scons: *** [build/ALPHA_SE/python/swig/random_wrap.fo] Error 1
scons: *** [build/ALPHA_FS/python/swig/random_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/debug_wrap.fo] Error 1
scons: *** [build/ALPHA_SE/python/swig/trace_wrap.fo] Error 1
scons: ***
I will push this if nobody has any objections.
On Mon, Aug 31, 2009 at 4:48 PM, Polina Dudnik pdud...@gmail.com wrote:
Hi,
I am attaching a small patch that enables the passing of the ruby config
file as a parameter. So, multiple protocols can be tested without manually
modifying the
changeset 369b61762d7b in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=369b61762d7b
description:
[mq]: MOESI_patch
diffstat:
1 file changed, 36 insertions(+), 13 deletions(-)
src/mem/protocol/MOESI_CMP_directory-dir.sm | 49 +++
diffs (109
I will read it today. There are some issues. Please be a bit more
patient.
On Sep 1, 2009, at 8:15, Polina Dudnik pdud...@gmail.com wrote:
I will push this if nobody has any objections.
On Mon, Aug 31, 2009 at 4:48 PM, Polina Dudnik pdud...@gmail.com
wrote:
Hi,
I am attaching a small
Thank you. No rush.
On Tue, Sep 1, 2009 at 9:30 AM, Nathan Binkert n...@binkert.org wrote:
I will read it today. There are some issues. Please be a bit more patient.
On Sep 1, 2009, at 8:15, Polina Dudnik pdud...@gmail.com wrote:
I will push this if nobody has any objections.
On Mon, Aug
Hi,
I am attaching a patch that allows memtest.cc to issue DMA requests.
The changes include:
1. Add bool use_dma and percent_dma to MemTest.py
2. Fix if O3CPU SCons issue that Somayeh had
3. Add percent_dma and use_dma to memtest.hh and memtest.cc
4. Added generation of dma requests to
Before we worry about the details of this patch, I have a higher-level
question: why do we need a separate DMA request type and port at all?
On the M5 side, we've gotten by just fine so far with ReadReq and
WriteReq, and M5 devices don't explicitly mark their DMA requests as
such. I understand
BTW, if you use the '-e' or '-m' options to qnew or qref you can
enter/edit a commit message for a patch which will get used when you
actually commit... obviously preferable to the default of '[mq]:
patch_name'. It's easy to overlook, I know... I've done this a few
times myself.
Steve
On Tue,
changeset dad8671f8769 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=dad8671f8769
description:
SCons fix to always make MemTest object
diffstat:
1 file changed, 4 insertions(+), 4 deletions(-)
src/cpu/memtest/SConscript |8
diffs (17 lines):
diff -r
Thanks. I didn't know that and I was wondering how I could do that.
On Tue, Sep 1, 2009 at 10:33 AM, Steve Reinhardt ste...@gmail.com wrote:
BTW, if you use the '-e' or '-m' options to qnew or qref you can
enter/edit a commit message for a patch which will get used when you
actually commit...
What exactly is the problem that you're encountering?
Note that syscall emulation only occurs in SE mode (that's what the SE
stands for). The file syscall_emul.cc doesn't even get compiled if
FULL_SYSTEM is defined.
Steve
On Mon, Aug 31, 2009 at 1:20 PM, soumyaroop roys...@cse.usf.edu wrote:
Oh, that is correct, Steve!
Ok, so here's the problem:
If I were to run an SMT configuration, say, 2T-hello-gzip (both compiled
with gcc 4.3.2 built with linux kernel 2.6.X) as two workloads on a single
processor using O3 or inorder, when hello finishes, it kills off gzip too.
I figured that this
On Tue, Sep 1, 2009 at 10:29 AM, Steve Reinhardt ste...@gmail.com wrote:
Before we worry about the details of this patch, I have a higher-level
question: why do we need a separate DMA request type and port at all?
On the M5 side, we've gotten by just fine so far with ReadReq and
WriteReq, and
Yea, the exit() vs exit_group() distinction is relatively recent, and
the initial SE-mode support predates that, which is why it isn't
handled quite right. The right answer is indicated by the comment
in exitGroupFunc... what you really want exit_group to do is identify
all the other threads
On Tue, Sep 1, 2009 at 10:29 AM, Steve Reinhardtste...@gmail.com wrote:
Before we worry about the details of this patch, I have a higher-level
question: why do we need a separate DMA request type and port at all?
On the M5 side, we've gotten by just fine so far with ReadReq and
WriteReq, and
On Tue, Sep 1, 2009 at 9:09 AM, Derek Howerderek.ho...@gmail.com wrote:
On Tue, Sep 1, 2009 at 10:29 AM, Steve Reinhardtste...@gmail.com wrote:
Before we worry about the details of this patch, I have a higher-level
question: why do we need a separate DMA request type and port at all?
On the M5
In addition to what Steve said in the subsequent email, you want to verify
for yourself what happens in exit / exit_group system calls get called
in syscall_emul.cc.
More than likely, the literal exit function gets called and stop the
simulation.
There are a couple of side issues:
(1) Is
On Tue, Sep 1, 2009 at 11:16 AM, Steve Reinhardt ste...@gmail.com wrote:
On Tue, Sep 1, 2009 at 9:09 AM, Derek Howerderek.ho...@gmail.com wrote:
On Tue, Sep 1, 2009 at 10:29 AM, Steve Reinhardtste...@gmail.com
wrote:
Before we worry about the details of this patch, I have a higher-level
On Tue, Sep 1, 2009 at 12:33 PM, Korey Sewell ksew...@umich.edu wrote:
In addition to what Steve said in the subsequent email, you want to verify
for yourself what happens in exit / exit_group system calls get called
in syscall_emul.cc.
More than likely, the literal exit function gets
So, in SE mode, is there a distinction made between two threads (workloads)
belonging to the same process and two threads belonging to different
processes? In other words, if I were to spawn two threads from a single
program, would it be possible to run them as two different h/w threads in SE
On Tue, Sep 1, 2009 at 1:52 PM, Gabriel Michael
Blackgbl...@eecs.umich.edu wrote:
So, in SE mode, is there a distinction made between two threads (workloads)
belonging to the same process and two threads belonging to different
processes? In other words, if I were to spawn two threads from a
21 matches
Mail list logo
