linux-kernel - Re: gpu sharing layer for kernel

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]

Message-ID: <21d7e9970701241439y1431254bwf088f9f3043dd0c@mail.gmail.com>
Date:	Thu, 25 Jan 2007 09:39:47 +1100
From:	"Dave Airlie" <airlied@...il.com>
To:	"Greg KH" <greg@...ah.com>
Cc:	airlied@...ux.ie, linux-kernel@...r.kernel.org
Subject: Re: gpu sharing layer for kernel

> > Why do we want this?
> >
> > Currently the kernel cannot provide both the fb and drm drivers with
> > access to the device model and this means the drm cannot get any
> > suspend/resume callbacks.  This layer attempts to fix this problem by
> > adding a bus for the gpu drivers to attach to. Currently a lowlevel
> > binding driver is needed along with optional fb and drm components.
>
> If we were to allow this kind of "sharing" for all PCI devices would
> that work out instead?  Or would this layer still be needed?

Initially this layer wouldn't be needed, but I'd like to add some
awareness to the drivers, so the drm can tell the fb to stop doing
stuff and vice-versa if necessary....  but perhaps that could be done
with a generic layer also.. or via the lowlevel driver I have...

Dave.
-
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/