qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: lementec fabien <fabien.lementec@gmail.com>,
	Cam Macdonell <cam@cs.ualberta.ca>,
	Nick Gasson <nick@nickg.me.uk>,
	qemu-devel <qemu-devel@nongnu.org>,
	fred.konrad@greensocs.com
Subject: Re: [Qemu-devel] TCP based PCIE request forwarding
Date: Thu, 22 Nov 2012 11:21:58 +0100	[thread overview]
Message-ID: <50ADFCC6.6070902@redhat.com> (raw)
In-Reply-To: <20121122081942.GC7598@stefanha-thinkpad.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

  parent reply	other threads:[~2012-11-22 10:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16  8:39 [Qemu-devel] TCP based PCIE request forwarding lementec fabien
2012-11-16 12:10 ` Stefan Hajnoczi
2012-11-16 13:05   ` lementec fabien
2012-11-19  8:55     ` Stefan Hajnoczi
2012-11-19 16:00       ` lementec fabien
2012-11-21 14:27       ` lementec fabien
2012-11-22  8:19         ` Stefan Hajnoczi
2012-11-22 10:08           ` lementec fabien
2012-11-22 10:21           ` Paolo Bonzini [this message]
2012-11-22 11:26             ` lementec fabien
2012-11-22 12:38             ` Stefan Hajnoczi
2012-11-20 16:41 ` Jason Baron
2012-11-21 13:13   ` lementec fabien

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=50ADFCC6.6070902@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=cam@cs.ualberta.ca \
    --cc=fabien.lementec@gmail.com \
    --cc=fred.konrad@greensocs.com \
    --cc=nick@nickg.me.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).