From: Raphael Norwitz <raphael.norwitz@nutanix.com>
To: qemu-devel@nongnu.org
Cc: Raphael Norwitz <raphael.norwitz@nutanix.com>
Subject: [PATCH] [RFC] vhost-user: clean up set_mem_table functions
Date: Wed, 30 Oct 2019 19:12:04 -0400 [thread overview]
Message-ID: <1572477125-25344-1-git-send-email-raphael.norwitz@nutanix.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 533 bytes --]
The functions sending vhost-user set memory table messages are getting
convoluted. The amount of nested logic is getting in the way of my
development and it looks like some identical logic should be refractored
out anyways. Here’s an RFC which cleans these functions up a bit.
Raphael
Raphael Norwitz (1):
vhost-user: Refractor vhost_user_set_mem_table Functions
hw/virtio/vhost-user.c | 140 +++++++++++++++++++++++--------------------------
1 file changed, 65 insertions(+), 75 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-11-06 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 23:12 Raphael Norwitz [this message]
2019-10-30 23:12 ` [PATCH] vhost-user: Refractor vhost_user_set_mem_table Functions Raphael Norwitz
2019-11-06 8:27 ` no-reply
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=1572477125-25344-1-git-send-email-raphael.norwitz@nutanix.com \
--to=raphael.norwitz@nutanix.com \
--cc=qemu-devel@nongnu.org \
/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).