virtio — archive

[PATCH v10 00/10] Introduce device group and device management

From: Jason Wang <[email protected]>
To: [email protected]
Date: Wed, 08 Mar 2023 05:18:00 -0000

On Wed, Mar 8, 2023 at 3:09?AM Parav Pandit <[email protected]> wrote: > > > > > From: Stefan Hajnoczi <[email protected]> > > Sent: Tuesday, March 7, 2023 2:04 PM > > > An alternative is unconditional out-of-order completion, where there are no > > per-command ordering rules. The driver must wait for a command to complete > > if it relies on the results of that command for its next command. I like this > > approach because it's less complex in the spec and for device implementers, > > while the burden on the driver implementer is still reasonable. > +1. Note that this is the way current ctrl virtqueue works. > This has best of both. > 1. Command ordering knowledge and hence the decision left to the one which issues them. (driver). > 2. Ability to execute multiple unrelated commands using a single AQ. > 3. stateless device in AQ command execution Does this mean if we want to migrate AQ (not use AQ to migrate), we need to wait for the AQ command to be completed? Thanks > > > --------------------------------------------------------------------- > 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 >