From: Wang Xin <wangxinxin.wang@huawei.com>
To: <qemu-devel@nongnu.org>
Cc: Wang Xin <wangxinxin.wang@huawei.com>,
jianjay.zhou@huawei.com, weidong.huang@huawei.com,
dgilbert@redhat.com, mst@redhat.com
Subject: [PATCH 0/2][RFC] exclude ivshmem mr from vhost sections
Date: Fri, 28 Aug 2020 17:59:51 +0800 [thread overview]
Message-ID: <20200828095953.2276-1-wangxinxin.wang@huawei.com> (raw)
The ivshmem me now mapped to vhost memory regions, and it reduces
the number of available memslots of vhost backend, which may
causes vhost backend memory slots limit check failure in
vhost dev init.
Since ivshmem_bar2 not normal RAM in Guest, and it shouldn't
have vhost DMAing into them, exclude it from the vhost sections.
The 1st patch re-spin Dave's patch, see link
https://lists.nongnu.org/archive/html/qemu-devel/2020-01/msg02370.html
However, I'm not sure is there any side effects, or maybe it's
better to add a new device property like 'novhost/nodma'?
Thanks,
Xin
Wang Xin (2):
memory: Allow a MemoryRegion to be marked no_vhost
misc/ivshmem: Mark shared memory regions as no vhost
hw/misc/ivshmem.c | 2 ++
hw/virtio/vhost.c | 5 ++++-
include/exec/memory.h | 21 +++++++++++++++++++++
softmmu/memory.c | 15 +++++++++++++++
4 files changed, 42 insertions(+), 1 deletion(-)
--
2.26.0.windows.1
next reply other threads:[~2020-08-28 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 9:59 Wang Xin [this message]
2020-08-28 9:59 ` [PATCH 1/2] memory: Allow a MemoryRegion to be marked no_vhost Wang Xin
2020-08-28 9:59 ` [PATCH 2/2] misc/ivshmem: Mark shared memory regions as no vhost Wang Xin
2020-09-04 4:36 ` [PATCH 0/2][RFC] exclude ivshmem mr from vhost sections Wangxin (Alexander)
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=20200828095953.2276-1-wangxinxin.wang@huawei.com \
--to=wangxinxin.wang@huawei.com \
--cc=dgilbert@redhat.com \
--cc=jianjay.zhou@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=weidong.huang@huawei.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 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).