While most objects can perform all their cleanup in the finalizer method, there can be interactions with other resources / subsystems / threads which require that some cleanup be performed on an user creatable object before unparenting it and entering finalization. The current 'can_be_deleted' method runs in the deletion path and is intended to be used to block deletion. While it could be used to perform cleanup tasks, its name suggests it should be free of side-effects. Generalize this by renaming it to 'prepare_delete', explicitly allowing for cleanup to be provided. Existing users of 'can_be_deleted' are re-written, which provides them with more detailed/tailored error messages. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Message-ID: <20260706135824.2623960-2-berrange@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
41 lines
992 B
C
41 lines
992 B
C
/*
|
|
* QEMU event-loop backend
|
|
*
|
|
* Copyright (C) 2022 Red Hat Inc
|
|
*
|
|
* Authors:
|
|
* Nicolas Saenz Julienne <nsaenzju@redhat.com>
|
|
*
|
|
* This work is licensed under the terms of the GNU GPL, version 2 or later.
|
|
* See the COPYING file in the top-level directory.
|
|
*/
|
|
#ifndef QEMU_EVENT_LOOP_BASE_H
|
|
#define QEMU_EVENT_LOOP_BASE_H
|
|
|
|
#include "qom/object.h"
|
|
#include "qemu/aio.h"
|
|
|
|
#define TYPE_EVENT_LOOP_BASE "event-loop-base"
|
|
OBJECT_DECLARE_TYPE(EventLoopBase, EventLoopBaseClass,
|
|
EVENT_LOOP_BASE)
|
|
|
|
struct EventLoopBaseClass {
|
|
ObjectClass parent_class;
|
|
|
|
void (*init)(EventLoopBase *base, Error **errp);
|
|
void (*update_params)(EventLoopBase *base, Error **errp);
|
|
bool (*prepare_delete)(EventLoopBase *base, Error **errp);
|
|
};
|
|
|
|
struct EventLoopBase {
|
|
Object parent;
|
|
|
|
/* AioContext AIO engine parameters */
|
|
int64_t aio_max_batch;
|
|
|
|
/* AioContext thread pool parameters */
|
|
int64_t thread_pool_min;
|
|
int64_t thread_pool_max;
|
|
};
|
|
#endif
|