Linux Virtualization - Jun 2020 - [PATCH RESEND V2] vdpa: introduce virtio pci driver

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 at 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

>

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 at 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.
> 
> >

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 at 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.

>