ted with it, as well as a MasterID. You should be able
>> to access these at the DRAM controller if that’s
>> > what you’re after. Note that you end up getting requests without this
>> information (write backs etc), so you cannot always rely on it.
>> >
>> > A
hese at the DRAM controller if that’s
> > what you’re after. Note that you end up getting requests without this
> information (write backs etc), so you cannot always rely on it.
> >
> > Andreas
> >
> >
> >
> > From: Prathap Kolakkampadath gmail.com>R
; Andreas
>
>
>
> From: Prathap Kolakkampadath gmail.com>Reply-To: gem5
users mailing list gem5.org>Date: Monday, 30 March 2015
17:27To: gem5 users mailing list gem5.org>Subject:
[gem5-users] Tracking DRAM requests from a process
>
>
>
>
>
>
t; these at the DRAM controller if that’s what you’re after. Note that you end
>> up getting requests without this information (write backs etc), so you
>> cannot always rely on it.
>>
>> Andreas
>>
>> From: Prathap Kolakkampadath
>> Reply-To: gem5 users ma
ers mailing list
> Subject: [gem5-users] Tracking DRAM requests from a process
>
> Hello Users,
>
> I am running Gem5 on ARM FS mode using classic memory system. I am
> running two process on a single core. I need to track the DRAM requests
> (memory access latency) of
mailing list mailto:gem5-users@gem5.org>>
Subject: [gem5-users] Tracking DRAM requests from a process
Hello Users,
I am running Gem5 on ARM FS mode using classic memory system. I am running two
process on a single core. I need to track the DRAM requests (memory access
latency) of a particu
Hello Users,
I am running Gem5 on ARM FS mode using classic memory system. I am running
two process on a single core. I need to track the DRAM requests (memory
access latency) of a particular process. Is it possible to identify the
process id of a linux process in the DRAM Controller layer?
Thank
