2014-06-10 15:15:21 +04:00
|
|
|
/*
|
|
|
|
* QEMU Host Memory Backend for hugetlbfs
|
|
|
|
*
|
|
|
|
* Copyright (C) 2013-2014 Red Hat Inc
|
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Paolo Bonzini <pbonzini@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.
|
|
|
|
*/
|
2016-01-29 20:49:54 +03:00
|
|
|
#include "qemu/osdep.h"
|
include/qemu/osdep.h: Don't include qapi/error.h
Commit 57cb38b included qapi/error.h into qemu/osdep.h to get the
Error typedef. Since then, we've moved to include qemu/osdep.h
everywhere. Its file comment explains: "To avoid getting into
possible circular include dependencies, this file should not include
any other QEMU headers, with the exceptions of config-host.h,
compiler.h, os-posix.h and os-win32.h, all of which are doing a
similar job to this file and are under similar constraints."
qapi/error.h doesn't do a similar job, and it doesn't adhere to
similar constraints: it includes qapi-types.h. That's in excess of
100KiB of crap most .c files don't actually need.
Add the typedef to qemu/typedefs.h, and include that instead of
qapi/error.h. Include qapi/error.h in .c files that need it and don't
get it now. Include qapi-types.h in qom/object.h for uint16List.
Update scripts/clean-includes accordingly. Update it further to match
reality: replace config.h by config-target.h, add sysemu/os-posix.h,
sysemu/os-win32.h. Update the list of includes in the qemu/osdep.h
comment quoted above similarly.
This reduces the number of objects depending on qapi/error.h from "all
of them" to less than a third. Unfortunately, the number depending on
qapi-types.h shrinks only a little. More work is needed for that one.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
[Fix compilation without the spice devel packages. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2016-03-14 11:01:28 +03:00
|
|
|
#include "qapi/error.h"
|
2014-06-10 15:15:23 +04:00
|
|
|
#include "qemu-common.h"
|
2018-07-18 10:48:00 +03:00
|
|
|
#include "qemu/error-report.h"
|
2014-06-10 15:15:21 +04:00
|
|
|
#include "sysemu/hostmem.h"
|
2014-06-10 15:15:23 +04:00
|
|
|
#include "sysemu/sysemu.h"
|
2014-06-10 15:15:21 +04:00
|
|
|
#include "qom/object_interfaces.h"
|
|
|
|
|
|
|
|
/* hostmem-file.c */
|
|
|
|
/**
|
|
|
|
* @TYPE_MEMORY_BACKEND_FILE:
|
|
|
|
* name of backend that uses mmap on a file descriptor
|
|
|
|
*/
|
|
|
|
#define TYPE_MEMORY_BACKEND_FILE "memory-backend-file"
|
|
|
|
|
|
|
|
#define MEMORY_BACKEND_FILE(obj) \
|
|
|
|
OBJECT_CHECK(HostMemoryBackendFile, (obj), TYPE_MEMORY_BACKEND_FILE)
|
|
|
|
|
|
|
|
typedef struct HostMemoryBackendFile HostMemoryBackendFile;
|
|
|
|
|
|
|
|
struct HostMemoryBackendFile {
|
|
|
|
HostMemoryBackend parent_obj;
|
2014-06-10 15:15:24 +04:00
|
|
|
|
2014-06-10 15:15:21 +04:00
|
|
|
char *mem_path;
|
hostmem-file: add "align" option
When mmap(2) the backend files, QEMU uses the host page size
(getpagesize(2)) by default as the alignment of mapping address.
However, some backends may require alignments different than the page
size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
kernel 4.13 to an address, which is 4K-aligned but not 2M-aligned,
fails with a kernel message like
[617494.969768] dax dax0.0: qemu-system-x86: dax_mmap: fail, unaligned vma (0x7fa37c579000 - 0x7fa43c579000, 0x1fffff)
Because there is no common approach to get such alignment requirement,
we add the 'align' option to 'memory-backend-file', so that users or
management utils, which have enough knowledge about the backend, can
specify a proper alignment via this option.
Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
Message-Id: <20171211072806.2812-2-haozhong.zhang@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[ehabkost: fixed typo, fixed error_setg() format string]
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-12-11 10:28:04 +03:00
|
|
|
uint64_t align;
|
2018-07-18 10:48:00 +03:00
|
|
|
bool discard_data;
|
|
|
|
bool is_pmem;
|
2014-06-10 15:15:21 +04:00
|
|
|
};
|
|
|
|
|
|
|
|
static void
|
|
|
|
file_backend_memory_alloc(HostMemoryBackend *backend, Error **errp)
|
|
|
|
{
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(backend);
|
2018-09-10 16:49:46 +03:00
|
|
|
#ifdef CONFIG_POSIX
|
hostmem: use object id for memory region name with >= 4.0
hostmem-file and hostmem-memfd use the whole object path for the
memory region name, and hostname-ram uses only the path component (the
object id, or canonical path basename):
qemu -m 1024 -object memory-backend-file,id=mem,size=1G,mem-path=/tmp/foo -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-memfd,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-ram,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
For consistency, change to use object id for -file and -memfd as well
with >= 4.0.
Having a consistent naming allows to migrate to different hostmem
backends.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
2018-09-12 15:18:00 +03:00
|
|
|
gchar *name;
|
2018-09-10 16:49:46 +03:00
|
|
|
#endif
|
2014-06-10 15:15:21 +04:00
|
|
|
|
|
|
|
if (!backend->size) {
|
|
|
|
error_setg(errp, "can't create backend with size 0");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
if (!fb->mem_path) {
|
2015-04-24 20:41:26 +03:00
|
|
|
error_setg(errp, "mem-path property not set");
|
2014-06-10 15:15:21 +04:00
|
|
|
return;
|
|
|
|
}
|
2018-09-24 15:32:05 +03:00
|
|
|
#ifndef CONFIG_POSIX
|
2014-06-10 15:15:21 +04:00
|
|
|
error_setg(errp, "-mem-path not supported on this host");
|
|
|
|
#else
|
2018-09-10 16:49:46 +03:00
|
|
|
backend->force_prealloc = mem_prealloc;
|
hostmem: use object id for memory region name with >= 4.0
hostmem-file and hostmem-memfd use the whole object path for the
memory region name, and hostname-ram uses only the path component (the
object id, or canonical path basename):
qemu -m 1024 -object memory-backend-file,id=mem,size=1G,mem-path=/tmp/foo -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-memfd,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-ram,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
For consistency, change to use object id for -file and -memfd as well
with >= 4.0.
Having a consistent naming allows to migrate to different hostmem
backends.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
2018-09-12 15:18:00 +03:00
|
|
|
name = host_memory_backend_get_name(backend);
|
2018-09-10 16:49:46 +03:00
|
|
|
memory_region_init_ram_from_file(&backend->mr, OBJECT(backend),
|
hostmem: use object id for memory region name with >= 4.0
hostmem-file and hostmem-memfd use the whole object path for the
memory region name, and hostname-ram uses only the path component (the
object id, or canonical path basename):
qemu -m 1024 -object memory-backend-file,id=mem,size=1G,mem-path=/tmp/foo -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-memfd,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-ram,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
For consistency, change to use object id for -file and -memfd as well
with >= 4.0.
Having a consistent naming allows to migrate to different hostmem
backends.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
2018-09-12 15:18:00 +03:00
|
|
|
name,
|
2018-09-10 16:49:46 +03:00
|
|
|
backend->size, fb->align,
|
|
|
|
(backend->share ? RAM_SHARED : 0) |
|
|
|
|
(fb->is_pmem ? RAM_PMEM : 0),
|
|
|
|
fb->mem_path, errp);
|
hostmem: use object id for memory region name with >= 4.0
hostmem-file and hostmem-memfd use the whole object path for the
memory region name, and hostname-ram uses only the path component (the
object id, or canonical path basename):
qemu -m 1024 -object memory-backend-file,id=mem,size=1G,mem-path=/tmp/foo -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-memfd,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
/objects/mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
qemu -m 1024 -object memory-backend-ram,id=mem,size=1G -numa node,memdev=mem -monitor stdio
(qemu) info ramblock
Block Name PSize Offset Used Total
mem 4 KiB 0x0000000000000000 0x0000000040000000 0x0000000040000000
For consistency, change to use object id for -file and -memfd as well
with >= 4.0.
Having a consistent naming allows to migrate to different hostmem
backends.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Acked-by: Eduardo Habkost <ehabkost@redhat.com>
2018-09-12 15:18:00 +03:00
|
|
|
g_free(name);
|
2014-06-10 15:15:21 +04:00
|
|
|
#endif
|
|
|
|
}
|
|
|
|
|
|
|
|
static char *get_mem_path(Object *o, Error **errp)
|
|
|
|
{
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(o);
|
|
|
|
|
|
|
|
return g_strdup(fb->mem_path);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void set_mem_path(Object *o, const char *str, Error **errp)
|
|
|
|
{
|
|
|
|
HostMemoryBackend *backend = MEMORY_BACKEND(o);
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(o);
|
|
|
|
|
2017-03-10 16:09:30 +03:00
|
|
|
if (host_memory_backend_mr_inited(backend)) {
|
2019-01-02 08:26:24 +03:00
|
|
|
error_setg(errp, "cannot change property 'mem-path' of %s",
|
|
|
|
object_get_typename(o));
|
2014-06-10 15:15:21 +04:00
|
|
|
return;
|
|
|
|
}
|
2015-08-26 14:17:18 +03:00
|
|
|
g_free(fb->mem_path);
|
2014-06-10 15:15:21 +04:00
|
|
|
fb->mem_path = g_strdup(str);
|
|
|
|
}
|
|
|
|
|
2017-08-24 22:23:15 +03:00
|
|
|
static bool file_memory_backend_get_discard_data(Object *o, Error **errp)
|
|
|
|
{
|
|
|
|
return MEMORY_BACKEND_FILE(o)->discard_data;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void file_memory_backend_set_discard_data(Object *o, bool value,
|
|
|
|
Error **errp)
|
|
|
|
{
|
|
|
|
MEMORY_BACKEND_FILE(o)->discard_data = value;
|
|
|
|
}
|
|
|
|
|
hostmem-file: add "align" option
When mmap(2) the backend files, QEMU uses the host page size
(getpagesize(2)) by default as the alignment of mapping address.
However, some backends may require alignments different than the page
size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
kernel 4.13 to an address, which is 4K-aligned but not 2M-aligned,
fails with a kernel message like
[617494.969768] dax dax0.0: qemu-system-x86: dax_mmap: fail, unaligned vma (0x7fa37c579000 - 0x7fa43c579000, 0x1fffff)
Because there is no common approach to get such alignment requirement,
we add the 'align' option to 'memory-backend-file', so that users or
management utils, which have enough knowledge about the backend, can
specify a proper alignment via this option.
Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
Message-Id: <20171211072806.2812-2-haozhong.zhang@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[ehabkost: fixed typo, fixed error_setg() format string]
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-12-11 10:28:04 +03:00
|
|
|
static void file_memory_backend_get_align(Object *o, Visitor *v,
|
|
|
|
const char *name, void *opaque,
|
|
|
|
Error **errp)
|
|
|
|
{
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(o);
|
|
|
|
uint64_t val = fb->align;
|
|
|
|
|
|
|
|
visit_type_size(v, name, &val, errp);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void file_memory_backend_set_align(Object *o, Visitor *v,
|
|
|
|
const char *name, void *opaque,
|
|
|
|
Error **errp)
|
|
|
|
{
|
|
|
|
HostMemoryBackend *backend = MEMORY_BACKEND(o);
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(o);
|
|
|
|
Error *local_err = NULL;
|
|
|
|
uint64_t val;
|
|
|
|
|
|
|
|
if (host_memory_backend_mr_inited(backend)) {
|
2019-01-02 08:26:24 +03:00
|
|
|
error_setg(&local_err, "cannot change property '%s' of %s",
|
|
|
|
name, object_get_typename(o));
|
hostmem-file: add "align" option
When mmap(2) the backend files, QEMU uses the host page size
(getpagesize(2)) by default as the alignment of mapping address.
However, some backends may require alignments different than the page
size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
kernel 4.13 to an address, which is 4K-aligned but not 2M-aligned,
fails with a kernel message like
[617494.969768] dax dax0.0: qemu-system-x86: dax_mmap: fail, unaligned vma (0x7fa37c579000 - 0x7fa43c579000, 0x1fffff)
Because there is no common approach to get such alignment requirement,
we add the 'align' option to 'memory-backend-file', so that users or
management utils, which have enough knowledge about the backend, can
specify a proper alignment via this option.
Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
Message-Id: <20171211072806.2812-2-haozhong.zhang@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[ehabkost: fixed typo, fixed error_setg() format string]
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-12-11 10:28:04 +03:00
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
|
|
|
|
visit_type_size(v, name, &val, &local_err);
|
|
|
|
if (local_err) {
|
|
|
|
goto out;
|
|
|
|
}
|
|
|
|
fb->align = val;
|
|
|
|
|
|
|
|
out:
|
|
|
|
error_propagate(errp, local_err);
|
|
|
|
}
|
|
|
|
|
2018-07-18 10:48:00 +03:00
|
|
|
static bool file_memory_backend_get_pmem(Object *o, Error **errp)
|
|
|
|
{
|
|
|
|
return MEMORY_BACKEND_FILE(o)->is_pmem;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void file_memory_backend_set_pmem(Object *o, bool value, Error **errp)
|
|
|
|
{
|
|
|
|
HostMemoryBackend *backend = MEMORY_BACKEND(o);
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(o);
|
|
|
|
|
|
|
|
if (host_memory_backend_mr_inited(backend)) {
|
2018-08-28 19:14:22 +03:00
|
|
|
|
2018-10-24 17:14:56 +03:00
|
|
|
error_setg(errp, "cannot change property 'pmem' of %s.",
|
|
|
|
object_get_typename(o));
|
2018-07-18 10:48:00 +03:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
#ifndef CONFIG_LIBPMEM
|
|
|
|
if (value) {
|
|
|
|
Error *local_err = NULL;
|
2018-08-28 19:14:22 +03:00
|
|
|
|
2018-07-18 10:48:00 +03:00
|
|
|
error_setg(&local_err,
|
|
|
|
"Lack of libpmem support while setting the 'pmem=on'"
|
2018-10-24 17:14:56 +03:00
|
|
|
" of %s. We can't ensure data persistence.",
|
|
|
|
object_get_typename(o));
|
2018-07-18 10:48:00 +03:00
|
|
|
error_propagate(errp, local_err);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
|
|
|
|
fb->is_pmem = value;
|
|
|
|
}
|
|
|
|
|
2017-08-24 22:23:15 +03:00
|
|
|
static void file_backend_unparent(Object *obj)
|
|
|
|
{
|
|
|
|
HostMemoryBackend *backend = MEMORY_BACKEND(obj);
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(obj);
|
|
|
|
|
|
|
|
if (host_memory_backend_mr_inited(backend) && fb->discard_data) {
|
|
|
|
void *ptr = memory_region_get_ram_ptr(&backend->mr);
|
|
|
|
uint64_t sz = memory_region_size(&backend->mr);
|
|
|
|
|
|
|
|
qemu_madvise(ptr, sz, QEMU_MADV_REMOVE);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2014-06-10 15:15:21 +04:00
|
|
|
static void
|
2016-10-14 00:18:41 +03:00
|
|
|
file_backend_class_init(ObjectClass *oc, void *data)
|
2014-06-10 15:15:21 +04:00
|
|
|
{
|
2016-10-14 00:18:41 +03:00
|
|
|
HostMemoryBackendClass *bc = MEMORY_BACKEND_CLASS(oc);
|
|
|
|
|
|
|
|
bc->alloc = file_backend_memory_alloc;
|
2017-08-24 22:23:15 +03:00
|
|
|
oc->unparent = file_backend_unparent;
|
2016-10-14 00:18:41 +03:00
|
|
|
|
2017-08-24 22:23:15 +03:00
|
|
|
object_class_property_add_bool(oc, "discard-data",
|
|
|
|
file_memory_backend_get_discard_data, file_memory_backend_set_discard_data,
|
|
|
|
&error_abort);
|
2016-10-14 00:18:41 +03:00
|
|
|
object_class_property_add_str(oc, "mem-path",
|
|
|
|
get_mem_path, set_mem_path,
|
|
|
|
&error_abort);
|
hostmem-file: add "align" option
When mmap(2) the backend files, QEMU uses the host page size
(getpagesize(2)) by default as the alignment of mapping address.
However, some backends may require alignments different than the page
size. For example, mmap a device DAX (e.g., /dev/dax0.0) on Linux
kernel 4.13 to an address, which is 4K-aligned but not 2M-aligned,
fails with a kernel message like
[617494.969768] dax dax0.0: qemu-system-x86: dax_mmap: fail, unaligned vma (0x7fa37c579000 - 0x7fa43c579000, 0x1fffff)
Because there is no common approach to get such alignment requirement,
we add the 'align' option to 'memory-backend-file', so that users or
management utils, which have enough knowledge about the backend, can
specify a proper alignment via this option.
Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
Message-Id: <20171211072806.2812-2-haozhong.zhang@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[ehabkost: fixed typo, fixed error_setg() format string]
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
2017-12-11 10:28:04 +03:00
|
|
|
object_class_property_add(oc, "align", "int",
|
|
|
|
file_memory_backend_get_align,
|
|
|
|
file_memory_backend_set_align,
|
|
|
|
NULL, NULL, &error_abort);
|
2018-07-18 10:48:00 +03:00
|
|
|
object_class_property_add_bool(oc, "pmem",
|
|
|
|
file_memory_backend_get_pmem, file_memory_backend_set_pmem,
|
|
|
|
&error_abort);
|
2014-06-10 15:15:21 +04:00
|
|
|
}
|
|
|
|
|
2016-04-13 19:57:40 +03:00
|
|
|
static void file_backend_instance_finalize(Object *o)
|
|
|
|
{
|
|
|
|
HostMemoryBackendFile *fb = MEMORY_BACKEND_FILE(o);
|
|
|
|
|
|
|
|
g_free(fb->mem_path);
|
|
|
|
}
|
|
|
|
|
2014-06-10 15:15:21 +04:00
|
|
|
static const TypeInfo file_backend_info = {
|
|
|
|
.name = TYPE_MEMORY_BACKEND_FILE,
|
|
|
|
.parent = TYPE_MEMORY_BACKEND,
|
|
|
|
.class_init = file_backend_class_init,
|
2016-04-13 19:57:40 +03:00
|
|
|
.instance_finalize = file_backend_instance_finalize,
|
2014-06-10 15:15:21 +04:00
|
|
|
.instance_size = sizeof(HostMemoryBackendFile),
|
|
|
|
};
|
|
|
|
|
|
|
|
static void register_types(void)
|
|
|
|
{
|
|
|
|
type_register_static(&file_backend_info);
|
|
|
|
}
|
|
|
|
|
|
|
|
type_init(register_types);
|