From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: eric.fangyi@huawei.com, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Jiang Dongxu <jiangdongxu1@huawei.com>,
eperezma <eperezma@redhat.com>,
longpeng2@huawei.com, Siwei Liu <loseweigh@gmail.com>
Subject: Re: [PATCH 0/2] vdpa: Add logging operatins
Date: Wed, 18 Oct 2023 11:07:31 -0400 [thread overview]
Message-ID: <20231018110719-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEsP+3nTjG8gj0PoYg0DvyqqOpJKoAxG=m27t+iv-6GVbQ@mail.gmail.com>
On Mon, Sep 11, 2023 at 02:56:58PM +0800, Jason Wang wrote:
> 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
Seems to be stuck. Dropped this for now.
> >
> > 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
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Jiang Dongxu <jiangdongxu1@huawei.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, longpeng2@huawei.com,
eric.fangyi@huawei.com, eperezma <eperezma@redhat.com>,
Siwei Liu <loseweigh@gmail.com>
Subject: Re: [PATCH 0/2] vdpa: Add logging operatins
Date: Wed, 18 Oct 2023 11:07:31 -0400 [thread overview]
Message-ID: <20231018110719-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEsP+3nTjG8gj0PoYg0DvyqqOpJKoAxG=m27t+iv-6GVbQ@mail.gmail.com>
On Mon, Sep 11, 2023 at 02:56:58PM +0800, Jason Wang wrote:
> 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
Seems to be stuck. Dropped this for now.
> >
> > 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
> >
next prev parent reply other threads:[~2023-10-18 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 1:23 [PATCH 0/2] vdpa: Add logging operatins Jiang Dongxu
2023-08-26 1:23 ` [PATCH 1/2] vdpa: add log operations Jiang Dongxu
2023-08-26 1:23 ` [PATCH 2/2] vhost-vdpa: add uAPI for logging Jiang Dongxu
2023-09-11 6:56 ` [PATCH 0/2] vdpa: Add logging operatins Jason Wang
2023-09-11 6:56 ` Jason Wang
2023-10-18 15:07 ` Michael S. Tsirkin [this message]
2023-10-18 15:07 ` Michael S. Tsirkin
2023-11-01 13:01 ` 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=20231018110719-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=jasowang@redhat.com \
--cc=jiangdongxu1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longpeng2@huawei.com \
--cc=loseweigh@gmail.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 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.