|
From: G N S. P. <gns...@ii...> - 2022-08-05 18:52:33
|
This is the first time we are using Valgrind, and we want to know if we can get a list of all the physical addresses the program used, in the order the program accessed them, and whether read/write. Please let us know if we can get this from Valgrind - the webpage information is not clear. Thanks Prasanna |
|
From: Paul F. <pj...@wa...> - 2022-08-05 19:30:44
|
> On 5 Aug 2022, at 20:53, G N Srinivasa Prasanna <gns...@ii...> wrote: > > > This is the first time we are using Valgrind, and we want to know if we can get a list of all the physical addresses the program used, in the order the program accessed them, and whether read/write. > > Please let us know if we can get this from Valgrind - the webpage information is not clear. > Hi Why do you need this? I’m not sure how to translate from virtual to physical address. Do you really mean physical address? For any real world application the size of the log would be overwhelmingly huge and I suspect would very rapidly fill most disks (unless you only want unique addresses). A+ Paul |
|
From: John R. <jr...@bi...> - 2022-08-05 19:49:06
|
>> if we can get a list of all the physical addresses the program used, in the order the program accessed them, and whether read/write. > For any real world application the size of the log would be overwhelmingly huge ... (unless you only want unique addresses). Of course this is the purpose of data compression (such as gzip, etc). You get some/much/most of the benefit of restricting to unique addresses while still capturing the entire stream of references. But as Paul noted, valgrind works in virtual addresses. Getting all the actual physical addresses is close to impossible. If you are working in an embedded device environment and care only about a small handful of memory-mapped device registers, then you can (must) process the mapping yourself. |
|
From: G N S. P. <gns...@ii...> - 2022-08-06 00:47:29
|
Thanks for this information. We are doing a memory system simulation, and need the address stream. At this point of time, we don't care if we need a Terabyte even, we can delete the files later. Is there anything we can use from Valgrind? Best ________________________________ From: John Reiser <jr...@bi...> Sent: 06 August 2022 01:18 To: val...@li... <val...@li...> Subject: Re: [Valgrind-users] Valgrind trace Memory Addresses while running? >> if we can get a list of all the physical addresses the program used, in the order the program accessed them, and whether read/write. > For any real world application the size of the log would be overwhelmingly huge ... (unless you only want unique addresses). Of course this is the purpose of data compression (such as gzip, etc). You get some/much/most of the benefit of restricting to unique addresses while still capturing the entire stream of references. But as Paul noted, valgrind works in virtual addresses. Getting all the actual physical addresses is close to impossible. If you are working in an embedded device environment and care only about a small handful of memory-mapped device registers, then you can (must) process the mapping yourself. _______________________________________________ Valgrind-users mailing list Val...@li... https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Eliot M. <mo...@cs...> - 2022-08-06 02:05:51
|
On 8/5/2022 8:47 PM, G N Srinivasa Prasanna wrote: > Thanks for this information. > > We are doing a memory system simulation, and need the address stream. At this point of time, we > don't care if we need a Terabyte even, we can delete the files later. > > Is there anything we can use from Valgrind? The lackey tool does just that - output a trace of memory references. -- Eliot Moss |
|
From: G N S. P. <gns...@ii...> - 2022-08-06 01:49:20
|
Thanks, will check it out. Best ________________________________ From: Eliot Moss <mo...@cs...> Sent: 06 August 2022 07:10 To: G N Srinivasa Prasanna <gns...@ii...>; John Reiser <jr...@bi...>; val...@li... <val...@li...> Subject: Re: [Valgrind-users] Valgrind trace Memory Addresses while running? On 8/5/2022 8:47 PM, G N Srinivasa Prasanna wrote: > Thanks for this information. > > We are doing a memory system simulation, and need the address stream. At this point of time, we > don't care if we need a Terabyte even, we can delete the files later. > > Is there anything we can use from Valgrind? The lackey tool does just that - output a trace of memory references. -- Eliot Moss |