From: Alex Williamson <alex.williamson@redhat.com>
To: Friedrich Oslage <friedrich+intel-gfx@oslage.de>
Cc: Dave Airlie <airlied@redhat.com>, intel-gfx@lists.freedesktop.org
Subject: Re: VGA arbiter support for Intel HD?
Date: Thu, 03 Apr 2014 12:28:27 -0600 [thread overview]
Message-ID: <1396549707.3215.23.camel@ul30vt.home> (raw)
In-Reply-To: <20140403194747.6d72874c@Anteaus.local.porno-bullen.de>
On Thu, 2014-04-03 at 19:47 +0200, Friedrich Oslage wrote:
> Hi,
>
> several months ago Alex Williamson added a patch to the linux kernel to
> enable VGA arbiter support for the IGD of Intel Core CPUs [1]. But just
> a month after that the patch was reverted [2].
>
> With these patches I am able to use VFIO and Qemu to passthrough a GTX
> 770 while using the Intel HD of a i7 4771 on the host for X.Org/XFCE.
>
> Using the stock 3.14 kernel, without these patches, it doesn't work.
> I believe the Nvidia card doesn't get initialized correctly...the
> screen stays black and the guest OS is unreachable via network.
>
>
> What is required to get these patches back into the mainline kernel? I
> can not reproduce the issues described in the revert commit log,
> perhaps we just need more testing?
I just happened to write-up an explanation this morning:
https://bbs.archlinux.org/viewtopic.php?pid=1400212#p1400212
Last I heard DRI gets disabled whenever Xorg finds that the VGA arbiter
is managing multiple devices. Therefore, while X still works, the
typical use case will have a pretty severe performance decrease.
I started designing a next-gen VGA arbiter that provides userspace with
a file descriptor they can use for accessing VGA space, including mmap.
This seems to work, invalidating the mapping in the no-lock-holder,
allowing it to fault and block re-mapping until the lock can be
re-acquired. I got stalled trying to figure out how to make use of it
in Xorg though. If anyone is interested in working on this, I'll
happily post my new arbiter code.
Dave Airlie also suggested that maybe all of the VGA arbiter support in
Xorg could be ripped out without anyone noticing (now I've spilled the
beans), but that would also solve the DRI problem. We'd probably need
to keep things as-is in i915 for compatibility for some time though.
That brings up another option of including those patches under some kind
of CONFIG_I915_DONT_LIE_TO_VGA_ARBITER option so a user could configure
their kernel how they choose. This may just turn the complaints into "I
want both" though.
As noted in the forum, another option is to avoid VGA in the guest by
using a "legacy-free" UEFI BIOS. This may circumvent other problems,
like lack of arbiter support in other drivers, but it relies on a
compatible legacy-free graphics card BIOS and guest support.
I'd certainly like to make progress on this, so welcome some sort of
discussion. Thanks,
Alex
next prev parent reply other threads:[~2014-04-03 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 17:47 VGA arbiter support for Intel HD? Friedrich Oslage
2014-04-03 18:28 ` Alex Williamson [this message]
2014-04-05 9:42 ` Friedrich Oslage
-- strict thread matches above, loose matches on Subject: below --
2013-08-14 13:23 Alex Williamson
2013-08-14 14:47 ` Ville Syrjälä
2013-08-14 17:14 ` Alex Williamson
2013-08-14 18:30 ` Ville Syrjälä
2013-08-14 19:39 ` Alex Williamson
2013-08-14 20:01 ` Ville Syrjälä
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=1396549707.3215.23.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=airlied@redhat.com \
--cc=friedrich+intel-gfx@oslage.de \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox