xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Alon Levy <alevy@redhat.com>
To: Xen Devel <xen-devel@lists.xensource.com>
Subject: [alevy@redhat.com: [Qemu-devel] 3D BoF in kvm-forum]
Date: Thu, 19 May 2011 09:43:49 +0300	[thread overview]
Message-ID: <20110519064349.GZ7083@playa.tlv.redhat.com> (raw)

Hi,

 Is there anyone interested that is coming to the kvm forum? see suggestion below, haven't written proposal yet (not a lot of time left).

Alon

----- Forwarded message from Alon Levy <alevy@redhat.com> -----

Date: Wed, 18 May 2011 18:13:38 +0300
From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] 3D BoF in kvm-forum
User-Agent: Mutt/1.5.21 (2010-09-15)

Hi,

 Anyone interested? Anyone submitted such a request already? I'm mainly interested in remoting 3d with spice, and I know there is existing out-of-tree patches for passthrough (not to mention other implementations out there). I guess the idea would be to work on the way forward for both (passthrough and remoting) in qemu.

Alon


----- End forwarded message -----

                 reply	other threads:[~2011-05-19  6:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110519064349.GZ7083@playa.tlv.redhat.com \
    --to=alevy@redhat.com \
    --cc=xen-devel@lists.xensource.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).