| 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
| ||
|
Message-ID: <21d7e9970901280142w50d081b2wfd6cac800c980f37@mail.gmail.com> Date: Wed, 28 Jan 2009 19:42:33 +1000 From: Dave Airlie <airlied@...il.com> To: Jonathan Campbell <jon@...dgrounds.com> Cc: Eric Anholt <eric@...olt.net>, Mark Knecht <markknecht@...il.com>, Linux Kernel List <linux-kernel@...r.kernel.org> Subject: Re: Vramfs: filesystem driver to utilize extra RAM on VGA devices On Wed, Jan 28, 2009 at 7:03 PM, Jonathan Campbell <jon@...dgrounds.com> wrote: > I can't think of a nice way to say this, but this idea is crack. > > Hey, thanks :) >> >> I can see one use for vramfs which is to use VRAM as a file backing >> store, we won't mention that VRAM is slow. Some caveats being >> the PCI aperture only exposes 1/2 the VRAM on some cards, there is >> more hidden away where the CPU can't find it. >> and that some cards have made up VRAM (read IGPs). >> > > I actually have in my possession PCI devices that do just that. The second > half of VRAM can always be found as the "Display controller", function #1, > where the main VGA device is function #0. A PCI Radeon card I have does > that, the Intel graphics chipset in my laptop does that... vramfs is able to > mount that VRAM and use it just fine. one swallow does not a summer make. I have lots of other gpus that don't do this sitting on my desk. some GPUs don't expose a second head. Intel GPU in laptops don't actually have any real VRAM behind them, they just have some small amount allocated by the BIOS. > > Use lspci -v and look for your VGA card, then at the "Display controller" > part (PCI class 0x038000), you'll see where that other half is. > > And VRAM isn't always slow. It usually is slower than host memory, yes, but > not slow enough to be useless. >> >> It doesn't in any way serve as a basis for talking to the GPU behind >> said VRAM or as a basis for any >> sort of backend to talk to the GPU. >> > > It's not supposed to. By design. Someone else runs the GPU. A root-level > userspace daemon controlling the MMIO registers directly through /dev/mem if > you like. This might be useful for the XFree86 or X.org guys for example. I am along with Eric one of the X.org people, hence my crack comment. We are also trying to kill userspace drivers that control the MMIO regs. TBH if you wanted to make this faster, you really would need some sort of CPU offload using the GPU blit engine which is a lot faster than doing CPU access to the uncached VRAM. Dave. >> >> Dave. >> >> >>> >>> My other concern is that GEM with a filesystem might be the best option >>> for >>> 3D gaming, but that it wouldn't work if the driver doesn't know the card. >>> The DRI drivers, as far as I know, are tied to the GPU and chipset of the >>> device (because they have to manage it, after all!). How exactly would >>> GEM >>> work for cards that it doesn't recognize, like one machine of mine with a >>> weird ATI chipset nobody knows how to talk to? If GEM doesn't recognize >>> it, >>> it won't provide VRAM resources to use it, right? >>> >>> This is where vramfs has it's advantage: it's not the absolute best >>> solution >>> for 3D graphics, but it's simple, it can serve as a starting point for >>> GPU >>> experiments from userspace, or if nothing else allows the use of the >>> onboard >>> video RAM on an otherwise unused and unrecognized video device. It's >>> device-agnostic by design. >>> >>>> >>>> The way you want do that is using OpenGL to put your data in textures >>>> and framebuffer objects, and render them. With KMS, we'll be able to >>>> support EGL even on the console so you can do the work without having an >>>> X environment set up. >>>> >>>> The problem with vramfs as a basis for GPU offload is that most GPU >>>> tasks end up at some point exceeding the size of available >>>> aperture/VRAM. So you need code that manages loading buffer objects in >>>> and out on demand, managing the execution pipeline and GPU and CPU >>>> caches as required. We have that with GEM already. >>>> >>>> Remember, writing data to an aperture isn't the hard part of offloading >>>> to the GPU, programming the GPU is. That's why you use OpenGL or >>>> another abstraction to do it. >>>> >>>> >>>> >>> >>> -- >>> 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/ >>> >>> >> >> -- >> 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/ >> >> >> > > -- 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