From: Alex Williamson <alex.williamson@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: make fbdev/fbcon switchable per driver?
Date: Fri, 27 Jan 2017 11:30:19 -0700 [thread overview]
Message-ID: <20170127113019.6621b1b5@t450s.home> (raw)
In-Reply-To: <1485511238.19754.58.camel@redhat.com>
On Fri, 27 Jan 2017 11:00:38 +0100
Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hi folks,
>
> Problem at hand: A virtual machine, equipped with two display devices,
> one virtual, one physical (using pci pass-through, or kvmgt-based vgpu).
>
> There is no easy way for the user to configure which of the two display
> devices fbcon should run on. i915 happens to win over bochs-drm or qxl,
> so you can't use the emulated gfx device as text console.
>
> One way out would be to add a module option to each driver, to turn off
> fbdev emulation. Attached patch does that for i915.
>
> Comments? Better ideas?
The vgaarb code has a concept of a vga_default_device(), it's rather
PCI-centric, but maybe better than nothing. This is typically the
first VGA class code device found with I/O and MMIO enabled. If fbcon
defaulted to running on the vga_default_device(), a user could select
which to use by re-ordering the VM hardware.
The problem isn't absent on bare metal, though re-ordering hardware
isn't always as simple, or necessarily possible. The problem might run
deeper there too dealing with vesafb and simplefb, as well as the more
device specific drivers. Rerouting legacy resources isn't always an
option, but some sort of primary selection for non-encumbered devices
would be useful. Thanks,
Alex
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-27 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 10:00 make fbdev/fbcon switchable per driver? Gerd Hoffmann
2017-01-27 14:02 ` Daniel Vetter
2017-01-27 14:41 ` Liviu Dudau
2017-01-27 18:30 ` Alex Williamson [this message]
2017-01-30 8:15 ` Gerd Hoffmann
2017-01-30 17:45 ` Alex Williamson
2017-01-31 8:00 ` Daniel Vetter
2017-01-31 10:06 ` Gerd Hoffmann
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=20170127113019.6621b1b5@t450s.home \
--to=alex.williamson@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@redhat.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