From: Gert Wollny <gert.wollny@collabora.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [PATCH v7] Add udmabuf misc device
Date: Mon, 10 Sep 2018 18:26:02 +0200 [thread overview]
Message-ID: <1536596762.5451.4.camel@collabora.com> (raw)
In-Reply-To: <20180910133050.tr2lozfmhimqs4c4@sirius.home.kraxel.org>
Am Montag, den 10.09.2018, 15:30 +0200 schrieb Gerd Hoffmann:
> On Mon, Sep 10, 2018 at 01:31:08PM +0200, Gert Wollny wrote:
> > Am Montag, den 10.09.2018, 12:53 +0200 schrieb Gerd Hoffmann:
> > >
> > > By default qemu doesn't use memfd for backing storage, you have
> > > to
> > > explicitly configure qemu that way (see qemu commit log of the
> > > test
> > > branch):
> > >
> > > qemu-system-x86_64 -m 2G
> > > -object memory-backend-memfd,id=ram,size=2G
> > > -numa node,memdev=ram"
> >
> > Thanks, but that doesn't seem to help.
>
With some more debugging I found
WARNING: CPU: 2 PID: 14658 at drivers/dma-buf/dma-buf.c:410
dma_buf_export+0x85/0x270 which refers to dma_buf_export:414
if (WARN_ON(!exp_info->priv
|| !exp_info->ops
|| !exp_info->ops->map_dma_buf
|| !exp_info->ops->unmap_dma_buf
|| !exp_info->ops->release
|| !exp_info->ops->map_atomic
|| !exp_info->ops->map
|| !exp_info->ops->mmap)) {
return ERR_PTR(-EINVAL);
}
Specifically, map_atomic is NULL, but as I can see from the git
version, this was removed some time ago, going to test the 4.19 rc2
kernel now,
Best,
Gert
next prev parent reply other threads:[~2018-09-10 16:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 11:11 [PATCH v7] Add udmabuf misc device Gert Wollny
2018-09-10 8:37 ` Gerd Hoffmann
2018-09-10 9:18 ` Gert Wollny
2018-09-10 10:53 ` Gerd Hoffmann
2018-09-10 11:31 ` Gert Wollny
2018-09-10 13:30 ` Gerd Hoffmann
2018-09-10 14:17 ` Gert Wollny
2018-09-10 16:26 ` Gert Wollny [this message]
2018-09-10 17:39 ` Gert Wollny
-- strict thread matches above, loose matches on Subject: below --
2018-08-27 9:34 Gerd Hoffmann
2018-08-27 9:34 ` Gerd Hoffmann
2018-08-27 9:34 ` Gerd Hoffmann
2018-08-27 9:34 ` kraxel
2018-08-31 8:48 ` Daniel Vetter
2018-08-31 8:48 ` Daniel Vetter
2018-08-31 8:48 ` Daniel Vetter
2018-08-31 8:48 ` daniel
2018-09-10 12:12 ` Laurent Pinchart
2018-09-10 12:12 ` Laurent Pinchart
2018-09-10 12:12 ` laurent.pinchart
2018-09-10 12:12 ` Laurent Pinchart
2018-09-11 6:50 ` Gerd Hoffmann
2018-09-11 6:50 ` Gerd Hoffmann
2018-09-11 6:50 ` kraxel
2018-09-11 9:50 ` Laurent Pinchart
2018-09-11 9:50 ` Laurent Pinchart
2018-09-11 9:50 ` laurent.pinchart
2018-09-11 9:50 ` Laurent Pinchart
2018-09-11 10:05 ` Daniel Vetter
2018-09-11 10:05 ` Daniel Vetter
2018-09-11 10:05 ` daniel
2018-09-11 12:03 ` Gerd Hoffmann
2018-09-11 12:03 ` Gerd Hoffmann
2018-09-11 12:03 ` kraxel
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=1536596762.5451.4.camel@collabora.com \
--to=gert.wollny@collabora.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=kraxel@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomeu.vizoso@collabora.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 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.