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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 11 Aug 2009 16:17:46 -0700
From:	Jesse Barnes <jesse.barnes@...el.com>
To:	Dave Airlie <airlied@...il.com>
Cc:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	linux-kernel@...r.kernel.org, dri-devel@...ts.sf.net,
	Tiago Vignatti <tiago.vignatti@...ia.com>
Subject: Re: [PATCH] vga: implements VGA arbitration on Linux

On Tue, 11 Aug 2009 15:52:06 +1000
Dave Airlie <airlied@...il.com> wrote:

> From: Tiago Vignatti <tiago.vignatti@...ia.com>
> 
> Background:
> Graphic devices are accessed through ranges in I/O or memory space.
> While most modern devices allow relocation of such ranges, some
> "Legacy" VGA devices implemented on PCI will typically have the same
> "hard-decoded" addresses as they did on ISA. For more details see
> "PCI Bus Binding to IEEE Std 1275-1994 Standard for Boot
> (Initialization Configuration) Firmware Revision 2.1" Section 7,
> Legacy Devices.
> 
> The Resource Access Control (RAC) module inside the X server
> currently does the task of arbitration when more than one legacy
> device co-exists on the same machine. But the problem happens when
> these devices are trying to be accessed by different userspace
> clients (e.g. two server in parallel). Their address assignments
> conflict. Therefore an arbitration scheme _outside_ of the X server
> is needed to control the sharing of these resources. This document
> introduces the operation of the VGA arbiter implemented for Linux
> kernel.
> 
> Signed-off-by: Tiago Vignatti <tiago.vignatti@...ia.com>
> Signed-off-by: Dave Airlie <airlied@...hat.com>

Ok, applied this to my linux-next branch, but I'd like to get Ben's
s-o-b before pushing it to Linus.

Ben?

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center
--
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