reserve device ID for hwsim wireless simulation
PATCH 1/1 reserve device ID for hwsim wireless simulation
From: Johannes Berg <[email protected]>
The Linux mac80211-hwsim module currently allows simulation of multiple wireless radios on a shared medium, and has an existing API for this to work through a userspace implementation of the medium simulation (e.g. implemented by wmediumd).
In order to simplify working with virtual machines and to enable (time-compressed) simulation use cases, allocate a virtio device ID to allow carrying this protocol over virtio in addition to the current netlink sockets.
Since device ID 28 was previously requested, use 29.
---
There's an existing allocation of ID 10 for "mac80211 wlan" that has - to my knowledge as the maintainer of mac80211 - never been used anywhere, and I'm not familiar with the allocation for it.
It seems pretty safe to use that number here, if that's better?
--- content.tex | 2 ++ 1 file changed, 2 insertions(+)
content.tex +2 -0
@@ -2795,6 +2795,8 @@ \chapter{Device Types}\label{sec:Device Types} \hline 27 & PMEM device \\ \hline +29 & mac80211 hwsim wireless simulation device \\ +\hline \end{tabular} Some of the devices above are unspecified by this document,
Signature · 18 lines
2.20.1 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/
Hi,
Quoted 11 lines
The Linux mac80211-hwsim module currently allows simulation of multiple wireless radios on a shared medium, and has an existing API for this to work through a userspace implementation of the medium simulation (e.g. implemented by wmediumd).
In order to simplify working with virtual machines and to enable (time-compressed) simulation use cases, allocate a virtio device ID to allow carrying this protocol over virtio in addition to the current netlink sockets.
Since device ID 28 was previously requested, use 29.
I evidently forgot to request a TC vote on this before, hereby doing that.
Thanks,
johannes
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/
Hi,
Quoted 13 lines · Johannes Berg
Hi,
Quoted 10 lines
The Linux mac80211-hwsim module currently allows simulation of multiple wireless radios on a shared medium, and has an existing API for this to work through a userspace implementation of the medium simulation (e.g. implemented by wmediumd).
In order to simplify working with virtual machines and to enable (time-compressed) simulation use cases, allocate a virtio device ID to allow carrying this protocol over virtio in addition to the current netlink sockets.
Quoted 6 lines
Quoted 1 line
Since device ID 28 was previously requested, use 29.
I evidently forgot to request a TC vote on this before, hereby doing that.
Is a TC vote for this issue in progress? I cannot find this issue in this list:
https://www.oasis-open.org/committees/ballots.php?wg_abbrev=virtio
I'm waiting for this issue resolved to request device ID 30 for video devices in https://github.com/oasis-tcs/virtio-spec/issues/67
Best regards,
Keiichi
Quoted 12 lines
Thanks,
johannesThis 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.
Quoted 9 lines
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/
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/
Hi,
Quoted 7 lines
Quoted 4 lines
I evidently forgot to request a TC vote on this before, hereby doing that.
Is a TC vote for this issue in progress? I cannot find this issue in this list:
https://www.oasis-open.org/committees/ballots.php?wg_abbrev=virtio
I have no idea what's going on, who's shepherding the process, who to ping, or anything like that, sorry.
Right now I was biding my time and ignoring the issue for now, but it'll come up again soon since I do want to upstream the code for this that we already have ...
So if anyone else has any thoughts, I'd greatly appreciate it.
Quoted 2 lines
I'm waiting for this issue resolved to request device ID 30 for video devices in https://github.com/oasis-tcs/virtio-spec/issues/67
I guess you don't really need to have this resolved to request a vote on the video device ID?
johannes
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/
Hi,
Quoted 18 lines · Johannes Berg
Hi,
Quoted 7 lines
Quoted 4 lines
I evidently forgot to request a TC vote on this before, hereby doing that.
Is a TC vote for this issue in progress? I cannot find this issue in this list:
https://www.oasis-open.org/committees/ballots.php?wg_abbrev=virtioI have no idea what's going on, who's shepherding the process, who to ping, or anything like that, sorry.
Right now I was biding my time and ignoring the issue for now, but it'll come up again soon since I do want to upstream the code for this that we already have ...
Quoted 7 lines
So if anyone else has any thoughts, I'd greatly appreciate it.
Quoted 2 lines
I'm waiting for this issue resolved to request device ID 30 for video devices in https://github.com/oasis-tcs/virtio-spec/issues/67
I guess you don't really need to have this resolved to request a vote on the video device ID?
You're right. I just requested a TC vote for my change. Thanks.
Best regards,
Keiichi
Quoted 3 lines
johannes
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 4 lines · Johannes Berg
I evidently forgot to request a TC vote on this before, hereby doing that.
Maybe this got lost in the noise? Or did I do something wrong?
Thanks,
johannes
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/
Hi all,
[...]
Quoted 1 line
Since device ID 28 was previously requested, use 29.
I see that IDs 30 and 31 have been allocated
(https://github.com/oasis-tcs/virtio-spec/issues/67)
and they specifically pointed out that they skipped 29 that was requested here...
TBH, this feels very arbitrary, and I'm just stuck on this thread here all by myself without any comments.
Can somebody please point out to me what I should be doing?
Thanks,
johannes
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 · On Wed, 11 Mar 2020 10:03:55 +0100 Johannes Berg <[email protected]>…
Hi all,
[...]
Quoted 1 line
Since device ID 28 was previously requested, use 29.
I see that IDs 30 and 31 have been allocated
(https://github.com/oasis-tcs/virtio-spec/issues/67)
and they specifically pointed out that they skipped 29 that was requested here...
Quoted 7 lines
TBH, this feels very arbitrary, and I'm just stuck on this thread here all by myself without any comments.
Can somebody please point out to me what I should be doing?
Thanks,
johannes
^^ Michael, can you please open a ballot? It seems I can't do that...
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/