From: Jason Wang <jasowang@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>,
mst@redhat.com, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: lulu@redhat.com, dan.daly@intel.com, cunming.liang@intel.com
Subject: Re: [PATCH V4 0/3] vdpa: Support config interrupt in vhost_vdpa
Date: Mon, 27 Apr 2020 11:31:05 +0800 [thread overview]
Message-ID: <ff2471ae-254e-7697-72b7-6601a561c3d9@redhat.com> (raw)
In-Reply-To: <1587901406-27400-1-git-send-email-lingshan.zhu@intel.com>
On 2020/4/26 下午7:43, Zhu Lingshan wrote:
> This series includes two patches, one introduced
> config interrupt support in VDPA core, the other
> one implemented config interrupt in IFCVF.
>
> changes from V3:
> move changes in driver/vhost/vhost.c to a
> separated patch.
>
> changes from V2:
> move VHOST_FILE_UNBIND to the uapi header.
>
> changes from V1:
> vdpa: more efficient code to handle eventfd unbind.
> ifcvf: add VIRTIO_NET_F_STATUS feature bit.
5.8 material I think.
Acked-by: Jason Wang <jasowang@redhat.com>
>
> Zhu Lingshan (3):
> vdpa: Support config interrupt in vhost_vdpa
> vhost: replace -1 with VHOST_FILE_UNBIND in iotcls
> vdpa: implement config interrupt in IFCVF
>
> drivers/vdpa/ifcvf/ifcvf_base.c | 3 +++
> drivers/vdpa/ifcvf/ifcvf_base.h | 3 +++
> drivers/vdpa/ifcvf/ifcvf_main.c | 22 ++++++++++++++++++-
> drivers/vhost/vdpa.c | 47 +++++++++++++++++++++++++++++++++++++++++
> drivers/vhost/vhost.c | 8 +++----
> include/uapi/linux/vhost.h | 4 ++++
> 6 files changed, 82 insertions(+), 5 deletions(-)
>
prev parent reply other threads:[~2020-04-27 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 11:43 Zhu Lingshan
2020-04-26 11:43 ` [PATCH V4 1/3] " Zhu Lingshan
2020-04-26 11:43 ` [PATCH V4 2/3] vhost: replace -1 with VHOST_FILE_UNBIND in iotcls Zhu Lingshan
2020-04-26 11:43 ` [PATCH V4 3/3] vdpa: implement config interrupt in IFCVF Zhu Lingshan
2020-04-27 3:31 ` Jason Wang [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=ff2471ae-254e-7697-72b7-6601a561c3d9@redhat.com \
--to=jasowang@redhat.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=kvm@vger.kernel.org \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--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
Powered by JetHome