[virtio-dev] Re: [virtio-comment] [PATCH 5/5] virtio-pci: implement VIRTIO_F_QUEUE_STATE
Jason Wang <[email protected]>
| Newsgroups | dev.linux.lists.virtio-dev,dev.linux.lists.virtio-comment |
|---|---|
| Message-ID | <CACGkMEtMz3KShVbxpf_DLSx8qde=8JAdPPYOnA_udEfQ8UU+uQ@mail.gmail.com> |
On Wed, Sep 13, 2023 at 12:46 PM Parav Pandit <[email protected]> wrote: > > > From: Jason Wang <[email protected]> > > Sent: Wednesday, September 13, 2023 10:14 AM > > > It's not about how many states in a single state machine, it's about how many > > state machines that exist for device status. Having more than one creates big > > obstacles and complexity in the device. You need to define the interaction of > > each state otherwise you leave undefined behaviours. > The device mode has zero relation to the device status. You will soon get this issue when you want to do nesting. > It does not mess with it at all. > In fact the new bits in device status is making it more complex for the device to handle. Are you challenging the design of the device status? It's definitely too late to do this. This proposal increases just one bit and that worries you? Or you think one more state is much more complicated than a new state machine with two states? Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]