search for: queue_window_idr

...5.7.2 Virtqueues 0 receiveq (RX), 1 transmitq (TX) 5.7.3 Feature Bits Possibly VIRTIO_F_MULTICAST (NOT clear yet left out for now) 5.7.4 Device configuration layout struct virtio_peer_config { le64 queue_data_offset; le32 queue_data_size; u8 queue_flags; /* read-only flags*/ u8 queue_window_idr; /* read-only */ u8 queue_window_idw; /* read-only */ } The fields above are queue-specific, and are thus selected by writing to the queue selector field in the common configuration structure. queue_data_offset is the offset from the start of the Window of the Queue Data area, queue_data_size...

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages