From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gao Shiyuan <gaoshiyuan@baidu.com>
Cc: Tiwei Bie <tiwei.bie@intel.com>,
zuoboqun@baidu.com, qemu-devel@nongnu.org,
Jason Wang <jasowang@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 1/1] virtio-pci: return RAM device MR when set host notifier success
Date: Fri, 16 Aug 2024 06:29:33 -0400 [thread overview]
Message-ID: <20240816061647-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20240812122027.65600-1-gaoshiyuan@baidu.com>
On Mon, Aug 12, 2024 at 08:20:27PM +0800, Gao Shiyuan wrote:
> When vhost-user backend register memory region based host notifiers,
> we should return RAM device MR of notify region MR's subregion in
> virtio_address_space_lookup.
>
> In seabios, it will use virtio PCI Configration Access Capability
> access notify region when assign notify region above 4GB. This will
> exit to QEMU and invoke virtio_address_space_write. When vhost-user
> backend register memory region based host notifiers, return RAM device
> MR instead of notify region MR is suitable.
I can't really parse this.
> Co-developed-by: Zuo Boqun <zuoboqun@baidu.com>
> Signed-off-by: Gao Shiyuan <gaoshiyuan@baidu.com>
> Signed-off-by: Zuo Boqun <zuoboqun@baidu.com>
CC Jason
> ---
> hw/virtio/virtio-pci.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> index 9534730bba..167ac9718a 100644
> --- a/hw/virtio/virtio-pci.c
> +++ b/hw/virtio/virtio-pci.c
> @@ -610,13 +610,22 @@ static MemoryRegion *virtio_address_space_lookup(VirtIOPCIProxy *proxy,
> {
> int i;
> VirtIOPCIRegion *reg;
> + MemoryRegion *mr, *submr;
>
> for (i = 0; i < ARRAY_SIZE(proxy->regs); ++i) {
> reg = &proxy->regs[i];
> if (*off >= reg->offset &&
> *off + len <= reg->offset + reg->size) {
> *off -= reg->offset;
> - return ®->mr;
> + mr = ®->mr;
> + QTAILQ_FOREACH(submr, &mr->subregions, subregions_link) {
> + if (*off >= submr->addr &&
> + *off + len < submr->addr + submr->size) {
> + *off -= submr->addr;
> + return submr;
> + }
> + }
> + return mr;
> }
> }
Poking at internals of MR like this is not nice.
Doesn't memory_region_find work for this?
>
> --
> 2.39.3 (Apple Git-146)
next prev parent reply other threads:[~2024-08-16 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 12:20 [PATCH 1/1] virtio-pci: return RAM device MR when set host notifier success Gao Shiyuan via
2024-08-16 10:12 ` Gao,Shiyuan via
2024-08-16 10:29 ` Michael S. Tsirkin [this message]
2024-08-16 12:12 ` Jason Wang
2024-08-16 12:33 ` Gao,Shiyuan via
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=20240816061647-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=gaoshiyuan@baidu.com \
--cc=jasowang@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tiwei.bie@intel.com \
--cc=zuoboqun@baidu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.