Draft 21

virtio-msg: propose common-spec integration text

Update common-spec text so Virtio Over Messages is referenced
from the core device facilities and introduction.

This is a proposal for changes in the virtio common
specification to properly insert the virtio message transport
in the transport-neutral text.

Keep the change minimal for now:
- update content.tex to mention Virtio Over Messages in the
  transport list and in VIRTIO_F_ADMIN_VQ text
- update introduction.tex to mention message-based transports

We could also adapt newtransport.tex, but that is intentionally
left out here to keep the proposal minimal.

Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>

Draft 20

email: adjust cover letter for PATCH v1

* Update cover letter
  * Add link to Arm's virtio-msg FF-A spec
  * Add link to QEMU RFC
  * Add link to LKML RFC
  * Updated Edgar's QEMU branch
  * Text to say this is not an RFC any more
* Update email subject title
* Add Armelle to CC list

Update 3:
* Remove paragraph about how much of bus should be documented

Signed-off-by: Bill Mills <bill.mills@linaro.org>

Draft 19

email: adjust cover letter for PATCH v1

* Update cover letter
  * Add link to Arm's virtio-msg FF-A spec
  * Add link to QEMU RFC
  * Add link to LKML RFC
  * Updated Edgar's QEMU branch
  * Text to say this is not an RFC any more
* Update email subject title
* Add Armelle to CC list

Update 3:
* Remove paragraph about how much of bus should be documented

Signed-off-by: Bill Mills <bill.mills@linaro.org>

Draft 18

virtio-msg: move ping before event_device

To keep messages in the order of the table of IDs, move ping definition
before event_device.

Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>

Draft 17

virtio-msg: fix-up response matching as discussed Oct 23

Simplify the response matching as discussed in the PR and in the Oct 23
meeting.

* Bus messages have a dev_num and it is normally 0 so we don't need to
  say that matching dev_num if only for transport messages.
* Drop msg_id from matching.  Altough the msg_id would normally match
  there may be some cases where it would not.  The token field should
  be unique for a given dev_num.
* This simplifys the description of the matching tuple as well

Signed-off-by: Bill Mills <bill.mills@linaro.org>

Draft 14

virtio-msg: eliminate non-ascii characters

Smart quotes and em-dashes snuck into the doc.
Upstream seems to only use ASCII so eliminate these.

Signed-off-by: Bill Mills <bill.mills@linaro.org>

Draft 16

virtio-msg: Add virtio-msg, a message based virtio transport layer

Add a new transport layer that is based on messages.

This transport layer still uses virtqueues as the other transport layers do
but implements transport layer operations by sending and receiving messages
instead of the "MMR" reads and writes used in virtio-mmio and virtio-pci.

This transport is useful when the device and driver are both implemented in
software but the trap and emulate operations of virtio-mmio and virtio-pci
can not be used.

This transport is intended to be used in many situations, including:
* between a host processor and its co-processors
* between two different systems (not SMP) connected via PCIe
* between normal and secure worlds
* host to vm
* vm to vm

This is an RFC and not yet intended to be merged. There are multiple
know issues including not conforming to virtio spec standards.

Signed-off-by: Bill Mills <bill.mills@linaro.org>
Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
Signed-off-by: Edgar E. Iglesias <edgar.iglesias@amd.com>
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>

Draft 15

virtio-msg: Add virtio-msg, a message based virtio transport layer

Add a new transport layer that is based on messages.

This transport layer still uses virtqueues as the other transport layers do
but implements transport layer operations by sending and receiving messages
instead of the "MMR" reads and writes used in virtio-mmio and virtio-pci.

This transport is useful when the device and driver are both implemented in
software but the trap and emulate operations of virtio-mmio and virtio-pci
can not be used.

This transport is intended to be used in many situations, including:
* between a host processor and its co-processors
* between two different systems (not SMP) connected via PCIe
* between normal and secure worlds
* host to vm
* vm to vm

This is an RFC and not yet intended to be merged. There are multiple
know issues including not conforming to virtio spec standards.

Signed-off-by: Bill Mills <bill.mills@linaro.org>
Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
Signed-off-by: Edgar E. Iglesias <edgar.iglesias@amd.com>
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>

Draft 13

virtio-msg: cover letter, mention more todo items

* As discussed Jun 19, mention work on FF-A spec is underway but don't
  promise a date.
* Do likewise for the AMP data structures and first bus message set
* Do likewise for aligned implementations and PATCH v1

Signed-off-by: Bill Mills <bill.mills@linaro.org>

Draft 11

Merge pull request #21 from wmamills/wam-gh-action-unique-names

github: give tag and pdf names unique to owner fork and branch