From: Jason Wang <jasowang@redhat.com>
To: David Hildenbrand <david@redhat.com>,
qemu-devel@nongnu.org, Xie Yongji <xieyongji@bytedance.com>
Cc: Cindy Lu <lulu@redhat.com>, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v1] vhost-vdpa: Set discarding of RAM broken when initializing the backend
Date: Thu, 4 Mar 2021 17:37:27 +0800 [thread overview]
Message-ID: <58b4e30e-d9ed-395b-2a23-03a04fb58060@redhat.com> (raw)
In-Reply-To: <2cd5c10c-0c85-b5a4-de06-30d7ee30661a@redhat.com>
On 2021/3/4 5:34 下午, David Hildenbrand wrote:
> On 04.03.21 10:32, Jason Wang wrote:
>>
>> On 2021/3/3 6:26 下午, David Hildenbrand wrote:
>>> On 03.03.21 03:53, Jason Wang wrote:
>>>>
>>>> On 2021/3/3 12:21 上午, 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 as planned for VFIO.
>>>>>
>>>>> 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>
>>>>
>>>>
>>>> Acked-by: Jason Wang <jasowang@redhat.com>
>>>>
>>>>
>>>>> ---
>>>>>
>>>>> Note: I was not actually able to reproduce/test as I fail to get the
>>>>> vdpa_sim/vdpa_sim_net running on upstream Linux (whetever vdpa,
>>>>> vhost_vdpa,
>>>>> vdpa_sim, vdpa_sim_net modules I probe, and in which order, no vdpa
>>>>> devices
>>>>> appear under /sys/bus/vdpa/devices/ or /dev/).
>>>>
>>>>
>>>> The device creation was switched to use vdpa tool that is integrated
>>>> with iproue2[1].
>>>>
>>>> [1]
>>>> https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=143610383da51e1f868c6d5a2a5e2fb552293d18
>>>>
>>>>
>>>
>>> It would be great to document that somewhere if not already done. I
>>> only found older RH documentations that were not aware of that. I'll
>>> give it a try - thanks!
>>
>>
>> Will think about this. Which RH doc do you refer here? Is this the
>> redhat blog?
>
> https://www.redhat.com/en/blog/hands-vdpa-what-do-you-do-when-you-aint-got-hardware
>
>
> As it's supposed to be from October 14, 2020 I was surprised to not
> get it running (even with older kernels IIRC).
Right, the mgmt API is just merged. Will try to see if we can fix the blog.
Thanks
next prev parent reply other threads:[~2021-03-04 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 16:21 [PATCH v1] vhost-vdpa: Set discarding of RAM broken when initializing the backend David Hildenbrand
2021-03-03 2:53 ` Jason Wang
2021-03-03 10:26 ` David Hildenbrand
2021-03-03 10:37 ` David Hildenbrand
2021-03-04 9:32 ` Jason Wang
2021-03-04 9:34 ` David Hildenbrand
2021-03-04 9:37 ` Jason Wang [this message]
2021-04-29 7:51 ` 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=58b4e30e-d9ed-395b-2a23-03a04fb58060@redhat.com \
--to=jasowang@redhat.com \
--cc=david@redhat.com \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xieyongji@bytedance.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).