From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Adam Litke <agl@us.ibm.com>
Cc: abeekhof@redhat.com, agl@linux.vnet.ibm.com,
qemu-devel@nongnu.org, aliguori@linux.vnet.ibm.com
Subject: [Qemu-devel] Re: [RFC][RESEND][PATCH v1 02/15] virtproxy: qemu-vp, standalone daemon skeleton
Date: Thu, 04 Nov 2010 08:57:14 -0500 [thread overview]
Message-ID: <4CD2BBBA.3070002@linux.vnet.ibm.com> (raw)
In-Reply-To: <1288824456.2846.15.camel@aglitke>
On 11/03/2010 05:47 PM, Adam Litke wrote:
> On Wed, 2010-11-03 at 10:27 -0500, Michael Roth wrote:
>> +/* mirror qemu I/O-related code for standalone daemon */
>> +typedef struct IOHandlerRecord {
>> + int fd;
>> + IOCanReadHandler *fd_read_poll;
>> + IOHandler *fd_read;
>> + IOHandler *fd_write;
>> + int deleted;
>> + void *opaque;
>> + /* temporary data */
>> + struct pollfd *ufd;
>> + QLIST_ENTRY(IOHandlerRecord) next;
>> +} IOHandlerRecord;
>
> As you say, this is exactly the same structure as defined in vl.c. If
> you copy and paste code for a new feature you should be looking for a
> way to share it instead. Why not create a separate patch that defines
> this structure in vl.h which can then be included by vl.c and virtproxy
> code.
>
>> +static QLIST_HEAD(, IOHandlerRecord) io_handlers =
>> + QLIST_HEAD_INITIALIZER(io_handlers);
>> +
>> +int vp_set_fd_handler2(int fd,
>> + IOCanReadHandler *fd_read_poll,
>> + IOHandler *fd_read,
>> + IOHandler *fd_write,
>> + void *opaque)
>> +{
>> + IOHandlerRecord *ioh;
>> +
>> + if (!fd_read&& !fd_write) {
>> + QLIST_FOREACH(ioh,&io_handlers, next) {
>> + if (ioh->fd == fd) {
>> + ioh->deleted = 1;
>> + break;
>> + }
>> + }
>> + } else {
>> + QLIST_FOREACH(ioh,&io_handlers, next) {
>> + if (ioh->fd == fd)
>> + goto found;
>> + }
>> + ioh = qemu_mallocz(sizeof(IOHandlerRecord));
>> + QLIST_INSERT_HEAD(&io_handlers, ioh, next);
>> + found:
>> + ioh->fd = fd;
>> + ioh->fd_read_poll = fd_read_poll;
>> + ioh->fd_read = fd_read;
>> + ioh->fd_write = fd_write;
>> + ioh->opaque = opaque;
>> + ioh->deleted = 0;
>> + }
>> + return 0;
>> +}
>
> Copied from vl.c -- export it instead.
>
>> +int vp_set_fd_handler(int fd,
>> + IOHandler *fd_read,
>> + IOHandler *fd_write,
>> + void *opaque)
>> +{
>> + return vp_set_fd_handler2(fd, NULL, fd_read, fd_write, opaque);
>> +}
>> +
>> +int vp_send_all(int fd, const void *buf, int len1)
>> +{
>> + int ret, len;
>> +
>> + len = len1;
>> + while (len> 0) {
>> + ret = write(fd, buf, len);
>> + if (ret< 0) {
>> + if (errno != EINTR&& errno != EAGAIN) {
>> + warn("write() failed");
>> + return -1;
>> + }
>> + } else if (ret == 0) {
>> + break;
>> + } else {
>> + buf += ret;
>> + len -= ret;
>> + }
>> + }
>> + return len1 - len;
>> +}
>
> Copied from qemu-char.c -- Share please.
>
>> +static void main_loop_wait(int nonblocking)
>> +{
>> + IOHandlerRecord *ioh;
>> + fd_set rfds, wfds, xfds;
>> + int ret, nfds;
>> + struct timeval tv;
>> + int timeout = 1000;
>> +
>> + if (nonblocking) {
>> + timeout = 0;
>> + }
>> +
>> + /* poll any events */
>> + nfds = -1;
>> + FD_ZERO(&rfds);
>> + FD_ZERO(&wfds);
>> + FD_ZERO(&xfds);
>> + QLIST_FOREACH(ioh,&io_handlers, next) {
>> + if (ioh->deleted)
>> + continue;
>> + if (ioh->fd_read&&
>> + (!ioh->fd_read_poll ||
>> + ioh->fd_read_poll(ioh->opaque) != 0)) {
>> + FD_SET(ioh->fd,&rfds);
>> + if (ioh->fd> nfds)
>> + nfds = ioh->fd;
>> + }
>> + if (ioh->fd_write) {
>> + FD_SET(ioh->fd,&wfds);
>> + if (ioh->fd> nfds)
>> + nfds = ioh->fd;
>> + }
>> + }
>> +
>> + tv.tv_sec = timeout / 1000;
>> + tv.tv_usec = (timeout % 1000) * 1000;
>> +
>> + ret = select(nfds + 1,&rfds,&wfds,&xfds,&tv);
>> +
>> + if (ret> 0) {
>> + IOHandlerRecord *pioh;
>> +
>> + QLIST_FOREACH_SAFE(ioh,&io_handlers, next, pioh) {
>> + if (ioh->deleted) {
>> + QLIST_REMOVE(ioh, next);
>> + qemu_free(ioh);
>> + continue;
>> + }
>> + if (ioh->fd_read&& FD_ISSET(ioh->fd,&rfds)) {
>> + ioh->fd_read(ioh->opaque);
>> + }
>> + if (ioh->fd_write&& FD_ISSET(ioh->fd,&wfds)) {
>> + ioh->fd_write(ioh->opaque);
>> + }
>> + }
>> + }
>> +
>
> This resembles vl.c's main_loop_wait() but I can see why you might want
> your own. There is opportunity for sharing the select logic and ioh
> callbacks but I think that could be addressed later.
>
Yup these are all basically copy/pastes from vl.c. It feels a bit dirty,
but I modeled things after the other qemu tools like qemu-nbd/qemu-io,
which don't link against vl.c (and adding a target for tools to do so
looks like it'd be a bit hairy since vl.c touches basically everything).
It might still make sense to share things like structs...but the ones
I'm stealing here are specific to reproducing the main_loop_wait logic.
So I guess the real question is whether main_loop_wait and friends make
sense to expose as a utility function of some sort, and virtproxy seems
to be the only use case so far.
next prev parent reply other threads:[~2010-11-04 14:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 15:27 [Qemu-devel] [RFC][RESEND][PATCH v1 00/15] virtproxy: host/guest communication layer Michael Roth
2010-11-03 15:27 ` [Qemu-devel] [RFC][RESEND][PATCH v1 01/15] virtproxy: base data structures and constants Michael Roth
2010-11-03 22:33 ` [Qemu-devel] " Adam Litke
2010-11-03 15:27 ` [Qemu-devel] [RFC][RESEND][PATCH v1 02/15] virtproxy: qemu-vp, standalone daemon skeleton Michael Roth
2010-11-03 22:47 ` [Qemu-devel] " Adam Litke
2010-11-04 13:57 ` Michael Roth [this message]
2010-11-05 13:32 ` Adam Litke
2010-11-09 10:45 ` Amit Shah
2010-11-10 2:51 ` Michael Roth
2010-11-03 15:27 ` [Qemu-devel] [RFC][RESEND][PATCH v1 03/15] virtproxy: add debug functions for virtproxy core Michael Roth
2010-11-03 22:51 ` [Qemu-devel] " Adam Litke
2010-11-03 15:27 ` [Qemu-devel] [RFC][RESEND][PATCH v1 04/15] virtproxy: list look-up functions conns/oforwards/iforwards Michael Roth
2010-11-03 22:56 ` [Qemu-devel] " Adam Litke
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 05/15] virtproxy: add accept handler for communication channel Michael Roth
2010-11-03 23:02 ` [Qemu-devel] " Adam Litke
2010-11-04 16:17 ` Michael Roth
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 06/15] virtproxy: add read " Michael Roth
2010-11-03 23:38 ` [Qemu-devel] " Adam Litke
2010-11-04 17:00 ` Michael Roth
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 07/15] virtproxy: add vp_new() VPDriver constructor Michael Roth
2010-11-03 23:45 ` [Qemu-devel] " Adam Litke
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 08/15] virtproxy: interfaces to set/remove/handle VPOForwards Michael Roth
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 09/15] virtproxy: add handler for data packets Michael Roth
2010-11-04 0:46 ` [Qemu-devel] " Adam Litke
2010-11-04 18:23 ` Michael Roth
2010-11-04 1:48 ` Adam Litke
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 10/15] virtproxy: add handler for control packet Michael Roth
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 11/15] virtproxy: add vp_handle_packet() Michael Roth
2010-11-04 1:13 ` [Qemu-devel] " Adam Litke
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 12/15] virtproxy: interfaces to set/remove VPIForwards Michael Roth
2010-11-04 1:12 ` [Qemu-devel] " Adam Litke
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 13/15] virtproxy: add read handler for proxied connections Michael Roth
2010-11-04 1:21 ` [Qemu-devel] " Adam Litke
2010-11-04 18:26 ` Michael Roth
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 14/15] virtproxy: Makefile/configure changes to build qemu-vp Michael Roth
2010-11-03 15:28 ` [Qemu-devel] [RFC][RESEND][PATCH v1 15/15] virtproxy: qemu-vp, main logic Michael Roth
2010-11-03 23:44 ` [Qemu-devel] Re: [RFC][RESEND][PATCH v1 00/15] virtproxy: host/guest communication layer Adam Litke
2010-11-04 18:46 ` Michael Roth
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=4CD2BBBA.3070002@linux.vnet.ibm.com \
--to=mdroth@linux.vnet.ibm.com \
--cc=abeekhof@redhat.com \
--cc=agl@linux.vnet.ibm.com \
--cc=agl@us.ibm.com \
--cc=aliguori@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.