Would it be feasible to introduce a generic virtio device type? #201
Description
In some cases, virtio is simply used as one possible kind of communication channels, such as with virtio-9p. For virtio-9p, it isn't really appropriate to place the core logic inside this crate, because 9PFS can also use other underlying transports like TCP. In terms of transport functionality, the code is too simple and not inherently tied to 9P itself.
A more suitable design would be to treat virtio and TCP as transport layers, while 9P serves as a separate logical abstraction. This approach would help avoid redundant implementations.
|----------------------------|
| 9P (Client) | ←→ 9P Protocol Layer
|----------------------------|
↑
|---------------------------|
| Transport Abstraction | ←→ Generic Transport Interface
|---------------------------|
↑ ↑
|--------| |-------------|
| virtio | | TCP | ←→ Transport Implementations
|--------| |-------------|
In addition, some customized virtio devices may also represent potential demand.