From: Mattias Nissler <mnissler@rivosinc.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Xu" <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Richard Henderson <richard.henderson@linaro.org>,
john.levon@nutanix.com,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/3] system/physmem: Propagate AddressSpace to MapClient helpers
Date: Tue, 7 May 2024 14:47:33 +0200 [thread overview]
Message-ID: <CAGNS4Ta9aV7ch5DCdMe=Pk3eB_3+0xx8fCekvuiAPb6hz=Yx_g@mail.gmail.com> (raw)
In-Reply-To: <20240507123025.93391-1-philmd@linaro.org>
On Tue, May 7, 2024 at 2:30 PM Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>
> Respin of Mattias patch [1 split to ease review.
> Preliminary use QEMU_LOCK_GUARD to simplify.
>
> I'm OK to include this and the endianness fix [2]
> if Mattias agrees, once first patch is reviewed.
To be honest, given that this patch series has been lingering for
almost a year now, I'm fine with whatever gets us closer to getting
this landed. I believe Peter was also considering doing a pull request
for the series, so you may want to coordinate with him if you haven't
already.
>
>
> Regards,
>
> Phil.
>
> [1 https://lore.kernel.org/qemu-devel/20240507094210.300566-2-mnissler@rivosinc.com/
> [2] https://lore.kernel.org/qemu-devel/20240507094210.300566-6-mnissler@rivosinc.com/
>
> Mattias Nissler (2):
> system/physmem: Propagate AddressSpace to MapClient helpers
> system/physmem: Per-AddressSpace bounce buffering
>
> Philippe Mathieu-Daudé (1):
> system/physmem: Replace qemu_mutex_lock() calls with QEMU_LOCK_GUARD
>
> include/exec/cpu-common.h | 2 -
> include/exec/memory.h | 45 +++++++++++++++++-
> system/dma-helpers.c | 4 +-
> system/memory.c | 7 +++
> system/physmem.c | 98 +++++++++++++++------------------------
> 5 files changed, 90 insertions(+), 66 deletions(-)
>
> --
> 2.41.0
>
next prev parent reply other threads:[~2024-05-07 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 12:30 [PATCH 0/3] system/physmem: Propagate AddressSpace to MapClient helpers Philippe Mathieu-Daudé
2024-05-07 12:30 ` [PATCH 1/3] system/physmem: Replace qemu_mutex_lock() calls with QEMU_LOCK_GUARD Philippe Mathieu-Daudé
2024-05-07 16:37 ` Richard Henderson
2024-05-07 12:30 ` [PATCH 2/3] system/physmem: Propagate AddressSpace to MapClient helpers Philippe Mathieu-Daudé
2024-05-07 12:30 ` [PATCH 3/3] system/physmem: Per-AddressSpace bounce buffering Philippe Mathieu-Daudé
2024-05-07 12:38 ` Philippe Mathieu-Daudé
2024-05-07 12:47 ` Mattias Nissler [this message]
2024-05-07 14:02 ` [PATCH 0/3] system/physmem: Propagate AddressSpace to MapClient helpers Philippe Mathieu-Daudé
2024-05-07 14:10 ` Mattias Nissler
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='CAGNS4Ta9aV7ch5DCdMe=Pk3eB_3+0xx8fCekvuiAPb6hz=Yx_g@mail.gmail.com' \
--to=mnissler@rivosinc.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=david@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=john.levon@nutanix.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).