lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CA+55aFwAbcQY3RDw0L4RQgX7M98=5ZiWfQc4r-Q+WUhcJ3kSfA@mail.gmail.com>
Date:	Fri, 11 Oct 2013 10:54:58 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Dave Airlie <airlied@...ux.ie>
Cc:	DRI mailing list <dri-devel@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] drm fixes

On Thu, Oct 10, 2013 at 10:28 PM, Dave Airlie <airlied@...ux.ie> wrote:
>
> and one pain in the ass revert, so we have VGA arbitration that when
> implemented 4-5 years ago really hoped that GPUs could remove themselves
> from arbitration completely once they had a kernel driver, it seems Intel
> hw designers decided that was too nice a facility to allow us to have so
> they removed it when they went on-die (so since Ironlake at least), now
> Alex Williamson added support for VGA arbitration for newer GPUs however
> this now exposes itself to userspace as requireing arbitration of GPU VGA
> regions and the X server gets involved and disables things that it can't
> handle when VGA access is possibly required around every operation, so in
> order to break userspace we just reverted things back to the old known
> broken status so maybe we can try and design out way out. Ville also had a
> patch to use stop machine for the two times Intel needs to access VGA
> space, that might be acceptable with some rework, but for now myself and
> Daniel agreed to just go back.

Your explanation messages tend to channel James Joyce. They may be
literary works of art, but it _does_ occasionally make them somewhat
hard to read.

I have tried to turn them into slightly less stream-of-consciousness.

             Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ