On 1/9/19 3:55 PM, Michael S. Tsirkin wrote:
On Wed, Jan 09, 2019 at 05:50:12PM +0300, Ilya Maximets wrote:
Version 3:
* Added 2 patches with fixes for current virtio driver.
Not directly connected with the new feature.
New version shouldn't be reply-to old one really :).
But the pa
On 1/9/2019 3:24 PM, Ilya Maximets wrote:
> On 09.01.2019 17:55, Michael S. Tsirkin wrote:
>> On Wed, Jan 09, 2019 at 05:50:12PM +0300, Ilya Maximets wrote:
>>> Version 3:
>>> * Added 2 patches with fixes for current virtio driver.
>>> Not directly connected with the new feature.
>>
>> New ve
On 09.01.2019 17:55, Michael S. Tsirkin wrote:
> On Wed, Jan 09, 2019 at 05:50:12PM +0300, Ilya Maximets wrote:
>> Version 3:
>> * Added 2 patches with fixes for current virtio driver.
>> Not directly connected with the new feature.
>
> New version shouldn't be reply-to old one really :).
I
On Wed, Jan 09, 2019 at 05:50:12PM +0300, Ilya Maximets wrote:
> Version 3:
> * Added 2 patches with fixes for current virtio driver.
> Not directly connected with the new feature.
New version shouldn't be reply-to old one really :).
But the patches are good I think.
Acked-by: Michael S. Ts
Version 3:
* Added 2 patches with fixes for current virtio driver.
Not directly connected with the new feature.
Version 2:
* rebased on current master (packed rings).
RFC --> Version 1:
* Dropped vendor-specific hack to determine if we need real barriers.
* Added VIRTIO_F_ORDER_PLATFO
5 matches
Mail list logo