From: lementec fabien <fabien.lementec@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: 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: Mon, 19 Nov 2012 17:00:58 +0100 [thread overview]
Message-ID: <CAAPMK-QKkZDbEj5AW4bY5sP2STuyPzhu03sM+BYPaJJYE1-AXA@mail.gmail.com> (raw)
In-Reply-To: <20121119085528.GD17444@stefanha-thinkpad.redhat.com>
Hi,
Thanks, it is actually a good idea to start with. I will write a spec
based on an improved version of what I have already implemented.
I think I will have some time this week, I will keep you updated soon.
Best regards,
Fabien.
2012/11/19 Stefan Hajnoczi <stefanha@gmail.com>:
> On Fri, Nov 16, 2012 at 02:05:29PM +0100, lementec fabien wrote:
>> Actually, I wanted to be independant of the QEMU event loop. Plus,
>> some proprietary simulation environment provides a closed socket
>> based interface to 'stimulate' the emulated device, at the PCIE level
>> for instance. These environments are sometimes installed on cluster
>> not running QEMU. The socket based approach fits quite well.
>>
>> Not knowing about QEMU internals, I spent some hours trying to find
>> out the best way to plug into QEMU, and did not find ivhsmem appropriate.
>> Honestly, I wanted to have a working solution asap, and it did not take
>> long before I opted for the socket based approach. Now that it is working,
>> I can take time to reconsider stuffs according to others need, and ideally
>> an integration to QEMU.
>
> I suggest writing up a spec for the socket protocol. It can be put in
> docs/specs/ (like the ivshmem spec).
>
> This is both a good way to increase discussion and important for others
> who may wish to make use of this feature.
>
> Stefan
next prev parent reply other threads:[~2012-11-19 16:01 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 [this message]
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
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=CAAPMK-QKkZDbEj5AW4bY5sP2STuyPzhu03sM+BYPaJJYE1-AXA@mail.gmail.com \
--to=fabien.lementec@gmail.com \
--cc=cam@cs.ualberta.ca \
--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).