[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 10/10] exec: Move cpu_physical_memory_* functions to 'exec/me
|
From: |
Juan Quintela |
|
Subject: |
Re: [PATCH 10/10] exec: Move cpu_physical_memory_* functions to 'exec/memory-internal.h' |
|
Date: |
Fri, 08 May 2020 10:12:53 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Philippe Mathieu-Daudé <address@hidden> wrote:
> Signed-off-by: Philippe Mathieu-Daudé <address@hidden>
Once here, can someone give a test that meassures if it makes sense that
this functions are inline?
They are relatively big, and I would preffer them to be in a .c file,
but I have no clue about how performance critical they are.
Again, this include was another of the reasons that migration/ram.c
can't be make target agnostic.
Later, Juan.
- [PATCH 07/10] exec: Move all RAMBlock functions to 'exec/ramblock.h', (continued)
- [PATCH 07/10] exec: Move all RAMBlock functions to 'exec/ramblock.h', Philippe Mathieu-Daudé, 2020/05/07
- [PATCH 08/10] hw/block: Let the NVMe emulated device be target-agnostic, Philippe Mathieu-Daudé, 2020/05/07
- [PATCH 09/10] exec: Update coding style to make checkpatch.pl happy, Philippe Mathieu-Daudé, 2020/05/07
- [PATCH 10/10] exec: Move cpu_physical_memory_* functions to 'exec/memory-internal.h', Philippe Mathieu-Daudé, 2020/05/07
- Re: [PATCH 00/10] exec: Shear 'exec/ram_addr.h' and make NVMe device target-agnostic, Paolo Bonzini, 2020/05/07
- Re: [PATCH 00/10] exec: Shear 'exec/ram_addr.h' and make NVMe device target-agnostic, no-reply, 2020/05/08