From: "Michael S. Tsirkin" <mst@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: zhiyong.yang@intel.com, qemu-devel@nongnu.org,
jfreiman@redhat.com, marcandre.lureau@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] vhost-user: pass message as a pointer to process_message_reply()
Date: Thu, 25 May 2017 00:58:22 +0300 [thread overview]
Message-ID: <20170525005724-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170524090520.321-1-maxime.coquelin@redhat.com>
On Wed, May 24, 2017 at 11:05:20AM +0200, Maxime Coquelin wrote:
> process_message_reply() was recently updated to get full message
> content instead of only its request field.
>
> There is no need to copy all the struct content into the stack,
> so just pass its pointer as const.
>
> Cc: Zhiyong Yang <zhiyong.yang@intel.com>
> Fixes: 60cd11024f41 ("hw/virtio: fix vhost user fails to startup when MQ")
> Reviewed-by: Jens Freimann <jfreiman@redhat.com>
> Reviewed-by: Zhiyong Yang <zhiyong.yang@intel.com>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Why "Fixes"? It's not a bugfix, is it? Passing a pointer is
slightly cleaner but it's not a big deal IMHO. I'll apply
but would like to get clarification on this tag.
> ---
> V2:
> - Make msg pointer const (Marc-Andre)
> - Apply R-b's
>
> hw/virtio/vhost-user.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
> index b87a176..dde094a 100644
> --- a/hw/virtio/vhost-user.c
> +++ b/hw/virtio/vhost-user.c
> @@ -162,11 +162,11 @@ fail:
> }
>
> static int process_message_reply(struct vhost_dev *dev,
> - VhostUserMsg msg)
> + const VhostUserMsg *msg)
> {
> VhostUserMsg msg_reply;
>
> - if ((msg.flags & VHOST_USER_NEED_REPLY_MASK) == 0) {
> + if ((msg->flags & VHOST_USER_NEED_REPLY_MASK) == 0) {
> return 0;
> }
>
> @@ -174,10 +174,10 @@ static int process_message_reply(struct vhost_dev *dev,
> return -1;
> }
>
> - if (msg_reply.request != msg.request) {
> + if (msg_reply.request != msg->request) {
> error_report("Received unexpected msg type."
> "Expected %d received %d",
> - msg.request, msg_reply.request);
> + msg->request, msg_reply.request);
> return -1;
> }
>
> @@ -324,7 +324,7 @@ static int vhost_user_set_mem_table(struct vhost_dev *dev,
> }
>
> if (reply_supported) {
> - return process_message_reply(dev, msg);
> + return process_message_reply(dev, &msg);
> }
>
> return 0;
> @@ -716,7 +716,7 @@ static int vhost_user_net_set_mtu(struct vhost_dev *dev, uint16_t mtu)
>
> /* If reply_ack supported, slave has to ack specified MTU is valid */
> if (reply_supported) {
> - return process_message_reply(dev, msg);
> + return process_message_reply(dev, &msg);
> }
>
> return 0;
> --
> 2.9.4
next prev parent reply other threads:[~2017-05-24 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 9:05 [Qemu-devel] [PATCH v2] vhost-user: pass message as a pointer to process_message_reply() Maxime Coquelin
2017-05-24 9:09 ` Marc-André Lureau
2017-05-24 21:58 ` Michael S. Tsirkin [this message]
2017-05-25 15:57 ` Maxime Coquelin
2017-05-25 17:21 ` Michael S. Tsirkin
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=20170525005724-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jfreiman@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhiyong.yang@intel.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).