qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Wafer Xie <wafer@jaguarmicro.com>
Cc: eperezma@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
	 angus.chen@jaguarmicro.com
Subject: Re: [PATCH v3] vdpa: fix vhost-vdpa suspended state not be shared
Date: Fri, 7 Nov 2025 15:12:12 +0800	[thread overview]
Message-ID: <CACGkMEsBUUWGuAvECdhMccfxPxXDOherXSBfPPt4bn3=dV3UQg@mail.gmail.com> (raw)
In-Reply-To: <20251107070723.7491-1-wafer@jaguarmicro.com>

On Fri, Nov 7, 2025 at 3:08 PM Wafer Xie <wafer@jaguarmicro.com> wrote:
>
> When stopping a vhost-vdpa device, only the first queue pair is marked as suspended,
> while the remaining queues are not updated to the suspended state.
> As a result, when stopping a multi-queue vhost-vdpa device,
> the following error message will be printed.
>
> qemu-system-x86_64:vhost VQ 2 ring restore failed: -1: Operation not permitted (1)
>
> qemu-system-x86_64:vhost VQ 3 ring restore failed: -1: Operation not permitted (1)
>
> So move v->suspended to v->shared, and then all the vhost_vdpa devices cannot
> have different suspended states.
>
> Fixes: 0bb302a9960a ("vdpa: add vhost_vdpa_suspend")
>
> Suggested-by: Eugenio Pérez <eperezma@redhat.com>
> Acked-by: Eugenio Pérez <eperezma@redhat.com>
> Signed-off-by: Wafer Xie <wafer@jaguarmicro.com>
>

Acked-by: Jason Wang <jasowang@redhat.com>

Thanks



      reply	other threads:[~2025-11-07  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07  7:07 [PATCH v3] vdpa: fix vhost-vdpa suspended state not be shared Wafer Xie
2025-11-07  7:12 ` Jason Wang [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='CACGkMEsBUUWGuAvECdhMccfxPxXDOherXSBfPPt4bn3=dV3UQg@mail.gmail.com' \
    --to=jasowang@redhat.com \
    --cc=angus.chen@jaguarmicro.com \
    --cc=eperezma@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wafer@jaguarmicro.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).