On Thu, Apr 19, 2018 at 10:20 PM, Bryce Patel wrote:
> Thanks for these links, I will look through them for help. The -r option
> indicates the checkpoint number that I want to restore, right? I have been
> using --restore=mtout/cpt.TICKNUMBER but I imagine -r will work similarly.
> Also, I am not
Thanks for these links, I will look through them for help. The -r option
indicates the checkpoint number that I want to restore, right? I have been
using --restore=mtout/cpt.TICKNUMBER but I imagine -r will work similarly.
Also, I am not sure what you mean by the "m5 guest tool". My understanding
i
On Thu, Apr 19, 2018 at 5:03 PM, Bryce Patel wrote:
> Hello,
>
> I am very new to GEM5 and I am wondering how best to simulate thread
> migration on an asymmetric multicore system. I was thinking I could take a
> checkpoint partway through execution using the checkpoint m5op, then use the
> switch
Hello,
I am very new to GEM5 and I am wondering how best to simulate thread
migration on an asymmetric multicore system. I was thinking I could take a
checkpoint partway through execution using the checkpoint m5op, then use
the switchcpu m5op, and then restore the checkpoints on another CPU. My
u
In my work, an application thread needs to run on another core at runtime.
When an application thread calls a pseudo-instruction (written by me),
this migration is triggered.
I want to do this migration from simulator side not to modify
application code for each time.
Different applications ca
It's not obvious to me how to easily emulate a software thread migration
purely inside the simulator. Since the application is triggering the
thread migration anyway, why not do it all in software?
Steve
On Tue, Oct 14, 2014 at 7:11 AM, Sanem Arslan
wrote:
> Hi Steve,
>
> First of all thank yo
Hi Steve,
First of all thank you very much for your response.
I will do thread migration multiple times and this method has
performance overhead due to high drain cycles.
AFAIK, this method is to migrate hardware threads. Actually, I want to
migrate software threads rather than hardware thr
The error you're seeing in your second email is precisely because you're no
longer using drain(). Basically you're in trouble if you switch CPUs while
there's a cache miss outstanding, because then the cache miss response will
come back to the wrong (old) CPU. The point of drain() is to put the
s
Hello again,
I give up to use drain() and switchOut() functions since I only seek
for migrate anapplication thread from one core to another without any
change on cpu type. So I updated my pseudo-instruction like that:
void
my_func(ThreadContext *tc)
{
BaseCPU *oldcpu = tc->getCpuPtr();
Syst
Hello,
I am working on migrating application threads from one core
to another on gem5. I have implemented a pseudo-instruction to trigger
thread migration. When an application thread calls this
pseudo-instruction, I want to migrate the thread to another cpu. My
problem is that I cannot migrate
10 matches
Mail list logo
