similar to: [chet.ensign@oasis-open.org: [members] 15-day Public Review for Virtual I/O Device (VIRTIO) V1.0 - ends 14 April]

OASIS members and other interested parties, The Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 04 / Public Review Draft 04 28 May 2015 Specification overview: This document describes the specifications of the

OASIS members and other interested parties, The Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 04 / Public Review Draft 04 28 May 2015 Specification overview: This document describes the specifications of the

OASIS members and other interested parties, The OASIS Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 05 / Public Review Draft 05 29 October 2015 Specification Overview: This document describes the

OASIS members and other interested parties, The OASIS Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 05 / Public Review Draft 05 29 October 2015 Specification Overview: This document describes the

Season's greetings all: The OASIS Virtual I/O Device (VIRTIO) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day(*) public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 01 / Public Review Draft 01 03 December 2013 Specification Overview: This document describes the specifications of the

Season's greetings all: The OASIS Virtual I/O Device (VIRTIO) TC [1] members have recently approved a Committee Specification Draft (CSD) and submitted this specification for 30-day(*) public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 01 / Public Review Draft 01 03 December 2013 Specification Overview: This document describes the specifications of the

On Wed, Feb 08, 2017 at 02:37:57PM +0100, Christian Borntraeger wrote: > On 02/08/2017 04:20 AM, Michael S. Tsirkin wrote: > [...] > > * Prototype > > > > A partial prototype can be found under > > tools/virtio/ringtest/ring.c > > > > Test run: > > [mst at tuck ringtest]$ time ./ring > > real 0m0.399s > > user 0m0.791s > >

On Wed, Feb 08, 2017 at 02:37:57PM +0100, Christian Borntraeger wrote: > On 02/08/2017 04:20 AM, Michael S. Tsirkin wrote: > [...] > > * Prototype > > > > A partial prototype can be found under > > tools/virtio/ringtest/ring.c > > > > Test run: > > [mst at tuck ringtest]$ time ./ring > > real 0m0.399s > > user 0m0.791s > >

Hi Michael, > -----Original Message----- > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > On Behalf Of Michael S. Tsirkin > Sent: Sunday, September 10, 2017 1:06 PM > To: virtio-dev at lists.oasis-open.org > Cc: virtualization at lists.linux-foundation.org > Subject: [virtio-dev] packed ring layout proposal v3 > [...] > *

On Wed, Sep 20, 2017 at 09:11:57AM +0000, Liang, Cunming wrote: > Hi Michael, > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, September 10, 2017 1:06 PM > > To: virtio-dev at lists.oasis-open.org > > Cc: virtualization at

On Wed, Sep 20, 2017 at 09:11:57AM +0000, Liang, Cunming wrote: > Hi Michael, > > > -----Original Message----- > > From: virtio-dev at lists.oasis-open.org [mailto:virtio-dev at lists.oasis-open.org] > > On Behalf Of Michael S. Tsirkin > > Sent: Sunday, September 10, 2017 1:06 PM > > To: virtio-dev at lists.oasis-open.org > > Cc: virtualization at

Michael, Would you please give an example or two how these two flags DESC_DRIVER and DESC_WRAP are used together? Like others, I am confused by the description and still don?t quite grok it. Steven On 9/25/17, 3:24 PM, "virtio-dev at lists.oasis-open.org on behalf of Michael S. Tsirkin" <virtio-dev at lists.oasis-open.org on behalf of mst at redhat.com> wrote: On Wed, Sep

On 02/08/2017 04:20 AM, Michael S. Tsirkin wrote: [...] > * Prototype > > A partial prototype can be found under > tools/virtio/ringtest/ring.c > > Test run: > [mst at tuck ringtest]$ time ./ring > real 0m0.399s > user 0m0.791s > sys 0m0.000s > [mst at tuck ringtest]$ time ./virtio_ring_0_9 > real 0m0.503s > user 0m0.999s > sys

Hi, I am trying to create a tarball from a 4.0.3 git checkout using "make dist", but it throws errors (small sample below, detailed Copy&Paste on request), and apart from this, www.oasis-open.org seems stale on connects from xsltproc, as can be seen in the lsof sample, below as well. Briefly and cheekily asked, is that normal? Are we all omitting docs in packaging at the moment?

*Dear **Madam**/**Sir,* *What would happen if we irrigate the degraded land using the desalinated saline water in Minqin Oasis, Gansu Province, China? Can we prevent the disappearing of Minqin Qasis?* * * *Background:* *1. **The Minqin Oasis is surrounded by two deserts, Badain Jaran Desert and Tengger Desert. * *2. **Water is the root of ecological

Hello, could anyone please help here? I have a program that wants to connect to the Internet for help file videos, price feeds etc. Code: fixme:shdocvw:PersistStreamInit_Load (0x18b708)->(0x18a430) fixme:shdocvw:navigate_url Unsupported args (Flags 0x32eba4:3; TargetFrameName 0x32eb94:3) fixme:shdocvw:OleObject_Close (0x18b708)->(1) fixme:shdocvw:PersistStreamInit_Load

On 2017?09?10? 13:06, Michael S. Tsirkin wrote: > This is an update from v2 version. > Changes: > - update event suppression mechanism > - add wrap counter: DESC_WRAP flag in addition to > DESC_DRIVER flag used for validity so device does not have to > write out all used descriptors. Do we have benchmark result to show the advantage of DESC_DRIVER over e.g avail/used

On Mon, Jan 19, 2015 at 05:45:54PM +0000, Pawel Moll wrote: > On Thu, 2015-01-15 at 19:12 +0000, Michael S. Tsirkin wrote: > > > > > > > > > +static struct device_attribute vm_dev_attr_version = > > > > > > > > > + __ATTR(version, S_IRUGO, vm_dev_attr_version_show, NULL); > > > > > > > > > + > >

On Mon, Jan 19, 2015 at 05:45:54PM +0000, Pawel Moll wrote: > On Thu, 2015-01-15 at 19:12 +0000, Michael S. Tsirkin wrote: > > > > > > > > > +static struct device_attribute vm_dev_attr_version = > > > > > > > > > + __ATTR(version, S_IRUGO, vm_dev_attr_version_show, NULL); > > > > > > > > > + > >

On Thu, Jan 15, 2015 at 06:51:01PM +0200, Michael S. Tsirkin wrote: > Host no longer knows the alignment, so why is it needed? > In fact, I notice that 4.3.2.3 Virtqueue Layout seems completely wrong: > it corresponds to legacy devices, and it does not > say what "align" is. I created https://issues.oasis-open.org/browse/VIRTIO-129 to track this. Can you write up a patch