search for: csprd01

...potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work. URIs: The prose specification document and related files are available here: PDF (Authoritative): http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.pdf HTML: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.html Editable TeX Source: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/tex/ For your convenience, OASIS provides a complete package of the prose specification and related files in a Z...

...potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work. URIs: The prose specification document and related files are available here: PDF (Authoritative): http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.pdf HTML: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.html Editable TeX Source: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/tex/ For your convenience, OASIS provides a complete package of the prose specification and related files in a Z...

...t; I am worried about the possibility that it will loop forever. > Could that happen? > > ... My understanding is that the function here is similar to virtio config generation [1]. So this can only happen for a buggy hardware. Thanks [1] https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.html Section 2.4.1 > >>>> +static void io_write64_twopart(u64 val, u32 *lo, u32 *hi) >>>> +{ >>>> + iowrite32(val & ((1ULL << 32) - 1), lo); >>>> + iowrite32(val >> 32, hi); >>>> +} >>> I...

...queue on PPS. Great job, thanks! Pls allow a bit more review time than usual as this is a big patchset. Should be done by Tuesday. -next material anyway. > More optimizations (e.g IN_ORDER) is on the road. > > Please review. > > [1] https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.html#x1-610007 > > This version were tested with: > - zercopy/datacopy > - mergeable buffer on/off > - TCP stream & virtio-user > > Changes from V2: > - rebase on top of vhost metadata accelreation series > - introduce shadow used ring API > -...

...ual I/O Device (VIRTIO) Technical Committee http://www.oasis-open.org/committees/virtio/ [2] Previous public reviews: 30-day public review, 24 December 2014: https://lists.oasis-open.org/archives/ members/201312/msg00013.html - Comment resolution log: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01 /virtio-v1.0-csprd01-comment-resolution-log.xlsx [3] http://www.oasis-open.org/policies-guidelines/ipr [4] http://www.oasis-open.org/committees/virtio/ipr.php https://www.oasis-open.org/policies-guidelines/ipr#licensing_req Non-Assertion Mode -- /chet ---------------- Chet Ensign Director of...

...ual I/O Device (VIRTIO) Technical Committee http://www.oasis-open.org/committees/virtio/ [2] Previous public reviews: 30-day public review, 24 December 2014: https://lists.oasis-open.org/archives/ members/201312/msg00013.html - Comment resolution log: http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01 /virtio-v1.0-csprd01-comment-resolution-log.xlsx [3] http://www.oasis-open.org/policies-guidelines/ipr [4] http://www.oasis-open.org/committees/virtio/ipr.php https://www.oasis-open.org/policies-guidelines/ipr#licensing_req Non-Assertion Mode -- /chet ---------------- Chet Ensign Director of...

...T: address space not found. FAULT: mapping not found. RANGE: request would split a mapping. [VIRTIO-v1.0] Virtual I/O Device (VIRTIO) Version 1.0. 03 December 2013. Committee Speci?cation Draft 01 / Public Review Draft 01. http://docs.oasis-open.org/virtio/virtio/v1.0/csprd01/virtio-v1.0-csprd01.html

...;vhost: access vq metadata through kernel virtual address"), such overhead cold be eliminated. So in this version, we can see about 2% improvement for packed virtqueue on PPS. More optimizations (e.g IN_ORDER) is on the road. Please review. [1] https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.html#x1-610007 This version were tested with: - zercopy/datacopy - mergeable buffer on/off - TCP stream & virtio-user Changes from V2: - rebase on top of vhost metadata accelreation series - introduce shadow used ring API - new SET_VRING_BASE/GET_VRING_BASE that takes care...

...;vhost: access vq metadata through kernel virtual address"), such overhead cold be eliminated. So in this version, we can see about 2% improvement for packed virtqueue on PPS. More optimizations (e.g IN_ORDER) is on the road. Please review. [1] https://docs.oasis-open.org/virtio/virtio/v1.1/csprd01/virtio-v1.1-csprd01.html#x1-610007 This version were tested with: - zercopy/datacopy - mergeable buffer on/off - TCP stream & virtio-user Changes from V2: - rebase on top of vhost metadata accelreation series - introduce shadow used ring API - new SET_VRING_BASE/GET_VRING_BASE that takes care...

This is the initial proposal for a paravirtualized IOMMU device using virtio transport. It contains a description of the device, a Linux driver, and a toy implementation in kvmtool. With this prototype, you can translate DMA to guest memory from emulated (virtio), or passed-through (VFIO) devices. In its simplest form, implemented here, the device handles map/unmap requests from the guest. Future

This is the initial proposal for a paravirtualized IOMMU device using virtio transport. It contains a description of the device, a Linux driver, and a toy implementation in kvmtool. With this prototype, you can translate DMA to guest memory from emulated (virtio), or passed-through (VFIO) devices. In its simplest form, implemented here, the device handles map/unmap requests from the guest. Future