From: Tomasz Figa <tfiga@chromium.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@linux.ie>,
dri-devel <dri-devel@lists.freedesktop.org>,
virtualization@lists.linux-foundation.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
stevensd@chromium.org,
"Stéphane Marchesin" <marcheu@chromium.org>,
"Zach Reizner" <zachr@chromium.org>,
"Keiichi Watanabe" <keiichiw@chromium.org>,
"Pawel Osciak" <posciak@chromium.org>
Subject: Re: [RFC PATCH] drm/virtio: Export resource handles via DMA-buf API
Date: Wed, 16 Oct 2019 17:27:04 +0900 [thread overview]
Message-ID: <CAAFQd5B2KRJ4hKuh2rwYvgY+FLzAR-ZqNthz9XrsaPm3v3Rsnw@mail.gmail.com> (raw)
In-Reply-To: <20191016061201.iinqjcw6trx5qztq@sirius.home.kraxel.org>
On Wed, Oct 16, 2019 at 3:12 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> Hi,
>
> > up later when given a buffer index. But we would still need to make
> > the DMA-buf itself importable. For virtio-gpu I guess that would mean
> > returning an sg_table backed by the shadow buffer pages.
>
> The virtio-gpu driver in drm-misc-next supports dma-buf exports.
Good to know, thanks.
Best regards,
Tomasz
next prev parent reply other threads:[~2019-10-16 8:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 9:41 [RFC PATCH] drm/virtio: Export resource handles via DMA-buf API Tomasz Figa
2019-09-12 12:38 ` Gerd Hoffmann
2019-09-12 12:38 ` Gerd Hoffmann
2019-09-12 14:04 ` Tomasz Figa
2019-09-13 8:07 ` Gerd Hoffmann
2019-09-13 8:07 ` Gerd Hoffmann
2019-09-13 8:31 ` Tomasz Figa
2019-09-13 11:05 ` Gerd Hoffmann
2019-09-13 11:05 ` Gerd Hoffmann
2019-09-19 11:41 ` Keiichi Watanabe
2019-09-17 13:23 ` Daniel Vetter
2019-09-17 13:23 ` Daniel Vetter
2019-10-05 5:41 ` Tomasz Figa
2019-10-05 5:41 ` Tomasz Figa
2019-10-08 10:03 ` Daniel Vetter
2019-10-08 10:03 ` Daniel Vetter
2019-10-08 10:49 ` Tomasz Figa
2019-10-08 15:04 ` Daniel Vetter
2019-10-16 3:19 ` Tomasz Figa
2019-10-16 6:12 ` Gerd Hoffmann
2019-10-16 6:12 ` Gerd Hoffmann
2019-10-16 6:12 ` Gerd Hoffmann
2019-10-16 8:27 ` Tomasz Figa [this message]
2019-10-16 9:18 ` Daniel Vetter
2019-10-16 9:18 ` Daniel Vetter
2019-10-16 10:31 ` Tomasz Figa
2019-10-08 15:04 ` Daniel Vetter
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=CAAFQd5B2KRJ4hKuh2rwYvgY+FLzAR-ZqNthz9XrsaPm3v3Rsnw@mail.gmail.com \
--to=tfiga@chromium.org \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=keiichiw@chromium.org \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=posciak@chromium.org \
--cc=stevensd@chromium.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zachr@chromium.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.