On Thu, 7 Dec 2017 19:18:44 +0200
"Michael S. Tsirkin" wrote:
> I see this in ccw in qemu:
>
> if (virtio_set_status(vdev, status) == 0) {
> if (vdev->status == 0) {
> virtio_ccw_reset_virtio(dev, vdev);
> }
> if (st
I see this in ccw in qemu:
if (virtio_set_status(vdev, status) == 0) {
if (vdev->status == 0) {
virtio_ccw_reset_virtio(dev, vdev);
}
if (status & VIRTIO_CONFIG_S_DRIVER_OK) {
virtio_ccw_start_ioeve
On Wed, Jun 01, 2011 at 05:56:02AM +0100, Stefan Hajnoczi wrote:
> Partitions are not at the virtio-blk level. The guest operating
> system will see the virtio-blk disk and scan its partition table to
> determine which partitions are available. The limit then depends on
> the partitioning scheme
On Wed, 1 Jun 2011, Wei Liu wrote:
> That's exactly what I'm seeing...
>
> Maybe I should modify the checking and make a exception for virtio
> disk? Stefano, what would you say?
That is not a check, it is just the upper limit to decode "vda1" or
"vde2" in a disk number and partition number.
I wo
Stefano Stabellini CC'ed
On Wed, Jun 1, 2011 at 12:56 PM, Stefan Hajnoczi wrote:
> On Wed, Jun 1, 2011 at 2:06 AM, Wei Liu wrote:
>> I'm programming for virtio disk support in Xen tool stack. I would
>> like to know the limitation of virtio disk.
>
> I'm interested what you are implementing - a
On Wed, Jun 1, 2011 at 2:06 AM, Wei Liu wrote:
> I'm programming for virtio disk support in Xen tool stack. I would
> like to know the limitation of virtio disk.
I'm interested what you are implementing - a virtio-blk backend for
Xen (which would basically mean vhost-blk)?
> That is, what's the
Hi, all.
I'm programming for virtio disk support in Xen tool stack. I would
like to know the limitation of virtio disk.
That is, what's the maximum number of disks supported through virtio
bus, and what's the maximum number of partitions supported per disk.
If I'm posting to the wrong list, plea
Michael S. Tsirkin wrote:
> Hi!
> I see this in virtio_ring.c:
>
> /* Put entry in available array (but don't update avail->idx *
> until they do sync). */
>
> Why is it done this way?
> It seems that updating the index straight away would be simpler, while
> this might allow the
Hi!
I see this in virtio_ring.c:
/* Put entry in available array (but don't update avail->idx *
until they do sync). */
Why is it done this way?
It seems that updating the index straight away would be simpler, while
this might allow the host to specilatively look up the buffer
