Re: [PATCH 08/12] qom: allow for properties to become "fixed"

2023-04-17 Thread Peter Maydell
On Mon, 17 Apr 2023 at 12:33, Alex Bennée wrote: > The use-case is this whole series. Basically I want to have a generic > device (vhost-user-device) which has a bunch of control knobs the user > can fiddle with (e.g. virtio id, num_vqs and the like). However for the > specialised versions of this

Re: [PATCH 08/12] qom: allow for properties to become "fixed"

2023-04-17 Thread Alex Bennée
Markus Armbruster writes: > Alex Bennée writes: > >> When specialising general purpose objects it is sometimes useful to >> "fix" some of the properties that were configurable by the base >> classes. We will use this facility when specialising >> vhost-user-device. >> >> Signed-off-by: Alex Be

Re: [PATCH 08/12] qom: allow for properties to become "fixed"

2023-04-17 Thread Markus Armbruster
Alex Bennée writes: > When specialising general purpose objects it is sometimes useful to > "fix" some of the properties that were configurable by the base > classes. We will use this facility when specialising > vhost-user-device. > > Signed-off-by: Alex Bennée > --- > qapi/qom.json

[PATCH 08/12] qom: allow for properties to become "fixed"

2023-04-14 Thread Alex Bennée
When specialising general purpose objects it is sometimes useful to "fix" some of the properties that were configurable by the base classes. We will use this facility when specialising vhost-user-device. Signed-off-by: Alex Bennée --- qapi/qom.json | 2 ++ include/qom/object.h| 16