Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Memory tracing (executing additional code for every memory access of a program) is a porful technique with many applications, e.g., debugging, taint checking, or tracking dataflow. Current approaches are limited: software-only memory tracing incurs high performance overhead (e.g., for Libdft up to 10×) because every single memory access of the application is checked by additional code that is not part of the original application and hardware is limited to a small set of watched locations.#R##N##R##N# introduces memTrace, a lightight memory tracing technique that builds on dynamic on-the-fly cross-ISA binary translation of 32-bit code to 64-bit code. Our software-only approach enables memory tracing for unmodified, binary-only ×86 applications using the ×64 extension that is available in current CPUs; no OS extensions or special hardware is required. The additional registers in ×64 and the wider memory addressing enable a low-overhead tracing infrastructure that is protected from the application code (i.e., uses disjunct registers and memory regions). MemTrace handles multi-threaded applications. Two case studies discuss a framework for unlimited read and write watchpoints and an allocation-based memory checker similar in functionality to memgrind.#R##N##R##N#The performance evaluation of memTrace shows that the time overhead is beten 1.3× and 3.1× for the SPEC CPU2006 benchmarks, with a geometric mean of 1.97×.
['Mathias Payer', 'Enrico Kravina', 'Thomas R. Gross']
I am writing a research paper on a idea Lightweight memory tracing
[{"from": "human", "value": "I am writing a research paper on a idea Lightweight memory tracing"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Memory tracing (executing additional code for every memory access of a program) is a porful technique with many applications, e.g., debugging, taint checking, or tracking dataflow. Current approaches are limited: software-only memory tracing incurs high performance overhead (e.g., for Libdft up to 10\u00d7) because every single memory access of the application is checked by additional code that is not part of the original application and hardware is limited to a small set of watched locations.#R##N##R##N# introduces memTrace, a lightight memory tracing technique that builds on dynamic on-the-fly cross-ISA binary translation of 32-bit code to 64-bit code. Our software-only approach enables memory tracing for unmodified, binary-only \u00d786 applications using the \u00d764 extension that is available in current CPUs; no OS extensions or special hardware is required. The additional registers in \u00d764 and the wider memory addressing enable a low-overhead tracing infrastructure that is protected from the application code (i.e., uses disjunct registers and memory regions). MemTrace handles multi-threaded applications. Two case studies discuss a framework for unlimited read and write watchpoints and an allocation-based memory checker similar in functionality to memgrind.#R##N##R##N#The performance evaluation of memTrace shows that the time overhead is beten 1.3\u00d7 and 3.1\u00d7 for the SPEC CPU2006 benchmarks, with a geometric mean of 1.97\u00d7."}]