Displaying 10 results from an estimated 10 matches for "ifc_supported_featur".
Did you mean:
ifc_supported_features
2019 Nov 05
1
[PATCH 1/2] IFC hardware operation layer
...t; +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */
> +#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 << VIRTIO_F_ORDER_PLATFORM) | \
ACCESS_PLATFORM must be enabled for sure?
> + (1ULL << VIRTIO_NET_F_GUEST_ANN...
2019 Oct 16
0
[RFC 1/2] vhost: IFC VF hardware operation layer
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.
> + (1ULL &l...
2019 Oct 21
0
[RFC 1/2] vhost: IFC VF hardware operation layer
.../10/21 ??5:57, Zhu, Lingshan wrote:
>
> 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)??????????? | \
>>
>>...
2019 Nov 08
0
[PATCH 1/2] IFC hardware operation layer
...t; +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */
> +#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 << VIRTIO_F_ORDER_PLATFORM) | \
> + (1ULL << VIRTIO_NET_F_GUEST_ANNOUNCE) | \
> + (1ULL << VIRTIO_NE...
2019 Oct 21
0
[RFC 2/2] vhost: IFC VF vdpa layer
...f (vring->cb.callback)
>>> +??????? return vring->cb.callback(vring->cb.private);
>>> +
>>> +??? return IRQ_HANDLED;
>>> +}
>>> +
>>> +static u64 ifcvf_mdev_get_features(struct mdev_device *mdev)
>>> +{
>>> +??? return IFC_SUPPORTED_FEATURES;
>>
>>
>> I would expect this should be done by querying the hw. Or IFC VF
>> can't get any update through its firmware?
>
> Hi Jason,
>
> Thanks for your comments, for now driver just support these features.
Ok, it should work but less flexible, we can...
2019 Nov 05
0
[PATCH 1/2] IFC hardware operation layer
...t; +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */
> +#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 << VIRTIO_F_ORDER_PLATFORM) | \
> + (1ULL << VIRTIO_NET_F_GUEST_ANNOUNCE) | \
> + (1ULL << VIRTIO_NE...
2019 Oct 16
0
[RFC 2/2] vhost: IFC VF vdpa layer
...q, void *arg)
> +{
> + struct vring_info *vring = arg;
> +
> + if (vring->cb.callback)
> + return vring->cb.callback(vring->cb.private);
> +
> + return IRQ_HANDLED;
> +}
> +
> +static u64 ifcvf_mdev_get_features(struct mdev_device *mdev)
> +{
> + return IFC_SUPPORTED_FEATURES;
I would expect this should be done by querying the hw. Or IFC VF can't
get any update through its firmware?
> +}
> +
> +static int ifcvf_mdev_set_features(struct mdev_device *mdev, u64 features)
> +{
> + struct ifcvf_adapter *adapter = mdev_get_drvdata(mdev);
> + struc...
2019 Nov 06
0
[PATCH 1/2] IFC hardware operation layer
...t; +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */
> +#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 << VIRTIO_F_ORDER_PLATFORM) | \
> + (1ULL << VIRTIO_NET_F_GUEST_ANNOUNCE) | \
> + (1ULL << VIRTIO_NE...
2019 Oct 16
0
[RFC 1/2] vhost: IFC VF hardware operation layer
...t; +/*
> + * Some ifcvf feature bits (currently bits 28 through 31) are
> + * reserved for the transport being used (eg. ifcvf_ring), the
> + * rest are per-device feature bits.
> + */
> +#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) | \
> + (1ULL << VIRTIO_NET_F_GUEST_ANNOUNCE) | \
> + (1ULL << VIRTIO_NET_F_CTRL...
2019 Oct 21
0
[RFC 1/2] vhost: IFC VF hardware operation layer
...28 through 31) are
>>> + * reserved for the transport being used (eg. ifcvf_ring), the
>>> + * rest are per-device feature bits.
>>> + */
>>> +#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)??????????? | \
>>> +????...