allocating device IDs without a vote
At the Virtio BoF at the virtual KVM forum, 2020, a recurring theme was the difficulty contributors face in obtaining device IDs for new devices. As allocating a new ID is a technicality, and can not break existing devices, it does not sound too bad to skip a voting step in that process.
I'd like to hear TC's take on such an idea.
This would be similar to the existing standing rule:
Minor cleanups, including editorial formatting changes, spelling and typo fixes can be committed directly into git for approval as part of the next specification approval ballot.
Signature · 7 lines
MST --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Quoted 5 lines · * Michael S. Tsirkin ([email protected]) wrote:
At the Virtio BoF at the virtual KVM forum, 2020, a recurring theme was the difficulty contributors face in obtaining device IDs for new devices. As allocating a new ID is a technicality, and can not break existing devices, it does not sound too bad to skip a voting step in that process.
It would seem reasonable to define what the expectations, if any are, about the use of those IDs:
Is it expected that the allocator of such an ID would eventually end a request to merge a spec for the device, or are they free not to?
If merging is expected, then is it acceptable to recycle IDs that have not been defined after n-Years.
Dave
Quoted 28 lines
I'd like to hear TC's take on such an idea.
This would be similar to the existing standing rule:
Minor cleanups, including editorial formatting changes, spelling and typo fixes can be committed directly into git for approval as part of the next specification approval ballot.
Signature · 18 lines
MST This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
Signature · 18 lines
Dr. David Alan Gilbert / [email protected] / Manchester, UK This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
Quoted 10 lines · Dr. David Alan Gilbert
Quoted 5 lines · * Michael S. Tsirkin ([email protected]) wrote:
At the Virtio BoF at the virtual KVM forum, 2020, a recurring theme was the difficulty contributors face in obtaining device IDs for new devices. As allocating a new ID is a technicality, and can not break existing devices, it does not sound too bad to skip a voting step in that process.
It would seem reasonable to define what the expectations, if any are, about the use of those IDs:
Quoted 7 lines
Is it expected that the allocator of such an ID would eventually end a request to merge a spec for the device, or are they free not to?
If merging is expected, then is it acceptable to recycle IDs that have not been defined after n-Years.
Lowering the barrier for grabbing IDs too much and not establishing a garbage collection mechanism can eventually shoot back, IMHO.
Jan
Quoted 31 lines
Dave
Quoted 28 lines
I'd like to hear TC's take on such an idea.
This would be similar to the existing standing rule:
Minor cleanups, including editorial formatting changes, spelling and typo fixes can be committed directly into git for approval as part of the next specification approval ballot.
Signature · 18 lines
MST This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: [email protected] Unsubscribe: [email protected] List help: [email protected] List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/
Signature · 7 lines
Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Quoted 15 lines · On Fri, 30 Oct 2020 11:30:09 +0100 Jan Kiszka <[email protected]> wrote:
Quoted 14 lines · Dr. David Alan Gilbert
Quoted 5 lines · * Michael S. Tsirkin ([email protected]) wrote:
At the Virtio BoF at the virtual KVM forum, 2020, a recurring theme was the difficulty contributors face in obtaining device IDs for new devices. As allocating a new ID is a technicality, and can not break existing devices, it does not sound too bad to skip a voting step in that process.
It would seem reasonable to define what the expectations, if any are, about the use of those IDs:
Is it expected that the allocator of such an ID would eventually end a request to merge a spec for the device, or are they free not to?
Quoted 6 lines
Quoted 3 lines
If merging is expected, then is it acceptable to recycle IDs that have not been defined after n-Years.
Lowering the barrier for grabbing IDs too much and not establishing a garbage collection mechanism can eventually shoot back, IMHO.
Maybe we really need two things:
- a "private" range, that anyone can use for playing etc.
- an easy way to request an ID, combined with some kind of garbage collection
We currently do have some IDs without a spec, but we really need to keep some of them reserved, as there are already (sometimes legacy) devices out there.
Perhaps there needs to be some kind of annotation? If you reserve an ID via the quick mechanism, it gets a "reserved until YYYY-MM-DD", and that tag gets removed when a proper spec is merged? For "in-the-wild-do-not-reuse" IDs, we'd still require a vote, as the default should be to have a proper spec if you want something outside of the private namespace.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
Quoted 35 lines · Cornelia Huck
Quoted 15 lines · On Fri, 30 Oct 2020 11:30:09 +0100 Jan Kiszka <[email protected]> wrote:
Quoted 14 lines · Dr. David Alan Gilbert
Quoted 5 lines · * Michael S. Tsirkin ([email protected]) wrote:
At the Virtio BoF at the virtual KVM forum, 2020, a recurring theme was the difficulty contributors face in obtaining device IDs for new devices. As allocating a new ID is a technicality, and can not break existing devices, it does not sound too bad to skip a voting step in that process.
It would seem reasonable to define what the expectations, if any are, about the use of those IDs:
Is it expected that the allocator of such an ID would eventually end a request to merge a spec for the device, or are they free not to?
Quoted 6 lines
Quoted 3 lines
If merging is expected, then is it acceptable to recycle IDs that have not been defined after n-Years.
Lowering the barrier for grabbing IDs too much and not establishing a garbage collection mechanism can eventually shoot back, IMHO.
Maybe we really need two things:
- a "private" range, that anyone can use for playing etc.
- an easy way to request an ID, combined with some kind of garbage collectionWe currently do have some IDs without a spec, but we really need to keep some of them reserved, as there are already (sometimes legacy) devices out there.
Quoted 6 lines
Perhaps there needs to be some kind of annotation? If you reserve an ID via the quick mechanism, it gets a "reserved until YYYY-MM-DD", and that tag gets removed when a proper spec is merged? For "in-the-wild-do-not-reuse" IDs, we'd still require a vote, as the default should be to have a proper spec if you want something outside of the private namespace.
I agree with Cornelia and Jan.
Thank you,
Mihai Carabas
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
On Fri, Oct 30, 2020 at 01:16:45PM +0100, Cornelia Huck wrote:
Let's clarify whether it is acceptable to keep the device without a spec indefinitely.
I am starting to get the feeling people would like to define one-off VIRTIO devices that are unlikely to be implemented elsewhere.
As VIRTIO expands we may find it acceptable to allow these use cases, but expectations should be clear:
1. VIRTIO spec features won't be added for out-of-tree devices. The user needs to be in the spec so that the design can be reviewed.
2. Out-of-tree devices that violate the VIRTIO device model may cease to work or be impossible to implement as the VIRTIO spec evolves.
Quoted 6 lines
Perhaps there needs to be some kind of annotation? If you reserve an ID via the quick mechanism, it gets a "reserved until YYYY-MM-DD", and that tag gets removed when a proper spec is merged? For "in-the-wild-do-not-reuse" IDs, we'd still require a vote, as the default should be to have a proper spec if you want something outside of the private namespace.
I'm not sure revoking an ID is realistic in the case where the owner refuses to upstream a spec but is shipping devices. The upstream device that reused the ID will suffer when collisions occur.
Stefan