Re: Replace calls to functions named cpu_physical_memory_* with address_space_*.

2023-10-27 Thread Thomas Huth
On 26/10/2023 20.21, Tanmay wrote: Yeah, I felt that it may not be a cakewalk as it might sound. You're right, trying to understand the whole code is overwhelming. I'll start with a small section instead. I have interest in working on x86_64 and Aarch64 architectures within qemu. Please let

Re: Replace calls to functions named cpu_physical_memory_* with address_space_*.

2023-10-26 Thread Tanmay
Yeah, I felt that it may not be a cakewalk as it might sound. You're right, trying to understand the whole code is overwhelming. I'll start with a small section instead. I have interest in working on x86_64 and Aarch64 architectures within qemu. Please let me know if there are any specific tasks

Re: Replace calls to functions named cpu_physical_memory_* with address_space_*.

2023-10-26 Thread Peter Maydell
On Thu, 26 Oct 2023 at 13:48, Tanmay wrote: > I'm really interested in contributing to qemu. I wanted to > work on the renaming API calls cpu_physical_memory_* to > address_space_*. I couldn't find any related issues on the > GItlab tracker. Can I work on this issue? You're welcome to, but be

Re: Replace calls to functions named cpu_physical_memory_* with address_space_*.

2023-10-26 Thread Tanmay
Hi, The above refactoring of functions was mentioned under API conversion at https://wiki.qemu.org/Contribute/BiteSizedTasks . Thanks, Tanmay Patil On Thu, 26 Oct 2023 at 15:54, Tanmay wrote: > Hi, > > I'm really interested in contributing to qemu. I wanted to work on the > renaming API calls

Replace calls to functions named cpu_physical_memory_* with address_space_*.

2023-10-26 Thread Tanmay
Hi, I'm really interested in contributing to qemu. I wanted to work on the renaming API calls cpu_physical_memory_* to address_space_*. I couldn't find any related issues on the GItlab tracker. Can I work on this issue? Thanks, Tanmay Patil