Hi Everyone,
I pushed a major change to the pull request for the spec here: https://github.com/Linaro/virtio-msg-spec/pull/16
I reworked the chapters and the content to look a lot more like other virtio transports and follow the sentence convention (MUST, SHALL, SHOULD).
Some sentences have been reworded with the help of chatgpt so we need to have a careful review of this but i think it looks a lot better than before.
please review based on the final content and not using the tree of patches as the last one is more or less rewriting everything.
Some things to think of: - message format description: should we switch to structures instead of tables ? I did that for the header and channel I/O is using structures which might look better - global terminology: i struggle a bit between driver/device vs frontend/backend and we must have a check on the coherency - compliance: this is the bare output of chatgpt more for discussing than keeping it but it could give us ideas if we want to have something (Warning the compliance chapter content might be wrong).
As always: any comments are welcome :-)
Cheers Bertrand
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi all,
Last week we said we would have a spec focused call this week in the normal timeslot. I forgot I had a different call at that time. I could cancel that call or we could find a different time.
I put together a poll here: https://doodle.com/meeting/participate/id/bDW96Q5a
NOTE: I included tomorrow but that will only be possible if a critical mass responds today.
Thanks, Bill
On 3/31/25 12:52 PM, Bertrand Marquis wrote:
Hi Everyone,
I pushed a major change to the pull request for the spec here: https://github.com/Linaro/virtio-msg-spec/pull/16
I reworked the chapters and the content to look a lot more like other virtio transports and follow the sentence convention (MUST, SHALL, SHOULD).
Some sentences have been reworded with the help of chatgpt so we need to have a careful review of this but i think it looks a lot better than before.
please review based on the final content and not using the tree of patches as the last one is more or less rewriting everything.
Some things to think of:
- message format description: should we switch to structures instead of tables ? I did that for the header and channel I/O is using structures which might look better
- global terminology: i struggle a bit between driver/device vs frontend/backend and we must have a check on the coherency
- compliance: this is the bare output of chatgpt more for discussing than keeping it but it could give us ideas if we want to have something (Warning the compliance chapter content might be wrong).
As always: any comments are welcome :-)
Cheers Bertrand
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Virtio-msg mailing list -- virtio-msg@lists.linaro.org To unsubscribe send an email to virtio-msg-leave@lists.linaro.org
Hi Bill,
On 1 Apr 2025, at 16:14, Bill Mills bill.mills@linaro.org wrote:
Hi all,
Last week we said we would have a spec focused call this week in the normal timeslot. I forgot I had a different call at that time. I could cancel that call or we could find a different time.
I put together a poll here: https://doodle.com/meeting/participate/id/bDW96Q5a
Just an FYI that I am on leave on friday and next week.
Also i pushed a new version of the spec which should be a lot nearer to what would be an acceptable plan and content to the repo so would be nice for participants in the discussion to have a quick look at it before.
I enclosed the pdf version for it to this mail.
Cheers Bertrand
NOTE: I included tomorrow but that will only be possible if a critical mass responds today.
Thanks, Bill
On 3/31/25 12:52 PM, Bertrand Marquis wrote:
Hi Everyone,
I pushed a major change to the pull request for the spec here: https://github.com/Linaro/virtio-msg-spec/pull/16
I reworked the chapters and the content to look a lot more like other virtio transports and follow the sentence convention (MUST, SHALL, SHOULD).
Some sentences have been reworded with the help of chatgpt so we need to have a careful review of this but i think it looks a lot better than before.
please review based on the final content and not using the tree of patches as the last one is more or less rewriting everything.
Some things to think of:
- message format description: should we switch to structures instead of tables ? I did that for the header and channel I/O is using structures which might look better
- global terminology: i struggle a bit between driver/device vs frontend/backend and we must have a check on the coherency
- compliance: this is the bare output of chatgpt more for discussing than keeping it but it could give us ideas if we want to have something (Warning the compliance chapter content might be wrong).
As always: any comments are welcome :-)
Cheers Bertrand
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Virtio-msg mailing list -- virtio-msg@lists.linaro.org To unsubscribe send an email to virtio-msg-leave@lists.linaro.org
-- Bill Mills Principal Technical Consultant, Linaro +1-240-643-0836 TZ: US Eastern Work Schedule: Tues/Wed/Thur
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-
Bertrand Marquis -
Bill Mills