Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131004023258.GB31318@openwall.com>
Date: Fri, 4 Oct 2013 06:32:58 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: AMD GPU documentation (was: Daniel's weekly report #15)

Lukas, Daniel -

On Thu, Oct 03, 2013 at 06:31:14PM +0200, Lukas Odzioba wrote:
> I have two ideas at the moment:
> 1) can you split binary on parts using definitions in this header:
> http://www.multi2sim.org/svn/multi2sim/trunk/src/arch/southern-islands/asm/bin-file.h
> 
> I am curious how much of that match the real format.
> 
> 2) Since CAL has separated compilation and linking phases, maybe we
> can somehow do something like pathing between those phases.
> You probably saw this:
> http://developer.amd.com/wordpress/media/2012/10/AMD_CAL_Programming_Guide_v2.0.pdf

BTW, speaking of AMD documentation on Southern Islands GPUs, these PDFs
might be relevant to the project as well:

http://www.x.org/docs/AMD/si_programming_guide_v2.pdf
http://www.x.org/docs/AMD/SI_3D_registers.pdf

In particular, page 165+ in SI_3D_registers.pdf describes "Shared
Program Registers", which includes things such as "Number of VGPRs,
granularity 4. Range is from 0-63 allocating 4, 8, 12, ... 256" - a
certain 6-bit value at a certain address (memory-mapped register?)
This might answer, negatively, my question on whether we can go beyond
256 VGPRs for a single work-item.

Alexander

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.