hw/s390x: Mark the "sclpquiesce" device with user_creatable = false
The "sclpquiesce" device is just an internal device that should not be created by the user directly. Though it currently does not seem to cause any obvious trouble when the user instantiates an additional device, let's better mark it with user_creatable = false to avoid unexpected behavior, e.g. because the quiesce notifier gets registered multiple times. Signed-off-by: Thomas Huth <thuth@redhat.com> Message-Id: <1507193105-15627-1-git-send-email-thuth@redhat.com> Reviewed-by: Halil Pasic <pasic@linux.vnet.ibm.com> Reviewed-by: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
This commit is contained in:
parent
8986db4922
commit
b923ab3112
@ -118,8 +118,13 @@ static void quiesce_class_init(ObjectClass *klass, void *data)
|
||||
dc->reset = quiesce_reset;
|
||||
dc->vmsd = &vmstate_sclpquiesce;
|
||||
set_bit(DEVICE_CATEGORY_MISC, dc->categories);
|
||||
k->init = quiesce_init;
|
||||
/*
|
||||
* Reason: This is just an internal device - the notifier should
|
||||
* not be registered multiple times in quiesce_init()
|
||||
*/
|
||||
dc->user_creatable = false;
|
||||
|
||||
k->init = quiesce_init;
|
||||
k->get_send_mask = send_mask;
|
||||
k->get_receive_mask = receive_mask;
|
||||
k->can_handle_event = can_handle_event;
|
||||
|
Loading…
Reference in New Issue
Block a user