From: Jason Wang <jasowang@redhat.com>
To: Jiang Dongxu <jiangdongxu1@huawei.com>
Cc: eric.fangyi@huawei.com, mst@redhat.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
eperezma <eperezma@redhat.com>,
longpeng2@huawei.com, Siwei Liu <loseweigh@gmail.com>
Subject: Re: [PATCH 0/2] vdpa: Add logging operatins
Date: Mon, 11 Sep 2023 14:56:58 +0800 [thread overview]
Message-ID: <CACGkMEsP+3nTjG8gj0PoYg0DvyqqOpJKoAxG=m27t+iv-6GVbQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1693012755.git.jiangdongxu1@huawei.com>
Adding Eugenio and Si Wei.
On Sat, Aug 26, 2023 at 9:24 AM Jiang Dongxu <jiangdongxu1@huawei.com> wrote:
>
> From: jiangdongxu <jiangdongxu1@huawei.com>
>
> Currently, the vdpa device supports suspend and resume operations.
> To support vdpa device live migration, we need to support logging
> operations and device state save/load opertions.
>
> These series introduces some new operations for vdpa devices.
> They allow vdpa to enable logging while vm start live migration.
>
> And I will submit another patches about saving and loading
> vdpa device state later.
Thanks for working on this, I have several questions:
1) Is there an example implementation of the logging in the drivers?
We need a real user in order to merge this.
2) Is the logging based on IOVA or VA? How the DMA isolation is being
done with this? Do we need a SET_LOGGING_ASID uAPI for this? (We had
some discussion on this in the past).
Thanks
>
> jiangdongxu (2):
> vdpa: add log operations
> vhost-vdpa: add uAPI for logging
>
> drivers/vhost/vdpa.c | 49 ++++++++++++++++++++++++++++++++++++++
> include/linux/vdpa.h | 14 +++++++++++
> include/uapi/linux/vhost.h | 4 ++++
> 3 files changed, 67 insertions(+)
>
> --
> 2.27.0
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next parent reply other threads:[~2023-09-11 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1693012755.git.jiangdongxu1@huawei.com>
2023-09-11 6:56 ` Jason Wang [this message]
2023-10-18 15:07 ` [PATCH 0/2] vdpa: Add logging operatins Michael S. Tsirkin
2023-11-01 13:01 ` Michael S. Tsirkin
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='CACGkMEsP+3nTjG8gj0PoYg0DvyqqOpJKoAxG=m27t+iv-6GVbQ@mail.gmail.com' \
--to=jasowang@redhat.com \
--cc=eperezma@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=jiangdongxu1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=loseweigh@gmail.com \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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).