All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	David Airlie <airlied@linux.ie>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"open list:VIRTIO CORE,
	NET..." <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] drm/virtio: Add window server support
Date: Fri, 12 Jan 2018 14:11:04 +1000	[thread overview]
Message-ID: <CAPM=9twT_jtfJteuUpRvu1Xn3nNfxG-5oLfcbHYVnHVeS9TzcA__18090.9829251052$1515730174$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <20171228115333.12289-1-tomeu.vizoso@collabora.com>

>
> this work is based on the virtio_wl driver in the ChromeOS kernel by
> Zach Reizner, currently at:
>
> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/chromeos-4.4/drivers/virtio/virtio_wl.c
>
> There's two features missing in this patch when compared with virtio_wl:
>
> * Allow the guest access directly host memory, without having to resort
> to TRANSFER_TO_HOST
>
> * Pass FDs from host to guest (Wayland specifies that the compositor
> shares keyboard data with the guest via a shared buffer)
>
> I plan to work on this next, but I would like to get some comments on
> the general approach so I can better choose which patch to follow.

Shouldn't qemu expose some kind of capability to enable this so we know to
look for the extra vqs?

What happens if you run this on plain qemu, does it fallback correctly?

Are there any scenarios where we don't want to expose this API because there
is nothing to back it.

Dave.

  parent reply	other threads:[~2018-01-12  4:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 11:53 [PATCH] drm/virtio: Add window server support Tomeu Vizoso
2017-12-28 11:53 ` Tomeu Vizoso
2018-01-09 12:56 ` Tomeu Vizoso
2018-01-09 12:56   ` Tomeu Vizoso
2018-01-09 12:56 ` Tomeu Vizoso
2018-01-12  4:11 ` Dave Airlie
2018-01-12  4:11   ` Dave Airlie
2018-01-12  7:59   ` Tomeu Vizoso
2018-01-12  7:59   ` Tomeu Vizoso
2018-01-12  7:59     ` Tomeu Vizoso
2018-01-12  4:11 ` Dave Airlie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-28 11:53 Tomeu Vizoso
2017-12-14 12:43 Tomeu Vizoso
2017-12-14 12:43 ` Tomeu Vizoso
2017-12-16  0:50 ` kbuild test robot
2017-12-16  0:50 ` kbuild test robot
2017-12-16  0:50   ` kbuild test robot
2017-12-16  0:58 ` kbuild test robot
2017-12-16  0:58   ` kbuild test robot
2017-12-14 12:43 Tomeu Vizoso

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='CAPM=9twT_jtfJteuUpRvu1Xn3nNfxG-5oLfcbHYVnHVeS9TzcA__18090.9829251052$1515730174$gmane$org@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=tomeu.vizoso@collabora.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.