qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	"Peter Xu" <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
	kraxel@redhat.com, Juan Quintela <quintela@redhat.com>,
	Leonardo Bras Soares Passos <lsoaresp@redhat.com>
Subject: Re: [PATCH v2 0/5] virtio-gpu: add blob migration support
Date: Tue, 7 Nov 2023 13:21:44 +0100	[thread overview]
Message-ID: <9efd7465-7277-9012-4c7b-8f6cc02476c2@redhat.com> (raw)
In-Reply-To: <CAJ+F1CK3Jw0GKo_So3JyOFc=RuONHx8JUF-KLHrSHYPY2OE6dg@mail.gmail.com>

On 11/6/23 11:44, Marc-André Lureau wrote:
> Hi
> 
> On Tue, Sep 19, 2023 at 7:09 PM Peter Xu <peterx@redhat.com> wrote:
>>
>> On Tue, Sep 19, 2023 at 04:51:21PM +0400, Marc-André Lureau wrote:
>>> Hi
>>>
>>> On Thu, Sep 7, 2023 at 5:15 PM <marcandre.lureau@redhat.com> wrote:
>>>>
>>>> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>>>>
>>>> Hi,
>>>>
>>>> This is a follow-up of the previous patch "[PATCH] virtio-gpu: block migration
>>>> of VMs with blob=true". Now that migration support is implemented, we can decide
>>>> to drop the migration blocker patch, or apply and revert it, so that
>>>> backporting of a quick fix is made easier.
>>>>
>>>> Fixes:
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=2236353
>>>>
>>>> Marc-André Lureau (5):
>>>>   virtio-gpu: block migration of VMs with blob=true
>>>>   virtio-gpu: factor out restore mapping
>>>>   virtio-gpu: move scanout restoration to post_load
>>>>   virtio-gpu: add virtio-gpu/blob vmstate subsection
>>>>   Revert "virtio-gpu: block migration of VMs with blob=true"
>>>>
>>>>  hw/display/virtio-gpu.c | 174 +++++++++++++++++++++++++++++++++-------
>>>>  1 file changed, 146 insertions(+), 28 deletions(-)
>>
>> For migration:
>>
>> Acked-by: Peter Xu <peterx@redhat.com>
>>
> 
> Anyone else to check this series? Laszlo perhaps?

Sorry, I don't have the patches, plus I'm already loaded with other
reviews elsehwere :/

> Or should I just send it as part of the next gpu-stuff PR?

You appear to have an ACK from Peter; I'd say run with it. Gerd is on CC
so I'm comfortable saying this.

Laszlo



      reply	other threads:[~2023-11-07 12:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 13:09 [PATCH v2 0/5] virtio-gpu: add blob migration support marcandre.lureau
2023-09-07 13:09 ` [PATCH v2 1/5] virtio-gpu: block migration of VMs with blob=true marcandre.lureau
2023-09-07 13:09 ` [PATCH v2 2/5] virtio-gpu: factor out restore mapping marcandre.lureau
2023-09-07 13:09 ` [PATCH v2 3/5] virtio-gpu: move scanout restoration to post_load marcandre.lureau
2023-09-07 13:09 ` [PATCH v2 4/5] virtio-gpu: add virtio-gpu/blob vmstate subsection marcandre.lureau
2023-09-07 13:09 ` [PATCH v2 5/5] Revert "virtio-gpu: block migration of VMs with blob=true" marcandre.lureau
2023-09-19 12:51 ` [PATCH v2 0/5] virtio-gpu: add blob migration support Marc-André Lureau
2023-09-19 15:09   ` Peter Xu
2023-11-06 10:44     ` Marc-André Lureau
2023-11-07 12:21       ` Laszlo Ersek [this message]

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=9efd7465-7277-9012-4c7b-8f6cc02476c2@redhat.com \
    --to=lersek@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lsoaresp@redhat.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=mst@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).