Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

On Tue, 10 Dec 2024 at 10:20, Philippe Mathieu-Daudé wrote: > > On 10/12/24 11:03, Peter Maydell wrote: > > On Wed, 27 Nov 2024 at 19:20, Philippe Mathieu-Daudé > > wrote: > >> > >> There is no vCPU within the QTest accelerator (well, they > >> are stubs doing nothing, see dummy_cpu_thread_fn).

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

On 10/12/24 11:20, Philippe Mathieu-Daudé wrote: On 10/12/24 11:03, Peter Maydell wrote: On Wed, 27 Nov 2024 at 19:20, Philippe Mathieu-Daudé wrote: There is no vCPU within the QTest accelerator (well, they are stubs doing nothing, see dummy_cpu_thread_fn). Directly use the cpu_physical_memor

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

On 10/12/24 11:03, Peter Maydell wrote: On Wed, 27 Nov 2024 at 19:20, Philippe Mathieu-Daudé wrote: There is no vCPU within the QTest accelerator (well, they are stubs doing nothing, see dummy_cpu_thread_fn). Directly use the cpu_physical_memory_rw() API -- which amusingly prefixed 'cpu_' does

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

On Wed, 27 Nov 2024 at 19:20, Philippe Mathieu-Daudé wrote: > > There is no vCPU within the QTest accelerator (well, they > are stubs doing nothing, see dummy_cpu_thread_fn). > Directly use the cpu_physical_memory_rw() API -- which > amusingly prefixed 'cpu_' does not use vCPU -- to access > memor

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

On 9/12/24 21:34, Fabiano Rosas wrote: Fabiano Rosas writes: Philippe Mathieu-Daudé writes: There is no vCPU within the QTest accelerator (well, they are stubs doing nothing, see dummy_cpu_thread_fn). Directly use the cpu_physical_memory_rw() API -- which amusingly prefixed 'cpu_' does not

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

Fabiano Rosas writes: > Philippe Mathieu-Daudé writes: > >> There is no vCPU within the QTest accelerator (well, they >> are stubs doing nothing, see dummy_cpu_thread_fn). >> Directly use the cpu_physical_memory_rw() API -- which >> amusingly prefixed 'cpu_' does not use vCPU -- to access >> mem

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

Philippe Mathieu-Daudé writes: > There is no vCPU within the QTest accelerator (well, they > are stubs doing nothing, see dummy_cpu_thread_fn). > Directly use the cpu_physical_memory_rw() API -- which > amusingly prefixed 'cpu_' does not use vCPU -- to access > memory. This reduces accesses to th

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

On 27/11/24 23:35, Richard Henderson wrote: On 11/27/24 13:19, Philippe Mathieu-Daudé wrote: There is no vCPU within the QTest accelerator (well, they are stubs doing nothing, see dummy_cpu_thread_fn). Directly use the cpu_physical_memory_rw() API -- which amusingly prefixed 'cpu_' does not use

Re: [PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

On 11/27/24 13:19, Philippe Mathieu-Daudé wrote: There is no vCPU within the QTest accelerator (well, they are stubs doing nothing, see dummy_cpu_thread_fn). Directly use the cpu_physical_memory_rw() API -- which amusingly prefixed 'cpu_' does not use vCPU -- to access memory. This reduces access

[PATCH-for-10.0] system/qtest: Access memory using cpu_physical_memory_rw() API

There is no vCPU within the QTest accelerator (well, they are stubs doing nothing, see dummy_cpu_thread_fn). Directly use the cpu_physical_memory_rw() API -- which amusingly prefixed 'cpu_' does not use vCPU -- to access memory. This reduces accesses to the global 'first_cpu'. Signed-off-by: Phili