Hi

I added the serialize/unserialize support for the Mainmemory object as you 
suggested in your email. I am able to creat a dump of the memory contents 
successfully. The simulator automatically called the Serialize function 
because the Main Memory object is a type of SimObject. The m5.cpt has 
the filename for the memory contents under the heading workload.MainMem.

The problem I face is that during the unserialization process - the 
simulator fails to call the MainMemory - Unserialize method. I was puzzled 
for a long while - because I didnt have to do any changes to other parts 
of the simulator for the MainMemory Serialize technique to get called.

I found that the Unserialization is based on the configuration in 
ConfigHierarchy and the MainMemory object does not seem to be a member of 
that. I realized that the ConfigHierarchy is built based on the config.ini 
file. I looked over the documentation of how the configuration files are 
to work to figure out what I should to create the appropriate Node in the 
ConfigHierarcy.

Could you please tell me what I would need to change or add to get the 
Unserialize method to be invoked?

Thanks
Brinda

  On Wed, 14 Jun 2006, 
Steve Reinhardt wrote:

>
> Yes, that's right... it didn't click when you said before you were in 
> stand-alone mode, but that is true that checkpoints only work in full-system 
> mode because of the way the memory module works.  This is yet another thing 
> we plan to have taken care of in v2.0, but in the meantime if you need the 
> capability soon, your best bet is to put together serialize/unserialize 
> support for the "main memory" object that's used by stand-alone (syscall 
> emulation) mode.
>
> Steve
>
> Brinda Ganesh wrote:
>> Hi
>> 
>> The problem seems that the checkpoint generated does not save relevant 
>> program state. The checkpoint memory section is also completely blank. As a 
>> result in this particular case when the program reaches a point where it 
>> does a check for the input file name - it draws a blank and exits.
>> 
>> On further looking - I find that the functional memory - which has an 
>> associated serialize functionality - is only instatiated in the Full System 
>> build. I am using the Stand Alone model - and would like to know
>> how I could configure my memory sub-system so that a checkpoint retains the 
>> required memory data.
>> 
>> Thanks
>> Brinda
>> 
>>   On Mon, 12 Jun 2006, Brinda Ganesh wrote:
>> 
>>> Hi
>>> 
>>> I am using the Simple CPU in stand-alone mode with at least 2 processors.
>>> I generated checkpoints as described in your tutorial (
>>> using the --Serialize.cycle command line flag). I find that when the
>>> simulator is made to take the input using the checkpoints ( by adding the
>>> command line flag --Root.checkpoint) the simulator runs for several cycles
>>> before halting with the following message
>>>  Terminating simulation -- halt instruction encountered
>>> 
>>> The benchmark when executed without a checkpoitn input does run past this
>>> point.
>>> 
>>> I was wondering if you could tell me what could be the problem and how I
>>> would go about fixing it.
>>> 
>>> Thanks
>>> Brinda
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> m5sim-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/m5sim-users
>>> 
>> 
>> 
>> _______________________________________________
>> m5sim-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/m5sim-users
>

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
m5sim-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m5sim-users

Reply via email to