From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 02/15] system/memory: Factor address_space_memory_is_io() out
Date: Mon, 29 Sep 2025 17:17:57 -0700 [thread overview]
Message-ID: <35e27208-6e6d-4d0f-b563-ae86057387b2@linaro.org> (raw)
In-Reply-To: <20250929183254.85478-3-philmd@linaro.org>
On 9/29/25 11:32, Philippe Mathieu-Daudé wrote:
> Factor address_space_memory_is_io() out of cpu_physical_memory_is_io()
> passing the address space and range length as argument.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/system/memory.h | 10 ++++++++++
> system/physmem.c | 21 ++++++++++++---------
> 2 files changed, 22 insertions(+), 9 deletions(-)
>
> diff --git a/include/system/memory.h b/include/system/memory.h
> index aa85fc27a10..6cfa22d7a80 100644
> --- a/include/system/memory.h
> +++ b/include/system/memory.h
> @@ -3029,6 +3029,16 @@ static inline MemoryRegion *address_space_translate(AddressSpace *as,
> bool address_space_access_valid(AddressSpace *as, hwaddr addr, hwaddr len,
> bool is_write, MemTxAttrs attrs);
>
> +/**
> + * address_space_memory_is_io: check whether an address space range is
> + * I/O memory.
> + *
> + * @as: #AddressSpace to be accessed
> + * @addr: address within that address space
> + * @len: length of the area to be checked
> + */
> +bool address_space_memory_is_io(AddressSpace *as, hwaddr addr, hwaddr len);
I don't think 'len' makes sense.
What are you doing if [addr, addr+len) crosses MemoryRegions?
> +bool address_space_memory_is_io(AddressSpace *as, hwaddr addr, hwaddr len)
> +{
> + MemoryRegion*mr;
Missing space.
> +
> + RCU_READ_LOCK_GUARD();
> + mr = address_space_translate(as, addr, &addr, &len, false,
> + MEMTXATTRS_UNSPECIFIED);
Just pass NULL as the plen parameter.
r~
next prev parent reply other threads:[~2025-09-30 0:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 18:32 [PATCH 00/15] system/physmem: Remove cpu_physical_memory _is_io() and _rw() Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 01/15] docs/devel/loads-stores: Stop mentioning cpu_physical_memory_write_rom() Philippe Mathieu-Daudé
2025-09-30 0:18 ` Richard Henderson
2025-09-29 18:32 ` [PATCH 02/15] system/memory: Factor address_space_memory_is_io() out Philippe Mathieu-Daudé
2025-09-30 0:17 ` Richard Henderson [this message]
2025-09-29 18:32 ` [PATCH 03/15] target/i386/arch_memory_mapping: Use address_space_memory_is_io() Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 04/15] hw/s390x/sclp: Use address_space_memory_is_io() in sclp_service_call() Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 05/15] system/physmem: Remove cpu_physical_memory_is_io() Philippe Mathieu-Daudé
2025-09-30 0:36 ` Richard Henderson
2025-09-29 18:32 ` [PATCH 06/15] system/physmem: Pass address space argument to cpu_flush_icache_range() Philippe Mathieu-Daudé
2025-09-30 0:37 ` Richard Henderson
2025-09-29 18:32 ` [PATCH 07/15] target/s390x/mmu: Replace [cpu_physical_memory -> address_space]_rw() Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 08/15] target/i386/whpx: Replace legacy cpu_physical_memory_rw() call Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 09/15] target/i386/kvm: " Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 10/15] target/i386/nvmm: Inline cpu_physical_memory_rw() in nvmm_mem_callback Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 11/15] hw/xen/hvm: Inline cpu_physical_memory_rw() in rw_phys_req_item() Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 12/15] system/physmem: Un-inline cpu_physical_memory_read/write() Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 13/15] system/physmem: Inline cpu_physical_memory_rw() and remove it Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 14/15] hw/virtio/vhost: Replace legacy cpu_physical_memory_*map() calls Philippe Mathieu-Daudé
2025-09-29 18:32 ` [PATCH 15/15] hw/virtio/virtio: Replace legacy cpu_physical_memory_map() call Philippe Mathieu-Daudé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=35e27208-6e6d-4d0f-b563-ae86057387b2@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).