From: Stefano Garzarella <sgarzare@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, Cindy Lu <lulu@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v2] vhost-vdpa: Set discarding of RAM broken when initializing the backend
Date: Thu, 28 Oct 2021 10:45:14 +0200 [thread overview]
Message-ID: <20211028084514.2rbedjsgd3flrfpa@steredhat> (raw)
In-Reply-To: <20211027130324.59791-1-david@redhat.com>
On Wed, Oct 27, 2021 at 03:03:24PM +0200, David Hildenbrand wrote:
>Similar to VFIO, vDPA will go ahead an map+pin all guest memory. Memory
>that used to be discarded will get re-populated and if we
>discard+re-access memory after mapping+pinning, the pages mapped into the
>vDPA IOMMU will go out of sync with the actual pages mapped into the user
>space page tables.
>
>Set discarding of RAM broken such that:
>- virtio-mem and vhost-vdpa run mutually exclusive
>- virtio-balloon is inhibited and no memory discards will get issued
>
>In the future, we might be able to support coordinated discarding of RAM
>as used by virtio-mem and already supported by vfio via the
>RamDiscardManager.
>
>Acked-by: Jason Wang <jasowang@redhat.com>
>Cc: Jason Wang <jasowang@redhat.com>
>Cc: Michael S. Tsirkin <mst@redhat.com>
>Cc: Cindy Lu <lulu@redhat.com>
>Signed-off-by: David Hildenbrand <david@redhat.com>
>---
>
>Unfortuantely, v1 never got picked up no matter how "hard" I tried to
>ping :)
>
>v1 -> v2:
>- Add ack from Jason
>- Extend patch description now that RamDiscardManager is upstream.
>
>---
> hw/virtio/vhost-vdpa.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
prev parent reply other threads:[~2021-10-28 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 13:03 [PATCH v2] vhost-vdpa: Set discarding of RAM broken when initializing the backend David Hildenbrand
2021-10-28 8:45 ` Stefano Garzarella [this message]
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=20211028084514.2rbedjsgd3flrfpa@steredhat \
--to=sgarzare@redhat.com \
--cc=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--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 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.