[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32d4c431-24f2-f9f0-8573-268abc7bb71c@intel.com>
Date: Mon, 21 Oct 2019 17:57:28 +0800
From: "Zhu, Lingshan" <lingshan.zhu@...el.com>
To: Jason Wang <jasowang@...hat.com>, mst@...hat.com,
alex.williamson@...hat.com
Cc: linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
netdev@...r.kernel.org, dan.daly@...el.com,
cunming.liang@...el.com, tiwei.bie@...el.com, jason.zeng@...el.com,
zhiyuan.lv@...el.com
Subject: Re: [RFC 1/2] vhost: IFC VF hardware operation layer
On 10/16/2019 4:45 PM, Jason Wang wrote:
>
> On 2019/10/16 上午9:30, Zhu Lingshan wrote:
>> + */
>> +#define IFCVF_TRANSPORT_F_START 28
>> +#define IFCVF_TRANSPORT_F_END 34
>> +
>> +#define IFC_SUPPORTED_FEATURES \
>> + ((1ULL << VIRTIO_NET_F_MAC) | \
>> + (1ULL << VIRTIO_F_ANY_LAYOUT) | \
>> + (1ULL << VIRTIO_F_VERSION_1) | \
>> + (1ULL << VHOST_F_LOG_ALL) | \
>
>
> Let's avoid using VHOST_F_LOG_ALL, using the get_mdev_features() instead.
Thanks, I will remove VHOST_F_LOG_ALL
>
>
>> + (1ULL << VIRTIO_NET_F_GUEST_ANNOUNCE) | \
>> + (1ULL << VIRTIO_NET_F_CTRL_VQ) | \
>> + (1ULL << VIRTIO_NET_F_STATUS) | \
>> + (1ULL << VIRTIO_NET_F_MRG_RXBUF)) /* not fully supported */
>
>
> Why not having VIRTIO_F_IOMMU_PLATFORM and VIRTIO_F_ORDER_PLATFORM?
I will add VIRTIO_F_ORDER_PLATFORM, for VIRTIO_F_IOMMU_PLATFORM, if we
add this bit, QEMU may enable viommu, can cause troubles in LM (through
we don't support LM in this version driver)
Thanks,
BR
Zhu Lingshan
>
> Thanks
>
Powered by blists - more mailing lists