Hi, I modified the protocol so that new message types can be added easily. It is necessary for control related messages, such as the hello one (I called it init). A type field has been added to the header.
I did not include a is_reply (or is_request) field, and prefered having 2 distinct message types. This is because one may imagine a message type that has no reply (ie. ping ...) Out of order reception is allowed by the use of a tag field in request and replies. I did not included the tag in the header, since not all the messages may need a tag. I plan to implement this tag as a simple incrementing counter, so made it large enough. I did not implement these modifications yet, since I prefer having feedbacks first. Neither did I have a look to the the command line option parsing. Regards, Fabien. 2012/11/22 Paolo Bonzini <pbonz...@redhat.com>: > Il 22/11/2012 09:19, Stefan Hajnoczi ha scritto: >>> > usage >>> > ----- >>> > PCIEFW devices are instanciated using the following QEMU options: >>> > -device \ >>> > pciefw,\ >>> > laddr=<local_addr>,\ >>> > lport=<local_port>,\ >>> > raddr=<remote_addr>,\ >>> > rport=<remote_port> >> Take a look at qemu_socket.h:socket_parse(). It should allow you to >> support TCP, UNIX domain sockets, and arbitrary file descriptors. >> > > Even better it could just be a chardev. socket_parse() is only used by > the (human) monitor interface. > > Paolo
pciefw.protocol
Description: Binary data
