Skip to content

Conversation

@bertrand-marquis
Copy link
Collaborator

Hi,

Those 3 patches are a proposal to handle the following things that have been discussed:

  • move to an 8 byte header
  • introduce a unique identifier in the header to have a solution to correlate requests to responses
  • relax error handling by the bus by allowing it to report errors to the transport and thus remove the need for the bus to generate dummy responses for transport messages

This is a draft for discussion

Move the header to be 8 bytes and include a unique identifier that can
be use to correlate request to responses.

Rename the msg_id field to msg_op as having a msg_id and msg_uid field
and using identifiers in 2 contexts would have been unclear.

Rework ID to OP and change wording message identifer to message
operation to be coherent in the rest of the specification.

Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
Add a sub-section to do a first explanation draft of how the message
correlation is to be done using a combination of a message device number
and the message unique identifier value.

Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
Relax error handling in the virtio-msg bus and introduce wording to
allow the virtio-msg bus to report error to the virtio-msg transport if
a request could not be transmited or a malformed response was received.

This prevents the need to generate dummy responses in the bus and make
the specification coherent with the current Linux PoC implementation.

Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
@wmamills
Copy link
Collaborator

The commits from this PR were included in PR #25.
That PR includes the changes we agreed to in the Oct 16 meeting

@wmamills wmamills closed this Oct 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants