...
- an additional flag to request more detailded GL error reporting to the client
3.4 IOMMU Device
NOTE: The current specification draft looks quite neat except the fact that it marks many requirements as SHOULD or MAY and leaves it for an implementation. Here I try to provide more strict rules when it is applicable.
REQ-1: Requirement according to chapter 2.1 in [VIRTIO-IOMMU].
REQ-2: Requirement according to chapter 2.2 in [VIRTIO-IOMMU].
REQ-3: Requirement according to chapter 2.3 in [VIRTIO-IOMMU].
REQ-4: Requirement according to chapter 2.4 in [VIRTIO-IOMMU].
REQ-5: Requirement according to chapter 2.5 in [VIRTIO-IOMMU].
REQ-5.1: As for chapter 2.5.2, the requirement is to be read as SHALL NOT.
REQ-6: Requirement according to chapter 2.6 in [VIRTIO-IOMMU].
REQ-6.1: As for chapter 2.6.2, MAY and SHOULD are to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
REQ-6.2: As for chapter 2.6.3.2, SHOULD is to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
REQ-6.3: As for chapter 2.6.4.2, SHOULD is to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
REQ-6.4: As for chapter 2.6.5.2 SHOULD is to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
REQ-6.5: As for chapter 2.6.6.2 SHOULD is to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
REQ-6.6: As for chapter 2.6.7.2 MAY and SHOULD are to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
REQ-6.7: As for chapter 2.6.8.2.2 SHOULD is to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
REQ-6.8: As for chapter 2.6.9.2 SHOULD is to be read as MUST, SHOULD NOT is to be read as SHALL NOT.
4. Supplemental Virtual Device categories
...
[VIRTIO-VIRGL] [AN OASIS STANDARD PROPOSAL OR OWN PAPER IS NEEDED] https://github.com/Keenuts/virtio-gpu-documentation/blob/master/src/virtio-gpu.md
[VIRTIO-IOMMU] VIRTIO-IOMMU DRAFT 0.8