2009-08-28 22:27:04 +04:00
|
|
|
/*
|
|
|
|
* QEMU Object Model.
|
|
|
|
*
|
|
|
|
* Based on ideas by Avi Kivity <avi@redhat.com>
|
|
|
|
*
|
2015-04-30 00:35:05 +03:00
|
|
|
* Copyright (C) 2009, 2015 Red Hat Inc.
|
2009-08-28 22:27:04 +04:00
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Luiz Capitulino <lcapitulino@redhat.com>
|
|
|
|
*
|
2010-05-12 23:34:42 +04:00
|
|
|
* This work is licensed under the terms of the GNU LGPL, version 2.1 or later.
|
|
|
|
* See the COPYING.LIB file in the top-level directory.
|
2009-08-28 22:27:04 +04:00
|
|
|
*
|
|
|
|
* QObject Reference Counts Terminology
|
|
|
|
* ------------------------------------
|
|
|
|
*
|
|
|
|
* - Returning references: A function that returns an object may
|
|
|
|
* return it as either a weak or a strong reference. If the reference
|
|
|
|
* is strong, you are responsible for calling QDECREF() on the reference
|
|
|
|
* when you are done.
|
|
|
|
*
|
|
|
|
* If the reference is weak, the owner of the reference may free it at
|
|
|
|
* any time in the future. Before storing the reference anywhere, you
|
|
|
|
* should call QINCREF() to make the reference strong.
|
|
|
|
*
|
|
|
|
* - Transferring ownership: when you transfer ownership of a reference
|
|
|
|
* by calling a function, you are no longer responsible for calling
|
|
|
|
* QDECREF() when the reference is no longer needed. In other words,
|
|
|
|
* when the function returns you must behave as if the reference to the
|
|
|
|
* passed object was weak.
|
|
|
|
*/
|
|
|
|
#ifndef QOBJECT_H
|
|
|
|
#define QOBJECT_H
|
|
|
|
|
qapi: Convert QType into QAPI built-in enum type
What's more meta than using qapi to define qapi? :)
Convert QType into a full-fledged[*] builtin qapi enum type, so
that a subsequent patch can then use it as the discriminator
type of qapi alternate types. Fortunately, the judicious use of
'prefix' in the qapi definition avoids churn to the spelling of
the enum constants.
To avoid circular definitions, we have to flip the order of
inclusion between "qobject.h" vs. "qapi-types.h". Back in commit
28770e0, we had the latter include the former, so that we could
use 'QObject *' for our implementation of 'any'. But that usage
also works with only a forward declaration, whereas the
definition of QObject requires QType to be a complete type.
[*] The type has to be builtin, rather than declared in
qapi/common.json, because we want to use it for alternates even
when common.json is not included. But since it is the first
builtin enum type, we have to add special cases to qapi-types
and qapi-visit to only emit definitions once, even when two
qapi files are being compiled into the same binary (the way we
already handled builtin list types like 'intList'). We may
need to revisit how multiple qapi files share common types,
but that's a project for another day.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1449033659-25497-4-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2015-12-02 08:20:47 +03:00
|
|
|
#include "qapi-types.h"
|
2009-08-28 22:27:04 +04:00
|
|
|
|
qapi: Convert QType into QAPI built-in enum type
What's more meta than using qapi to define qapi? :)
Convert QType into a full-fledged[*] builtin qapi enum type, so
that a subsequent patch can then use it as the discriminator
type of qapi alternate types. Fortunately, the judicious use of
'prefix' in the qapi definition avoids churn to the spelling of
the enum constants.
To avoid circular definitions, we have to flip the order of
inclusion between "qobject.h" vs. "qapi-types.h". Back in commit
28770e0, we had the latter include the former, so that we could
use 'QObject *' for our implementation of 'any'. But that usage
also works with only a forward declaration, whereas the
definition of QObject requires QType to be a complete type.
[*] The type has to be builtin, rather than declared in
qapi/common.json, because we want to use it for alternates even
when common.json is not included. But since it is the first
builtin enum type, we have to add special cases to qapi-types
and qapi-visit to only emit definitions once, even when two
qapi files are being compiled into the same binary (the way we
already handled builtin list types like 'intList'). We may
need to revisit how multiple qapi files share common types,
but that's a project for another day.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1449033659-25497-4-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2015-12-02 08:20:47 +03:00
|
|
|
struct QObject {
|
2015-12-02 08:20:46 +03:00
|
|
|
QType type;
|
2009-08-28 22:27:04 +04:00
|
|
|
size_t refcnt;
|
qapi: Convert QType into QAPI built-in enum type
What's more meta than using qapi to define qapi? :)
Convert QType into a full-fledged[*] builtin qapi enum type, so
that a subsequent patch can then use it as the discriminator
type of qapi alternate types. Fortunately, the judicious use of
'prefix' in the qapi definition avoids churn to the spelling of
the enum constants.
To avoid circular definitions, we have to flip the order of
inclusion between "qobject.h" vs. "qapi-types.h". Back in commit
28770e0, we had the latter include the former, so that we could
use 'QObject *' for our implementation of 'any'. But that usage
also works with only a forward declaration, whereas the
definition of QObject requires QType to be a complete type.
[*] The type has to be builtin, rather than declared in
qapi/common.json, because we want to use it for alternates even
when common.json is not included. But since it is the first
builtin enum type, we have to add special cases to qapi-types
and qapi-visit to only emit definitions once, even when two
qapi files are being compiled into the same binary (the way we
already handled builtin list types like 'intList'). We may
need to revisit how multiple qapi files share common types,
but that's a project for another day.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1449033659-25497-4-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2015-12-02 08:20:47 +03:00
|
|
|
};
|
2009-08-28 22:27:04 +04:00
|
|
|
|
|
|
|
/* Get the 'base' part of an object */
|
2009-11-11 19:50:36 +03:00
|
|
|
#define QOBJECT(obj) (&(obj)->base)
|
2009-08-28 22:27:04 +04:00
|
|
|
|
|
|
|
/* High-level interface for qobject_incref() */
|
|
|
|
#define QINCREF(obj) \
|
|
|
|
qobject_incref(QOBJECT(obj))
|
|
|
|
|
|
|
|
/* High-level interface for qobject_decref() */
|
|
|
|
#define QDECREF(obj) \
|
2012-09-03 23:19:11 +04:00
|
|
|
qobject_decref(obj ? QOBJECT(obj) : NULL)
|
2009-08-28 22:27:04 +04:00
|
|
|
|
|
|
|
/* Initialize an object to default values */
|
2015-12-02 08:20:46 +03:00
|
|
|
static inline void qobject_init(QObject *obj, QType type)
|
2015-12-02 08:20:45 +03:00
|
|
|
{
|
qapi: Convert QType into QAPI built-in enum type
What's more meta than using qapi to define qapi? :)
Convert QType into a full-fledged[*] builtin qapi enum type, so
that a subsequent patch can then use it as the discriminator
type of qapi alternate types. Fortunately, the judicious use of
'prefix' in the qapi definition avoids churn to the spelling of
the enum constants.
To avoid circular definitions, we have to flip the order of
inclusion between "qobject.h" vs. "qapi-types.h". Back in commit
28770e0, we had the latter include the former, so that we could
use 'QObject *' for our implementation of 'any'. But that usage
also works with only a forward declaration, whereas the
definition of QObject requires QType to be a complete type.
[*] The type has to be builtin, rather than declared in
qapi/common.json, because we want to use it for alternates even
when common.json is not included. But since it is the first
builtin enum type, we have to add special cases to qapi-types
and qapi-visit to only emit definitions once, even when two
qapi files are being compiled into the same binary (the way we
already handled builtin list types like 'intList'). We may
need to revisit how multiple qapi files share common types,
but that's a project for another day.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1449033659-25497-4-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2015-12-02 08:20:47 +03:00
|
|
|
assert(QTYPE_NONE < type && type < QTYPE__MAX);
|
2015-12-02 08:20:45 +03:00
|
|
|
obj->refcnt = 1;
|
|
|
|
obj->type = type;
|
|
|
|
}
|
2009-08-28 22:27:04 +04:00
|
|
|
|
|
|
|
/**
|
|
|
|
* qobject_incref(): Increment QObject's reference count
|
|
|
|
*/
|
|
|
|
static inline void qobject_incref(QObject *obj)
|
|
|
|
{
|
2009-10-07 20:41:47 +04:00
|
|
|
if (obj)
|
|
|
|
obj->refcnt++;
|
2009-08-28 22:27:04 +04:00
|
|
|
}
|
|
|
|
|
2015-12-02 08:20:45 +03:00
|
|
|
/**
|
|
|
|
* qobject_destroy(): Free resources used by the object
|
|
|
|
*/
|
|
|
|
void qobject_destroy(QObject *obj);
|
|
|
|
|
2009-08-28 22:27:04 +04:00
|
|
|
/**
|
|
|
|
* qobject_decref(): Decrement QObject's reference count, deallocate
|
|
|
|
* when it reaches zero
|
|
|
|
*/
|
|
|
|
static inline void qobject_decref(QObject *obj)
|
|
|
|
{
|
2015-11-06 09:35:27 +03:00
|
|
|
assert(!obj || obj->refcnt);
|
2009-10-07 20:41:47 +04:00
|
|
|
if (obj && --obj->refcnt == 0) {
|
2015-12-02 08:20:45 +03:00
|
|
|
qobject_destroy(obj);
|
2009-08-28 22:27:04 +04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* qobject_type(): Return the QObject's type
|
|
|
|
*/
|
2015-12-02 08:20:46 +03:00
|
|
|
static inline QType qobject_type(const QObject *obj)
|
2009-08-28 22:27:04 +04:00
|
|
|
{
|
qapi: Convert QType into QAPI built-in enum type
What's more meta than using qapi to define qapi? :)
Convert QType into a full-fledged[*] builtin qapi enum type, so
that a subsequent patch can then use it as the discriminator
type of qapi alternate types. Fortunately, the judicious use of
'prefix' in the qapi definition avoids churn to the spelling of
the enum constants.
To avoid circular definitions, we have to flip the order of
inclusion between "qobject.h" vs. "qapi-types.h". Back in commit
28770e0, we had the latter include the former, so that we could
use 'QObject *' for our implementation of 'any'. But that usage
also works with only a forward declaration, whereas the
definition of QObject requires QType to be a complete type.
[*] The type has to be builtin, rather than declared in
qapi/common.json, because we want to use it for alternates even
when common.json is not included. But since it is the first
builtin enum type, we have to add special cases to qapi-types
and qapi-visit to only emit definitions once, even when two
qapi files are being compiled into the same binary (the way we
already handled builtin list types like 'intList'). We may
need to revisit how multiple qapi files share common types,
but that's a project for another day.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1449033659-25497-4-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
2015-12-02 08:20:47 +03:00
|
|
|
assert(QTYPE_NONE < obj->type && obj->type < QTYPE__MAX);
|
2015-12-02 08:20:45 +03:00
|
|
|
return obj->type;
|
2009-08-28 22:27:04 +04:00
|
|
|
}
|
|
|
|
|
2015-04-30 00:35:05 +03:00
|
|
|
extern QObject qnull_;
|
|
|
|
|
|
|
|
static inline QObject *qnull(void)
|
|
|
|
{
|
|
|
|
qobject_incref(&qnull_);
|
|
|
|
return &qnull_;
|
|
|
|
}
|
|
|
|
|
2009-08-28 22:27:04 +04:00
|
|
|
#endif /* QOBJECT_H */
|