tps://github.com/gem5/linux-arm-gem5-legacy/commit/516ba2d255b502b1dad07662bd18110f3bf37b1b
>>
>>
>>
>> *From:* gem5-users [mailto:gem5-users-boun...@gem5.org] *On Behalf Of *Shehab
>> Elsayed
>> *Sent:* Friday, January 11, 2019 10:58 PM
>> *To:* gem5 users mailin
ithub.com/gem5/linux-arm-gem5-legacy/commit/516ba2d255b502b1dad07662bd18110f3bf37b1b
>
>
>
> *From:* gem5-users [mailto:gem5-users-boun...@gem5.org] *On Behalf Of *Shehab
> Elsayed
> *Sent:* Friday, January 11, 2019 10:58 PM
> *To:* gem5 users mailing list
> *Subject:* Re: [gem5-users] [EXT] Acc
: gem5-users [mailto:gem5-users-boun...@gem5.org] On Behalf Of Shehab
Elsayed
Sent: Friday, January 11, 2019 10:58 PM
To: gem5 users mailing list
Subject: Re: [gem5-users] [EXT] Accessing logical (software) thread ID in gem5
Thank you all for your help. I have been trying to to get what Paul
Thank you all for your help. I have been trying to to get what Paul
suggested to work, however, I keep running into this problem:
warn: Unable to find kernel symbol thread_info_task
warn: Kernel not compiled with task_struct info; can't get currently
executing task/process/thread name/ids!
I am n
You could take the approach previously implemented by ARM, which is to add a
few annotations to your kernel that allow you to find the task_info structures
in kernel memory and then ask gem5 to hook the kernel process switch function.
Each time the kernel context switches on a core, you get a ca
