From: David Hildenbrand <david@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
"Jagannathan Raman" <jag.raman@oracle.com>,
"Dr. David Alan Gilbert" <dave@treblig.org>,
"Stefan Zabka" <git@zabka.it>
Subject: Re: [PATCH v2 0/7] physmem: teach cpu_memory_rw_debug() to write to more memory regions
Date: Tue, 4 Feb 2025 16:03:46 +0100 [thread overview]
Message-ID: <715ae765-81c6-4ab4-a00b-c98a9863ffac@redhat.com> (raw)
In-Reply-To: <Z6DzfFvgXw9AQs8p@x1.local>
On 03.02.25 17:49, Peter Xu wrote:
> On Fri, Jan 24, 2025 at 04:45:25PM +0100, David Hildenbrand wrote:
>> This is a follow-up to [1], implementing it by avoiding the use of
>> address_space_write_rom() in cpu_memory_rw_debug() completely, and
>> teaching address_space_write() about debug access instead, the can also
>> write to ROM.
>>
>> The goal is to let GDB via cpu_memory_rw_debug() to also properly write to
>> MMIO device regions, not just RAM/ROM.
>>
>> It's worth noting that other users of address_space_write_rom() are
>> left unchanged. Maybe hw/core/loader.c and friends could now be converted
>> to to a debug access via address_space_write() instead?
>>
>> Survives a basic gitlab CI build/check.
>>
>> [1] https://lore.kernel.org/all/20241220195923.314208-1-git@zabka.it/
>>
>> v1 -> v2:
>> * Split up "physmem: disallow direct access to RAM DEVICE in
>> address_space_write_rom()" into 4 patches
>>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Cc: Peter Xu <peterx@redhat.com>
>> Cc: Philippe Mathieu-Daudé <philmd@linaro.org>
>> Cc: Peter Maydell <peter.maydell@linaro.org>
>> Cc: Alex Bennée <alex.bennee@linaro.org>
>> Cc: Alex Williamson <alex.williamson@redhat.com>
>> Cc: Eduardo Habkost <eduardo@habkost.net>
>> Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
>> Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>
>> Cc: Jagannathan Raman <jag.raman@oracle.com>
>> Cc: "Dr. David Alan Gilbert" <dave@treblig.org>
>> Cc: Stefan Zabka <git@zabka.it>
>>
>> David Hildenbrand (7):
>> physmem: factor out memory_region_is_ram_device() check in
>> memory_access_is_direct()
>> physmem: factor out RAM/ROMD check in memory_access_is_direct()
>> physmem: factor out direct access check into
>> memory_region_supports_direct_access()
>> physmem: disallow direct access to RAM DEVICE in
>> address_space_write_rom()
>
> IIUC the last patch will stop using this for debug path anyway, so I'm not
> sure whether this one is still needed. The hope is it's only used to
> modify real ROMs?
There are still some remaining (other) non-debug users of
address_space_write_rom(), such as hw/core/loader.c.
We could likely remove address_space_write_rom() by adding another
"ignore-non-rom" tx flag, or allow for writing non-rom.
I'm not doing that as part of this series, though.
>
>> memory: pass MemTxAttrs to memory_access_is_direct()
>> hmp: use cpu_get_phys_page_debug() in hmp_gva2gpa()
>> physmem: teach cpu_memory_rw_debug() to write to more memory regions
>
> Still, I can't think of anything harmful of patch 4. So nothing I see
> wrong..
>
> Reviewed-by: Peter Xu <peterx@redhat.com>
Thanks!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-02-04 15:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 15:45 [PATCH v2 0/7] physmem: teach cpu_memory_rw_debug() to write to more memory regions David Hildenbrand
2025-01-24 15:45 ` [PATCH v2 1/7] physmem: factor out memory_region_is_ram_device() check in memory_access_is_direct() David Hildenbrand
2025-01-24 15:45 ` [PATCH v2 2/7] physmem: factor out RAM/ROMD " David Hildenbrand
2025-01-24 15:45 ` [PATCH v2 3/7] physmem: factor out direct access check into memory_region_supports_direct_access() David Hildenbrand
2025-01-24 15:45 ` [PATCH v2 4/7] physmem: disallow direct access to RAM DEVICE in address_space_write_rom() David Hildenbrand
2025-01-24 15:45 ` [PATCH v2 5/7] memory: pass MemTxAttrs to memory_access_is_direct() David Hildenbrand
2025-01-24 16:23 ` Philippe Mathieu-Daudé
2025-01-24 15:45 ` [PATCH v2 6/7] hmp: use cpu_get_phys_page_debug() in hmp_gva2gpa() David Hildenbrand
2025-01-24 16:24 ` Philippe Mathieu-Daudé
2025-01-24 15:45 ` [PATCH v2 7/7] physmem: teach cpu_memory_rw_debug() to write to more memory regions David Hildenbrand
2025-02-03 16:49 ` [PATCH v2 0/7] " Peter Xu
2025-02-04 15:03 ` David Hildenbrand [this message]
2025-02-04 14:46 ` Peter Xu
2025-02-04 15:04 ` David Hildenbrand
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=715ae765-81c6-4ab4-a00b-c98a9863ffac@redhat.com \
--to=david@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=dave@treblig.org \
--cc=eduardo@habkost.net \
--cc=elena.ufimtseva@oracle.com \
--cc=git@zabka.it \
--cc=jag.raman@oracle.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--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).