On 11/16/10 02:16, Michael Roth wrote: > Virtproxy relies on routines defined within qemu-vp which mirror various > i/o related operations in qemu to provide similar functionality for the > guest daemon. When building virtproxy as part of qemu rather than > qemu-vp we need these definitions to provide those functions in terms of > the original qemu functions. > > Signed-off-by: Michael Roth <mdr...@linux.vnet.ibm.com> > --- > virtproxy-builtin.c | 38 ++++++++++++++++++++++++++++++++++++++ > 1 files changed, 38 insertions(+), 0 deletions(-) > create mode 100644 virtproxy-builtin.c > > diff --git a/virtproxy-builtin.c b/virtproxy-builtin.c > new file mode 100644 > index 0000000..71fc5bc > --- /dev/null > +++ b/virtproxy-builtin.c > @@ -0,0 +1,38 @@ > +/* > + * virt-proxy - host/guest communication layer builtin definitions > + * > + * Copyright IBM Corp. 2010 > + * > + * Authors: > + * Adam Litke <agli...@linux.vnet.ibm.com> > + * Michael Roth <mdr...@linux.vnet.ibm.com> > + * > + * This work is licensed under the terms of the GNU GPL, version 2 or later. > + * See the COPYING file in the top-level directory. > + * > + */ > + > +/* the following are functions we define in terms of qemu when linked > + * against qemu/vl.c. these will be added on an as-needed basis > + */ > + > +#include "qemu-char.h" > +#include "qemu_socket.h" > +#include "virtproxy.h" > + > +int vp_set_fd_handler(int fd, > + IOHandler *fd_read, > + IOHandler *fd_write, > + void *opaque)
odd alignment again. Jes
