On Wed, Nov 11, 2020 at 12:19:18PM +0100, Cornelia Huck wrote: > On Tue, 10 Nov 2020 09:53:49 +0000 > Stefan Hajnoczi <stefa...@redhat.com> wrote: > > (...) > > > The meaning of the migration parameter and its possible values are specific > > to > > the device, but values are based on one of the following types: > > * bool - booleans (on/off) > > * int - integers (0, 1, 2, ...) > > * str - character strings > > > > Migration parameters are represented as <name>=<value> in this document. > > Examples include my-feature=on and num-queues=4. > > > > When a new migration parameter is introduced, its absence must have the same > > effect as before the migration parameter was introduced. For example, if > > my-feature=on|off is added to control the availability of a new device > > feature, > > then my-feature=off is equivalent to omitting the migration parameter. > > Maybe this could be made more clear by using a non-bool parameter as > an example? > > For the num-queues parameter used as an example above, if num-queues=2 > would lead to the same effect as before, omitting the num-queues > parameter must be treated as if num-queues had been specified as 2.
Will fix, thanks! Stefan
signature.asc
Description: PGP signature