From: Gerd Hoffmann <kraxel@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, Tina Zhang <tina.zhang@intel.com>,
intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Qemu-devel] [RfC PATCH 6/6] vfio/display: add dmabuf support (v15)
Date: Wed, 11 Oct 2017 09:01:33 +0200 [thread overview]
Message-ID: <1507705293.31518.7.camel@redhat.com> (raw)
In-Reply-To: <20171010142706.360019aa@t450s.home>
Hi,
> Looks pretty straight forward otherwise. I like the LRU dmabuf
> freeing, but is it mostly for validating the interface? My
> impression
> is that we'd reach a steady state with a single plane and single
> cursor so I wonder if keeping that cache really provides a noticeable
> benefit.
Really depends on what the guest is doing. I didn't do too much
testing with various cache sizes and guests yet.
> Perhaps for a Linux guest switching between vt and graphics
> mode?
fbcon/vt is one dmabuf. xorg I have seen using multiple primary plane
dma-bufs, dunno why, doesn't change often. wayland does page-flipping
on each rendered frame, which translates to very frequent dma-buf
changes and I expect the caching will pay off here.
cursor dma-buf with xorg changes each time the cursor shape changes.
> It also seems like the primary and cursor will be fighting for
> the head of the list, so if we keep lists, maybe they should be per
> plane type.
Makes sense indeed.
> This uses the x-display option for now, how do we move past that to
> get
> automatic configuration?
I think a OnOffAuto display property would be the best choice.
cheers,
Gerd
next prev parent reply other threads:[~2017-10-11 7:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 14:03 [Qemu-devel] [RfC PATCH 0/6] vfio: add display support Gerd Hoffmann
2017-10-10 14:03 ` [Qemu-devel] [RfC PATCH 1/6] headers: update linux-headers/linux/vfio.h (intel-gvt kernel patches, v15) Gerd Hoffmann
2017-10-10 14:03 ` [Qemu-devel] [RfC PATCH 2/6] headers: add drm/drm_fourcc.h to standard-headers Gerd Hoffmann
2017-10-10 14:03 ` [Qemu-devel] [RfC PATCH 3/6] ui/pixman: add qemu_drm_format_to_pixman() Gerd Hoffmann
2017-10-10 14:03 ` [Qemu-devel] [RfC PATCH 4/6] vfio/display: core & wireup Gerd Hoffmann
2017-10-10 14:03 ` [Qemu-devel] [RfC PATCH 5/6] vfio/display: adding region support Gerd Hoffmann
2017-10-10 20:27 ` Alex Williamson
2017-10-11 10:47 ` Gerd Hoffmann
2017-10-11 16:55 ` Alex Williamson
2017-11-10 10:48 ` Gerd Hoffmann
2017-10-10 14:03 ` [Qemu-devel] [RfC PATCH 6/6] vfio/display: add dmabuf support (v15) Gerd Hoffmann
2017-10-10 20:27 ` Alex Williamson
2017-10-11 7:01 ` Gerd Hoffmann [this message]
2017-10-10 14:20 ` [Qemu-devel] [RfC PATCH 0/6] vfio: add display support no-reply
2017-10-10 14:23 ` no-reply
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=1507705293.31518.7.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=qemu-devel@nongnu.org \
--cc=tina.zhang@intel.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).