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:	Thu, 21 Aug 2008 15:42:59 +0200
From:	Jerome Glisse <glisse@...edesktop.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Keith Packard <keithp@...thp.com>,
	Nick Piggin <nickpiggin@...oo.com.au>,
	Dave Airlie <airlied@...il.com>,
	Christoph Hellwig <hch@...radead.org>,
	Eric Anholt <eric@...olt.net>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Export shmem_file_setup and shmem_getpage for DRM-GEM

On Tue, 19 Aug 2008 11:50:11 -0700
Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> As for in-kernel stuff, as long as we keep the GEM shmem hooks separate from 
> the actual bookkeeping (like we do now with i915_gem_create_ioctl() vs 
> drm_gem_object_alloc() for example) we should be able to do the in-kernel 
> stuff w/o jumping through too many VFS/VM hoops.  That would also assume we 
> don't care about swapping in the in-kernel case, which we don't; we want to 
> pin the kernel allocated frame buffer and other memory anyway, so using the 
> internal functions should be fine.

What about suspend to disk ? How do we save such buffers ? 

Btw i think that GTT looks a lot like IOMMU, i don't know the IOMMU kernel
side API that much, but from memory i think that you have call to ask IOMMU
mapping why not do somethings like that for GTT ?

You get normal mapping of object diret but userspace can ask some kind of
GTT mapping on a given object. Anyway new flag on fd sounds good enough too.

Cheers,
Jerome Glisse <glisse@...edesktop.org>
--
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