From: "Cédric Le Goater" <clg@redhat.com>
To: marcandre.lureau@redhat.com, qemu-devel@nongnu.org
Cc: lersek@redhat.com, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v5 0/3] ramfb: migration support
Date: Tue, 10 Oct 2023 14:48:54 +0200 [thread overview]
Message-ID: <0cdcd25f-9ed5-cbfe-1633-213bd6a2c82f@redhat.com> (raw)
In-Reply-To: <20231009063247.119333-1-marcandre.lureau@redhat.com>
Hello,
On 10/9/23 08:32, marcandre.lureau@redhat.com wrote:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Hi,
>
> Implement RAMFB migration, and add properties to enable it only on >= 8.2
> machines, + a few related cleanups.
Should this series go in vfio-next ?
Thanks,
C.
>
> thanks
>
> v5:
> - add missing VMSTATE_END_OF_LIST
> - changed ramfb=off & x-mig=on user config error to a warning
> - add r-b tags
>
> v4: (Laszlo review and suggestions)
> - change migrate_needed() to assert(ramfb_exists)
> - rename vfio_display_needed() to vfio_display_migration_needed(),
> update the condition and associated comment
> - move the ramfb-migrate option check and add a check for ramfb=on
> - add a stub to fix compilation on some architectures
>
> v3:
> - add a "x-" prefix to properties, as they are not meant for users.
> - RAMFB now exports a ramfb_vmstate for actual devices to include
> - VFIOPCIDevice now has a VFIODisplay optional subsection whenever ramfb
> migration is required (untested)
>
> Fixes:
> https://bugzilla.redhat.com/show_bug.cgi?id=1859424
>
> Marc-André Lureau (3):
> ramfb: add migration support
> ramfb-standalone: add migration support
> hw/vfio: add ramfb migration support
>
> hw/vfio/pci.h | 3 +++
> include/hw/display/ramfb.h | 4 ++++
> hw/core/machine.c | 2 ++
> hw/display/ramfb-standalone.c | 27 +++++++++++++++++++++
> hw/display/ramfb.c | 19 +++++++++++++++
> hw/vfio/display.c | 21 +++++++++++++++++
> hw/vfio/pci.c | 44 +++++++++++++++++++++++++++++++++++
> stubs/ramfb.c | 2 ++
> 8 files changed, 122 insertions(+)
>
next prev parent reply other threads:[~2023-10-10 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 6:32 [PATCH v5 0/3] ramfb: migration support marcandre.lureau
2023-10-09 6:32 ` [PATCH v5 1/3] ramfb: add " marcandre.lureau
2023-10-09 6:32 ` [PATCH v5 2/3] ramfb-standalone: " marcandre.lureau
2023-10-09 6:32 ` [PATCH v5 3/3] hw/vfio: add ramfb " marcandre.lureau
2023-10-09 10:19 ` Laszlo Ersek
2023-10-10 7:03 ` Cédric Le Goater
2023-10-10 7:08 ` Marc-André Lureau
2023-10-10 12:48 ` Cédric Le Goater [this message]
2023-10-10 13:46 ` [PATCH v5 0/3] ramfb: " Marc-André Lureau
2023-10-11 17:09 ` Cédric Le Goater
2023-10-12 9:18 ` Gerd Hoffmann
2023-10-12 10:11 ` Cédric Le Goater
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0cdcd25f-9ed5-cbfe-1633-213bd6a2c82f@redhat.com \
--to=clg@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).