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 11:18:38 +0200 [thread overview]
Message-ID: <1536571118.4810.38.camel@collabora.com> (raw)
In-Reply-To: <20180910083731.o4rryvermyighbtp@sirius.home.kraxel.org>
Am Montag, den 10.09.2018, 10:37 +0200 schrieb Gerd Hoffmann:
...
> > The other question is of course, why did dma_buf_export fail for me
> > ...
>
> What exactly did you try?
I ran
qemu-system-x86_64 -enable-kvm -smp 5 -M q35 -m 8G \
-drive format=raw,file=ubuntu.raw,if=virtio \
-net nic,model=virtio -net user,hostfwd=tcp::2224-:22 \
-vga virtio
ubuntu.raw = Ubuntu 18.04 (bionic) + 4.17 kernel (from Ubuntu cosmic).
The VM boots up to a certain point, the last line from the boot log is
varying, as far as I can see it is a few lines after virtio_blk detects
the disks.
When I add '-display sdl' the Xsession freezes. I was still able to log
in remotely and kill -9 qemu, then X11 became usable again.
In all cases I get on the host:
qemu-system-x86_64: info: udmabuf: init ok
and there it stays, certainly because of the kernel bug reported.
Best,
Gert
next prev parent reply other threads:[~2018-09-10 9:19 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 [this message]
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
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=1536571118.4810.38.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.