Hmm.. That makes some sense. The issue is that the interrupt object that the timing cpu is instantiating is never used. When the switch happens the timing cpu gets attached to the one that the atomic cpu was using. Something that would probably work is assigning the timing cpu's interrupt object to None.
Ali On 22.02.2012 14:31, Nilay Vaish wrote: > Hi > > As you might have noticed there have been several emails on the users > mailing list about the interrupts object not being connected to anything. > As per my understanding this happens only in case of the x86 architecture. > > Here is the situation -- suppose one wants to switch from Atomic CPU to > Timing CPU at time T. Then, the script will create the system and add both > the Atomic and the Timing CPUs. As per my understanding different > Interrupts objects are created for the two CPUs. Since this object is a > PIO device (I think this true only for x86), its init() function is > called. The function works correctly for the Atomic CPU, but in case of > timing CPU it fails as the PIO port of the object is not connected to > anything. > > Any ideas on how to resolve this issue? > > -- > Nilay > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
