Awesome, this is exactly what I needed!
Thanks for the pointers,
-Mark
On Fri, Apr 27, 2012 at 4:54 PM, Steve Reinhardt wrote:
> Or to word it a little more precisely, quiesce the CPU in the system call,
> which will keep it from scheduling new tick events until some other
> condition comes al
Or to word it a little more precisely, quiesce the CPU in the system call,
which will keep it from scheduling new tick events until some other
condition comes along to call wakeup and start scheduling tick events
again. So the system call instruction will complete, but nothing else will
happen on
Hi Mark,
You could return in the system call but schedule an event
that quiesced the CPU in question until a the condition was satisfied.
Thanks,
Ali
On 27.04.2012 16:23, Mark Browning wrote:
> Howdy
all,
> I'm adding custom system calls to provide inter-processor
communication in a s
Howdy all,
I'm adding custom system calls to provide inter-processor communication in
a special purpose network processor. However, I'd like emulate
asynchronous/interrupt based communication, so was hoping to represent this
with a blocking system call. However, it appears that gem5 is single
thre
