qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Tom Lonergan <tom.lonergan@nutanix.com>
To: mst@redhat.com
Cc: raphael.norwitz@nutanix.com, qemu-devel@nongnu.org,
	yuanmh12@chinatelecom.cn, Tom Lonergan <tom.lonergan@nutanix.com>
Subject: [PATCH 2/2] vhost-user: Make RESET_DEVICE a per device message
Date: Wed, 28 Jun 2023 16:39:27 +0000	[thread overview]
Message-ID: <20230628163927.108171-3-tom.lonergan@nutanix.com> (raw)
In-Reply-To: <20230628163927.108171-1-tom.lonergan@nutanix.com>

A device reset is issued per device, not per VQ. The legacy device reset
message, VHOST_USER_RESET_OWNER, is already a per device message. Therefore,
this change adds the proper message, VHOST_USER_RESET_DEVICE, to per device
messages.

Signed-off-by: Tom Lonergan <tom.lonergan@nutanix.com>
---
 hw/virtio/vhost-user.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
index 65d6299343..8dcf049d42 100644
--- a/hw/virtio/vhost-user.c
+++ b/hw/virtio/vhost-user.c
@@ -375,6 +375,7 @@ static bool vhost_user_per_device_request(VhostUserRequest request)
     case VHOST_USER_SET_MEM_TABLE:
     case VHOST_USER_GET_QUEUE_NUM:
     case VHOST_USER_NET_SET_MTU:
+    case VHOST_USER_RESET_DEVICE:
     case VHOST_USER_ADD_MEM_REG:
     case VHOST_USER_REM_MEM_REG:
         return true;
-- 
2.22.3



  parent reply	other threads:[~2023-06-28 16:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 16:39 [PATCH 0/2] vhost user one time message fixes Tom Lonergan
2023-06-28 16:39 ` [PATCH 1/2] vhost-user: Change one_time to per_device request Tom Lonergan
2023-06-30 12:15   ` Raphael Norwitz
2023-06-28 16:39 ` Tom Lonergan [this message]
2023-06-30 12:16   ` [PATCH 2/2] vhost-user: Make RESET_DEVICE a per device message Raphael Norwitz

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=20230628163927.108171-3-tom.lonergan@nutanix.com \
    --to=tom.lonergan@nutanix.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raphael.norwitz@nutanix.com \
    --cc=yuanmh12@chinatelecom.cn \
    /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).