303c33e606
Implementing RAMFB migration is quite straightforward. One caveat is to treat the whole RAMFBCfg as a blob, since that's what is exposed to the guest directly. This avoid having to fiddle with endianness issues if we were to migrate fields individually as integers. The devices using RAMFB will have to include ramfb_vmstate in their migration description. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Reviewed-by: Laszlo Ersek <lersek@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com> Signed-off-by: Cédric Le Goater <clg@redhat.com>
17 lines
346 B
C
17 lines
346 B
C
#ifndef RAMFB_H
|
|
#define RAMFB_H
|
|
|
|
#include "migration/vmstate.h"
|
|
|
|
/* ramfb.c */
|
|
typedef struct RAMFBState RAMFBState;
|
|
void ramfb_display_update(QemuConsole *con, RAMFBState *s);
|
|
RAMFBState *ramfb_setup(Error **errp);
|
|
|
|
extern const VMStateDescription ramfb_vmstate;
|
|
|
|
/* ramfb-standalone.c */
|
|
#define TYPE_RAMFB_DEVICE "ramfb"
|
|
|
|
#endif /* RAMFB_H */
|