On 10/2/23 13:11, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> 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
On 10/2/23 14:01, Marc-André Lureau wrote:
> Hi
>
> On Mon, Oct 2, 2023 at 3:12 PM wrote:
>>
>> From: Marc-André Lureau
>>
>> 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
Hi
On Mon, Oct 2, 2023 at 3:12 PM wrote:
>
> From: Marc-André Lureau
>
> 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
>
From: Marc-André Lureau
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 fo
