From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: shahafs@mellanox.com, lulu@redhat.com, saugatm@xilinx.com,
mhabets@solarflare.com, vmireyno@marvell.com,
linux-kernel@vger.kernel.org, gdawar@xilinx.com,
virtualization@lists.linux-foundation.org, eperezma@redhat.com,
hanand@xilinx.com, zhangweining@ruijie.com.cn, eli@mellanox.com,
lingshan.zhu@intel.com, rob.miller@broadcom.com
Subject: Re: [PATCH RESEND V2] vdpa: introduce virtio pci driver
Date: Wed, 10 Jun 2020 14:29:01 +0800 [thread overview]
Message-ID: <be938f8f-8f98-b55e-34b8-b0faf560ef30@redhat.com> (raw)
In-Reply-To: <20200610022030-mutt-send-email-mst@kernel.org>
On 2020/6/10 下午2:21, Michael S. Tsirkin wrote:
> On Wed, Jun 10, 2020 at 02:16:26PM +0800, Jason Wang wrote:
>> On 2020/6/10 下午2:07, Michael S. Tsirkin wrote:
>>> On Wed, Jun 10, 2020 at 01:49:51PM +0800, Jason Wang wrote:
>>>> This patch introduce a vDPA driver for virtio-pci device. It bridges
>>>> the virtio-pci control command to the vDPA bus. This will be used for
>>>> developing new features for both software vDPA framework and hardware
>>>> vDPA feature.
>>>>
>>>> Compared to vdpa_sim, it has several advantages:
>>>>
>>>> - it's a real device driver which allow us to play with real hardware
>>>> features
>>>> - type independent instead of networking specific
>>>>
>>>> Note that since virtio specification does not support get/restore
>>>> virtqueue state. So we can not use this driver for VM. This can be
>>>> addressed by extending the virtio specification.
>>>>
>>>> Consider the driver is mainly for testing and development for vDPA
>>>> features, it can only be bound via dynamic ids to make sure it's not
>>>> conflict with the drivers like virtio-pci or IFCVF.
>>>>
>>>> Signed-off-by: Jason Wang<jasowang@redhat.com>
>>> error: sha1 information is lacking or useless (drivers/vdpa/Kconfig).
>>>
>>> which tree is this on top of?
>>
>> Your vhost.git vhost branch, HEAD is bbea3bcfd1d6 vdpa: fix typos in the
>> comments for __vdpa_alloc_device()
>>
>> Do I need to use other branch?
>>
>> Thanks
> No it's ok, I am just wondering why doesn't it apply then.
I found the reason, I generate the patch on another branch whose base
does not existed in the vhost branch. Will repost.
Sorry.
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2020-06-10 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 5:49 [PATCH RESEND V2] vdpa: introduce virtio pci driver Jason Wang
2020-06-10 6:07 ` Michael S. Tsirkin
2020-06-10 6:16 ` Jason Wang
2020-06-10 6:21 ` Michael S. Tsirkin
2020-06-10 6:29 ` 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=be938f8f-8f98-b55e-34b8-b0faf560ef30@redhat.com \
--to=jasowang@redhat.com \
--cc=eli@mellanox.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mhabets@solarflare.com \
--cc=mst@redhat.com \
--cc=rob.miller@broadcom.com \
--cc=saugatm@xilinx.com \
--cc=shahafs@mellanox.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vmireyno@marvell.com \
--cc=zhangweining@ruijie.com.cn \
/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).