[dpdk-dev] [PATCH] vhost: Fix default value of kickfd and callfd

2016-03-10 Thread Tetsuya Mukawa
On 2016/03/10 15:39, Tan, Jianfeng wrote: > > On 3/10/2016 2:34 PM, Tetsuya Mukawa wrote: >> On 2016/03/10 15:25, Tan, Jianfeng wrote: >>> >>> On 3/10/2016 2:14 PM, Tetsuya Mukawa wrote: Currently, default value of kickfd and callfd is -1. If the value is -1, current code guess kickfd and

[dpdk-dev] [PATCH] vhost: Fix default value of kickfd and callfd

2016-03-10 Thread Tetsuya Mukawa
On 2016/03/10 15:25, Tan, Jianfeng wrote: > > > On 3/10/2016 2:14 PM, Tetsuya Mukawa wrote: >> Currently, default value of kickfd and callfd is -1. >> If the value is -1, current code guess kickfd and callfd hasn't been >> initialized yet. And vhost library will guess the virtqueue isn't ready >> f

[dpdk-dev] [PATCH] vhost: Fix default value of kickfd and callfd

2016-03-10 Thread Tetsuya Mukawa
Currently, default value of kickfd and callfd is -1. If the value is -1, current code guess kickfd and callfd hasn't been initialized yet. And vhost library will guess the virtqueue isn't ready for processing. But callfd and kickfd will be set as -1 when "--enable-kvm" isn't specified in QEMU comma

[dpdk-dev] [PATCH] vhost: Fix default value of kickfd and callfd

2016-03-10 Thread Tan, Jianfeng
On 3/10/2016 2:34 PM, Tetsuya Mukawa wrote: > On 2016/03/10 15:25, Tan, Jianfeng wrote: >> >> On 3/10/2016 2:14 PM, Tetsuya Mukawa wrote: >>> Currently, default value of kickfd and callfd is -1. >>> If the value is -1, current code guess kickfd and callfd hasn't been >>> initialized yet. And vhost

[dpdk-dev] [PATCH] vhost: Fix default value of kickfd and callfd

2016-03-10 Thread Tan, Jianfeng
On 3/10/2016 2:14 PM, Tetsuya Mukawa wrote: > Currently, default value of kickfd and callfd is -1. > If the value is -1, current code guess kickfd and callfd hasn't been > initialized yet. And vhost library will guess the virtqueue isn't ready > for processing. > But callfd and kickfd will be set